Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-11
- 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]
- 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 process, as documented in [RFC 6335]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535); the different uses of these ranges are described in [RFC 6335]. According to Section 8.1.2 of [RFC 6335], System Ports are assigned by the "IETF Review" or "IESG Approval" procedures described in [RFC 8126]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per [RFC 6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC 6335]. Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration. ************************************************************************ * PLEASE NOTE THE FOLLOWING: * * * * 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. * ************************************************************************
- Request an Assignment
-
[https://www.iana.org/protocols/apply]
- Available Formats
-

CSV
XML
HTML
TXT
| 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
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Alexander_V_Ivanov] | Alexander V. Ivanov | mailto:support&aidaim.com | 2004-12 | |
| [Greg_Hansen] | Greg Hansen | Mele Associates | mailto:greg.hansen&meleassociates.com | 2014-11-26 |
| [Mele_Associates] | Mele Associates | mailto:easl&meleassociates.com | 2014-11-26 | |
| [Randy_Yates] | Randy Yates | Digital Signal Labs | mailto:yates&digitalsignallabs.com | 2014-11-26 |
| [XMPP_Registrar] | XMPP Registrar | mailto:registrar&xmpp.org |