A common network ports list is a curated reference table that maps frequently used port numbers to the registered service names, transport protocols, and short descriptions an operator is likely to encounter in everyday troubleshooting, configuration review, or study work. The Common Network Ports List is built for that exact task: it holds one numeric port per row, the selected IANA service name, the relevant transport protocol, a plain-language description, and a category label, sorted numerically and searchable from a single field. It is deliberately curated rather than a reproduction of the entire registry, which keeps the table readable and fast on every lookup. Every search and filter result stays on the page, so the tool also fits ticket workflows where network details need to be recorded without sending data to a third party.
Ports themselves are a 16-bit identifier carried in a TCP or UDP header. They tell a client where on a host to direct a connection, and they tell a server which socket should receive incoming traffic. Because the same number can host different services on different machines, because servers may bind an unusual number, and because a single registered number can host more than one IANA assignment, a port number is a hint about a likely service, not a proof of identity. That distinction shapes how the curated list is meant to be used: translate a number into a candidate service, then confirm with platform-native tools, configuration files, and the actual endpoint.
How the Port Number Space Is Organized
The Internet Assigned Numbers Authority, working through the rules in RFC 6335, divides the 16-bit port space into three ranges. Knowing which range a port sits in tells you roughly what kind of service to expect, what kind of process is allowed to bind it on a typical Unix host, and how permanent the assignment is.
| Range | Numeric span | Purpose | Typical binding |
|---|---|---|---|
| System Ports | 0 – 1023 | Assigned services, tightly coupled to well-known protocols such as HTTP, HTTPS, SSH, and SMTP | Often requires elevated privileges on Unix-like systems |
| User Ports | 1024 – 49151 | Registered services run by user-level processes, including databases, messaging, directory, and remote access daemons | Generally bindable by ordinary users |
| Dynamic or Private Ports | 49152 – 65535 | Ephemeral client ports and private or convention-based services not tracked by IANA | Used by client sockets for outgoing connections |
The Common Network Ports List covers a curated mix of System and User Ports. It does not enumerate the dynamic range, because ephemeral ports are assigned by the operating system at connection time and are not the kind of number an operator looks up by hand. A port that is absent from the table may still be registered with IANA, used by convention by a specific vendor, or reserved for a private deployment, and absence means only that it sits outside the curated set.
Search and Filter the Common Network Ports List
The tool is intentionally small, with one field, two filters, and a copy action, so it fits cleanly into a side-by-side workflow next to a terminal, a ticket, or a configuration file. Follow these steps to look up a port or copy a reference.
- Open the Common Network Ports List in your browser; the full table loads immediately with all rows visible.
- Enter a port number, service name, product term, or plain-language description in the search field. A query for 443 returns HTTPS, a query for PostgreSQL returns 5432, and a query for mail returns SMTP, POP3, IMAP, message submission, and their TLS variants.
- If you want to isolate a specific transport, apply the protocol filter to show only TCP rows or only UDP rows where the distinction is meaningful. DNS appears with both protocols in the curated table, for example, while HTTPS is shown with TCP only.
- Apply the category filter to narrow the visible rows to a single group, such as databases, web services, remote access, directory, messaging, file transfer, printing, container, or core network services, without altering the underlying reference data.
- Review the matching registration hints in the table, paying attention to the service name, protocol, and short description together rather than to the port number alone.
- When you need a tab-separated reference for tickets, runbooks, study notes, or a configuration review, use the copy action to export only the rows currently visible after filtering.
Because every search and filter runs locally in the browser, no query or copied result leaves the page, which makes the workflow appropriate for incidents where packet details or internal hostnames would otherwise be sensitive.
Categories Covered by the Curated Table
The category label on each row is the same label used by the category filter, so it doubles as a quick grouping and as a way to scope a lookup. The curated set is organized to match common operational questions rather than to mirror the alphabetical shape of the registry.
| Category | What it groups | Example entries |
|---|---|---|
| Web services | HTTP, HTTPS, and adjacent web protocols used to serve or proxy content | 80, 443, 8080, 8443 |
| SMTP, POP3, IMAP, submission, and their TLS variants | 25, 110, 143, 465, 587, 993, 995 | |
| File transfer | FTP, SFTP, FTPS, and related transfer protocols | 20, 21, 22, 989, 990 |
| Remote access | SSH, Telnet, RDP, VNC, and similar console or desktop protocols | 22, 23, 3389, 5900 |
| Directory | LDAP, LDAPS, and related naming services | 389, 636 |
| Database | Common relational, document, and cache databases | 1433, 1521, 3306, 5432, 6379, 27017 |
| Messaging | AMQP, MQTT, and other message brokers | 5672, 15672, 1883, 8883 |
| Printing and container | Print services plus Docker and Kubernetes APIs | 515, 631, 2375, 2376, 6443 |
| Core network | DNS, DHCP, NTP, SNMP, Syslog, and infrastructure basics | 53, 67, 68, 123, 161, 514 |
Some ports legitimately belong to more than one category, such as a TLS variant that could be read as either mail or directory. The curated table assigns one category per row so that the filter behaves predictably, and the short description and service name carry the rest of the context.
Why a Port Number Is Not Proof of Identity
IANA explicitly warns that the act of assigning a port number does not endorse a specific application and does not, on its own, prove that observed traffic is good. Three practical consequences follow for anyone using a port list at work.
- Servers can listen on an unusual port. An administrator can run HTTPS on port 8443, run a database on a non-default port, or move an entire service off its registered number for operational reasons. The presence of traffic on 443 does not prove it is HTTPS, and traffic on 8443 is not automatically something else.
- A single port number can host several registered names. IANA lists more than one service name for some numbers, and a packet that uses a registered number may belong to a program that happens to bind that number without being the listed service.
- Encryption depends on the real configuration. The same daemon may speak clear text or TLS depending on how it was started, so a row labelled IMAPS does not by itself tell you that the traffic on 993 is encrypted on the wire. Compare related clear-text and TLS entries, then confirm against the actual service configuration.
For these reasons, the curated list is not a firewall allowlist. A working firewall rule needs direction, source, destination, protocol, authentication, encryption status, business owner, and a least-privilege scope; a port number is just one input into that decision. For deeper background on a few specific entries, the related guide Five Common Network Ports and Their Services Explained walks through the practical use of 22, 53, 80, 443, and 3389.
When to Reach for the Full IANA Registry
The curated table is tuned for everyday lookups, where speed and readability matter more than exhaustiveness. There are several situations where the IANA Service Name and Transport Protocol Port Number Registry is the right next stop instead.
- You need every registered name for a single number, including aliases, contacts, assignment dates, and references.
- You are looking for SCTP or DCCP transport entries, which are outside the scope of the curated TCP and UDP view.
- You need the latest change history for a port, especially after a recent reassignment or deprecation.
- You are auditing a service against the authoritative wording rather than a shortened description.
RFC 6335 also gives the regulatory background for how IANA allocates and reviews port numbers, which matters when you are writing policy or explaining why a number is reserved. For anything that touches a production decision, the right pattern is to use the Common Network Ports List to translate a number into a likely service, then confirm against the real endpoint with platform-native tools, service configuration, logs, and network policy before changing anything.