Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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
- [RFC6335]
- 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 [RFC6335]. 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 [RFC6335]. According to Section 8.1.2 of [RFC6335], 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, or the "Expert Review" process, as per [RFC6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC6335]. 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
Plain text
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ieee-mms | 651 | tcp | IEEE MMS | [Curtis_Anderson] | [Curtis_Anderson] | ||||||
| ieee-mms | 651 | udp | IEEE MMS | [Curtis_Anderson] | [Curtis_Anderson] | ||||||
| shiva-confsrvr | 1651 | tcp | shiva_confsrvr IANA assigned this well-formed service name as a replacement for "shiva_confsrvr". |
[Mike_Horowitz] | [Mike_Horowitz] | ||||||
| shiva_confsrvr | 1651 | tcp | shiva_confsrvr | [Mike_Horowitz] | [Mike_Horowitz] | This entry is an alias to "shiva-confsrvr". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
| shiva-confsrvr | 1651 | udp | shiva_confsrvr IANA assigned this well-formed service name as a replacement for "shiva_confsrvr". |
[Mike_Horowitz] | [Mike_Horowitz] | ||||||
| shiva_confsrvr | 1651 | udp | shiva_confsrvr | [Mike_Horowitz] | [Mike_Horowitz] | This entry is an alias to "shiva-confsrvr". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
| ebinsite | 2651 | tcp | EBInSite | [Lefteris_Kalamaras] | [Lefteris_Kalamaras] | ||||||
| ebinsite | 2651 | udp | EBInSite | [Lefteris_Kalamaras] | [Lefteris_Kalamaras] | ||||||
| mdtp | 3232 | tcp | MDT port | 2012-02-21 | [RFC6513] | ||||||
| mdtp | 3232 | udp | MDT port | 2012-02-21 | [RFC6513] | ||||||
| xrpc-registry | 3651 | tcp | XRPC Registry | [Slava_Monich] | [Slava_Monich] | 2003-01 | |||||
| xrpc-registry | 3651 | udp | XRPC Registry | [Slava_Monich] | [Slava_Monich] | 2003-01 | |||||
| mcer-port | 6510 | tcp | MCER Port | [Portnoy_Boxman] | [Portnoy_Boxman] | ||||||
| mcer-port | 6510 | udp | MCER Port | [Portnoy_Boxman] | [Portnoy_Boxman] | ||||||
| 6511 | tcp | Reserved | |||||||||
| dccp-udp | 6511 | udp | Datagram Congestion Control Protocol Encapsulation for NAT Traversal | [IESG] | [IETF_Chair] | [RFC6773] | |||||
| 6512-6512 | Unassigned | ||||||||||
| netconf-tls | 6513 | tcp | NETCONF over TLS | [IESG] | [IETF_Chair] | 2024-01-24 | [RFC7589][RFC9918] | ||||
| 6513 | udp | Reserved | |||||||||
| syslog-tls | 6514 | tcp | Syslog over TLS | [RFC5425] | |||||||
| syslog-tls | 6514 | udp | syslog over DTLS | [RFC6012] | |||||||
| syslog-tls | 6514 | dccp | syslog over DTLS | [RFC6012] | |||||||
| elipse-rec | 6515 | tcp | Elipse RPC Protocol | [F_Englert] | [F_Englert] | 2007-09-17 | |||||
| elipse-rec | 6515 | udp | Elipse RPC Protocol | [F_Englert] | [F_Englert] | 2007-09-17 | |||||
| 6516-6542 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Curtis_Anderson] | Curtis Anderson | mailto:canderson&turbolinux.com | ||
| [F_Englert] | Fl√°vio Englert | mailto:flavio&elipse.com.br | 2007-09-17 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Lefteris_Kalamaras] | Lefteris Kalamaras | mailto:lefteris&ebi.com | ||
| [Mike_Horowitz] | Mike Horowitz | mailto:mah&shiva.com | ||
| [Portnoy_Boxman] | Portnoy Boxman | mailto:portnoy_boxman&bmc.com | 2005-01 | |
| [Slava_Monich] | Slava Monich | mailto:Slava.Monich&nokia.com | 2003-01 |