IANA.ORG Services and Ports list
Service Name and Transport Protocol Port Number Registry
Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP.
TCP/UDP:
- Joe Touch
- Eliot Lear
- Kumiko Ono
- Wes Eddy
- Brian Trammell
- Jana Iyengar
- Michael Scharf
SCTP:
- Michael Tuexen
DCCP:
- Eddie Kohler
- Yoshifumi Nishida
ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN ENDORSEMENT OF AN APPLICATION OR PRODUCT
THE FACT THAT NETWORK TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT IT IS “GOOD” TRAFFIC, NOR THAT IT NECESSARILY CORRESPONDS TO THE ASSIGNED SERVICE.FIREWALL AND SYSTEM ADMINISTRATORS SHOULD CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER REGISTERED OR NOT
Service names are assigned on a first-come, first-served process, as documented in RFC63351.
Port numbers are assigned in various ways, based on three ranges:
Range | Purpose |
---|---|
0-1023 | System |
1024-49151 | User |
49152-65535 | Dynamic / Private |
The different uses of these ranges are described in RFC63351.
According to Section 8.1.2 of RFC63353, System Ports are assigned by the “IETF Review” or “IESG Approval” procedures described in RFC8126.
User Ports are assigned by
- IANA using the “IETF Review” process
- the “IESG Approval” process
- The “Expert Review” process, as per RFC63351.
Dynamic Ports are not assigned.
The registration procedures for service names and port numbers are described in RFC63351.
Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.