Service Name and Transport Protocol Port Number Registry
Last Updated
- 2026-11-06
Expert(s)
- TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, and Michael Scharf
- SCTP: Michael Tuexen
- DCCP: Eddie Kohler and Yoshifumi Nishida
Reference
- RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
Note
Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP.
Service names are assigned on a First Come First Served basis, as described in RFC 6335.
Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:
- System Ports (0-1023) are assigned using the IETF Review or IESG Approval procedures.
- User Ports (1024-49151) are assigned using the IETF Review, IESG Approval, or Expert Review procedures.
- Dynamic and/or Private Ports (49152-65535) are not assigned.
The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.
Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.
Assignment of a port number does not in any way imply an endorsement of an application or product, and 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.
Registration Forms
- To request a new assignment, please use the Application for Service Names and User Port Numbers form.
- To modify an existing assignment, please use the Modify a Port Number Assignment form.
Available Formats
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dectalk | 2007 | tcp | |||||||||
| raid-am | 2007 | udp | |||||||||
| easl | 3693 | tcp | Emergency Automatic Structure Lockdown System | Mele Associates | Greg Hansen; Randy Yates | 2014-11-26 | This port was previously removed on 2007-04-05. | ||||
| 3693 | udp | Reserved | 2014-11-26 | This port was previously removed on 2007-04-05. | |||||||
| accuracer | 12007 | tcp | Accuracer Database System Server | Alexander V. Ivanov | Alexander V. Ivanov | 2004-12 | |||||
| accuracer | 12007 | udp | Accuracer Database System Server | Alexander V. Ivanov | Alexander V. Ivanov | 2004-12 | |||||
| presence | Peer-to-peer messaging / Link-Local Messaging | XMPP Registrar | XMPP Registrar | Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html Note: Registration updated May 2007. Was formerly listed as "iChat AV" (Apple's IM client for Mac OS X) with TXT keys: txtvers, port.p2pj, phsh, vc, 1st, AIM, msg, status, last When first shipped in Mac OS X 10.2, iChat's peer-to-peer messaging protocol was created to solve the problem of serverless messaging between peers on the same link. However, there is nothing inherent in the protocol that limits it to being only link-local; it was simply an artifact of iChat in Mac OS X 10.2 using link-local Multicast DNS to discover peers. With the advent of Wide-Area DNS-SD, it is also possible to use iChat's peer-to-peer messaging between machines on different links. |
Contact Information
| Name | Organization | Contact URI | Last Updated |
|---|---|---|---|
| Alexander V. Ivanov | support&aidaim.com | 2004-12 | |
| Greg Hansen | Mele Associates | greg.hansen&meleassociates.com | 2014-11-26 |
| Mele Associates | easl&meleassociates.com | 2014-11-26 | |
| Randy Yates | Digital Signal Labs | yates&digitalsignallabs.com | 2014-11-26 |
| XMPP Registrar | registrar&xmpp.org |