Well-known port
What is Well-known port?
A well-known port -- a System Port in RFC 6335's terms -- is one of the 1,024 numbers from 0-1023 IANA reserves for an established service, like 22 for SSH or 443 for HTTPS. A port number is a strong hint about what's listening, not a guarantee, which is why AdminKit's port-check tool reports what actually answers.
By AdminKit team, Netbase JSC · Updated
A well-known port — formally a System Port in RFC 6335’s terminology — is one of the 1,024 port numbers from 0-1023 that IANA reserves for an established service, such as 21 for FTP, 22 for SSH, 443 for HTTPS, or 502 for Modbus/TCP. RFC 6335 divides the full 0-65535 TCP/UDP port space into three ranges tracked in IANA’s Service Name and Transport Protocol Port Number Registry: System Ports (0-1023, the well-known ports, requiring IANA review to assign), User Ports (1024-49151, also called registered ports, assignable to a named application on request), and Dynamic or Private Ports (49152-65535, never formally assigned, used as ephemeral source ports for outbound connections). On Linux, the ip(7) manual page calls ports below 1024 privileged ports: only a privileged process, meaning one with the CAP_NET_BIND_SERVICE capability, may bind to them.
None of these ranges are enforced by the network itself — any sufficiently privileged process can bind to any port regardless of what the registry says it’s for, a limitation NIST’s firewall guidelines flag when discussing the limits of port-based filtering rules, and a home router’s port forwarding rule, or NAT more generally, maps a port number through to an internal device the same way regardless of which range that number falls in — so a port number is a strong hint about what’s listening, not a guarantee; an open port that doesn’t match its registered service is itself worth investigating — port 1521, which Oracle’s database listener uses by convention, is a concrete example: IANA’s registry actually lists it under an older, unrelated assignment. A well-known URI is an entirely separate IANA registry despite the shared name — a path under /.well-known/ on a web server, not a TCP/UDP port number.
Well-known port is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What is a well-known port?
One of the 1,024 port numbers from 0-1023 that IANA reserves for an established service -- a System Port in RFC 6335's terminology.
What are the other two port ranges RFC 6335 defines?
User Ports (1024-49151, also called registered ports) and Dynamic or Private Ports (49152-65535, used as ephemeral source ports).
Is a well-known port number enforced by the network itself?
No -- any sufficiently privileged process can bind to any port regardless of what the registry says it is for.
Is a well-known port the same thing as a well-known URI?
No -- despite the shared name, they are two entirely separate IANA registries: one is a TCP/UDP port number, the other a path on a web server.
Sources
- RFC 6335 -- Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
- IANA -- Service Name and Transport Protocol Port Number Registry
- NIST SP 800-41 Rev. 1 -- Guidelines on Firewalls and Firewall Policy
- Linux man-pages -- ip(7), Linux IPv4 protocol implementation