Network Ports Explained: The Complete Guide to Common Ports

If IP addresses are the street addresses of the internet, then ports are the apartment numbers. They ensure that data arriving at a machine gets delivered to the right application. Whether you're configuring a firewall, troubleshooting connectivity issues, or studying for a networking certification, understanding ports is absolutely essential.

This guide covers everything you need to know — from the basics of the transport layer to a complete reference of the most important ports in use today.

What Exactly Is a Port?

A network port is a 16-bit number (ranging from 0 to 65,535) that identifies a specific process or service on a machine. Ports operate at the transport layer (Layer 4) of the OSI model, working alongside protocols like TCP and UDP to route data to the correct application.

When your browser connects to a web server, it doesn't just connect to an IP address — it connects to an IP address on a specific port. For example, 93.184.216.34:443 means "connect to this IP on port 443 (HTTPS)."

The Three Port Ranges

The 65,535 available ports are divided into three official ranges defined by IANA (Internet Assigned Numbers Authority):

Well-Known Ports (0–1023)

Reserved for the most common, standardized services. These require root/administrator privileges to bind to on most operating systems. Examples: HTTP (80), HTTPS (443), SSH (22), DNS (53).

Registered Ports (1024–49151)

Assigned by IANA to specific services upon request, but don't require special privileges. Examples: MySQL (3306), PostgreSQL (5432), RDP (3389), alternative HTTP (8080).

Dynamic/Ephemeral Ports (49152–65535)

Used temporarily by client applications for outbound connections. When your browser connects to a website, it picks a random ephemeral port as the source port. These are never assigned to specific services.

The Ports Every IT Professional Should Know

Here's a comprehensive reference of the most important ports you'll encounter in the real world:

File Transfer & Remote Access

• Port 21 — FTP (File Transfer Protocol): The classic file transfer protocol. Sends credentials in plaintext, so use SFTP (port 22) instead whenever possible.
• Port 22 — SSH (Secure Shell): Encrypted remote access to servers. Also used for SFTP and SCP file transfers. The backbone of server administration.
• Port 3389 — RDP (Remote Desktop Protocol): Windows Remote Desktop. Used to graphically control remote Windows machines. A common target for brute-force attacks — always use strong passwords and consider VPN access.

Email

• Port 25 — SMTP (Simple Mail Transfer Protocol): Used for sending email between mail servers. Often blocked by ISPs to prevent spam.
• Port 110 — POP3 (Post Office Protocol): Downloads email from the server and typically deletes it. Largely replaced by IMAP.
• Port 143 — IMAP (Internet Message Access Protocol): Syncs email across devices, keeping messages on the server. The modern standard for email retrieval.

Web & DNS

• Port 53 — DNS (Domain Name System): Translates domain names to IP addresses. Uses both TCP and UDP — UDP for standard queries, TCP for zone transfers and large responses.
• Port 80 — HTTP (HyperText Transfer Protocol): Unencrypted web traffic. Most sites now redirect port 80 to port 443 (HTTPS).
• Port 443 — HTTPS (HTTP Secure): Encrypted web traffic using TLS. The standard for all modern websites.
• Port 8080 — Alt HTTP: Commonly used as an alternative HTTP port for development servers, proxies, and web applications that don't want to bind to privileged port 80.

Database & File Sharing

• Port 445 — SMB (Server Message Block): Windows file sharing. Historically targeted by malware (WannaCry ransomware exploited SMB vulnerabilities). Should never be exposed to the internet.
• Port 3306 — MySQL: The default port for MySQL and MariaDB databases. Bind to localhost only unless you explicitly need remote access.
• Port 5432 — PostgreSQL: The default port for PostgreSQL. Same advice as MySQL — keep it off the public internet.

TCP vs. UDP: Two Protocols, Different Trade-offs

Ports work with two transport-layer protocols, each designed for different use cases:

TCP (Transmission Control Protocol) is connection-oriented. It establishes a three-way handshake, guarantees delivery, and ensures packets arrive in order. Most services use TCP: HTTP, SSH, SMTP, FTP, databases.

UDP (User Datagram Protocol) is connectionless. It fires packets without confirming receipt — faster but unreliable. Used for DNS queries, video streaming, VoIP, and gaming where speed matters more than perfection.

Port Forwarding Basics

Port forwarding is a NAT (Network Address Translation) technique that redirects traffic arriving on a specific port of your router to a specific device on your local network. Common use cases include:

• Hosting a game server from home
• Accessing a home security camera remotely
• Running a web server on your local machine
• Setting up remote desktop access to a home PC

To set up port forwarding, you typically log into your router's admin panel, find the port forwarding section, and create a rule mapping an external port to an internal IP and port. Always be mindful of the security implications — every forwarded port is a potential entry point.

Explore All 65,535 Ports on NetLynx

Need to look up a specific port? The NetLynx Port Database has a dedicated page for every single port from 0 to 65,535 — that's 65,535 individual reference pages. Each page includes the port number, common services that use it, the protocol (TCP/UDP), and security notes.

Whether you're configuring a firewall, investigating suspicious traffic, or just curious about what's running on a port, bookmark the NetLynx port database for instant reference.

Final Thoughts

Ports are a fundamental building block of networking. They're how your computer knows to send web traffic to your browser, email to your mail client, and database queries to MySQL. Understanding which ports do what — and which ones to lock down — is essential knowledge for developers, sysadmins, and security professionals alike.

Keep this guide bookmarked as a reference, and use the NetLynx port database whenever you need a quick lookup.