Common Port Numbers List for CompTIA Network+ (N10-009)
To pass the CompTIA Network+ (N10-009), you must memorize key port numbers categorized as Well-Known (0-1023), Registered (1024-49151), and Dynamic (49152-65535). Focus on critical TCP ports like HTTPS (443) and SSH (22), and UDP ports like DNS (53) and DHCP (67/68) to ensure network connectivity and security.
Why do you need to memorize port numbers for the Network+?
Think of port numbers as the specific doors to a building. If the IP address gets you to the right building, the port number ensures you enter the right room to get the service you need. For the N10-009 exam, you aren't just memorizing a list for the sake of it; you're learning how to troubleshoot connectivity issues and configure firewalls. If a user can't access a website, you need to know instantly that TCP port 80 or 443 is likely blocked.
In real-world scenarios, misconfigured ports are the root cause of countless network outages. Whether you are setting up a secure shell (SSH) connection or configuring a DHCP relay, knowing the transport layer protocol and the associated port is non-negotiable. We see students struggle most when they confuse TCP and UDP applications, so mastering this mapping early is the fastest way to boost your score in the Network Operations domain.
How are port numbers categorized by IANA?
The Internet Assigned Numbers Authority (IANA) divides the 65,535 available ports into three distinct ranges. First, the Well-Known Ports (0-1023) are reserved for system processes and core services. These are the 'heavy hitters' you'll see most often on the exam, such as HTTP and FTP. Because these are critical, they typically require administrative privileges to bind to on a host system.
Next, we have the Registered Ports (1024-49151). These are used by specific applications or vendors. For example, Microsoft's RDP uses port 3389. Finally, the Dynamic or Private Ports (49152-65535) are used as ephemeral ports. When your browser opens a connection to a server, your OS assigns a random dynamic port to that session so the returning traffic knows exactly which tab it belongs to. Understanding this hierarchy helps you identify whether a service is a standard system process or a third-party application.
Which TCP ports are non-negotiable for the exam?
TCP (Transmission Control Protocol) is all about reliability. It uses a three-way handshake to ensure data arrives intact and in order. For the N10-009, you must prioritize these four: SSH (22) for secure remote management, HTTP (80) for unencrypted web traffic, HTTPS (443) for encrypted web traffic, and RDP (3389) for remote desktop access.
When you're studying, don't just memorize the number—associate it with the behavior. For instance, if you see a question about 'securely managing a Linux server,' your brain should immediately jump to TCP 22. If the scenario mentions 'encrypted web transactions,' think TCP 443. We recommend creating a mental map where you group these by function (e.g., 'Management Ports' vs. 'Web Ports') to avoid mixing them up during the high-pressure environment of the testing center.
Which UDP ports should you prioritize?
UDP (User Datagram Protocol) is the 'fire and forget' protocol. It's faster than TCP because it doesn't check if the data arrived. This makes it perfect for services where speed is more important than 100% accuracy. You need to know DNS (53), which handles domain name resolution, and DHCP (67 for the server, 68 for the client), which automatically assigns IP addresses to devices on your network.
Another critical one is SNMP (Simple Network Management Protocol), which uses ports 161 and 162. Port 161 is used for general requests, while 162 is used for 'traps'—alerts that a device sends to a management station when something goes wrong. A common exam trick is to ask which protocol a monitoring tool uses; remembering that SNMP is primarily UDP-based will save you from picking a TCP-based distractor answer.
How do you map services to their transport layer protocols?
The secret to mastering this is understanding the 'Why.' Ask yourself: 'Does this service need a guaranteed delivery?' If the answer is yes (like an email or a file transfer), it's TCP. If the answer is 'I just need this data as fast as possible' (like a DNS query or a VoIP call), it's UDP. This logical approach is far more effective than rote memorization.
For example, DNS is unique because it can use both. For a simple query, it uses UDP 53 for speed. However, if the response is too large or it's performing a zone transfer between servers, it switches to TCP 53 for reliability. Mapping these services to their protocols is a core part of the N10-009 objectives. When you practice, try to visualize the packet flow: is it a steady stream (TCP) or a burst of independent packets (UDP)?
What is the most effective way to memorize these for the N10-009?
Passive reading is the enemy of retention. To truly lock these port numbers into your long-term memory, you need active recall. Start with flashcards, but quickly move to application-based practice. Try to simulate a firewall configuration: 'If I want to allow web traffic but block remote desktop, which ports do I open and close?'
This is where we've focused our efforts at Cert Sensei. We provide 1,000 expert-curated CompTIA Network+ (N10-009) practice questions that put these ports into real-world scenarios. Instead of just asking 'What is port 22?', we'll give you a troubleshooting scenario where a technician can't SSH into a switch. With our detailed expert reasoning for every answer and domain-level analytics, you can see exactly which port groups you're struggling with and pivot your study time to where it actually matters.
❓ Frequently Asked Questions
Do I need to know both TCP and UDP for DNS (Port 53)?
Yes. While most DNS queries use UDP 53 for speed, zone transfers between DNS servers and very large responses require the reliability of TCP 53. The exam may test your knowledge of this distinction.
What is the difference between DHCP ports 67 and 68?
Port 67 is used by the DHCP server to listen for requests from clients, while port 68 is used by the DHCP client to receive the server's responses. They work as a pair to automate IP addressing.
How do I remember the difference between SNMP 161 and 162?
Think of 161 as the 'Question' port (the manager asking the device for status) and 162 as the 'Scream' port (the device sending an unsolicited trap/alert to the manager).