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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| password-chg | 586 | tcp | Password Change | ||||||||
| password-chg | 586 | udp | Password Change | ||||||||
| ibm-abtact | 1586 | tcp | ibm-abtact | [Sandeep_K_Singhal] | [Sandeep_K_Singhal] | ||||||
| ibm-abtact | 1586 | udp | ibm-abtact | [Sandeep_K_Singhal] | [Sandeep_K_Singhal] | ||||||
| netx-agent | 2586 | tcp | NETX Agent | [Brett_Dolecheck] | [Brett_Dolecheck] | ||||||
| netx-agent | 2586 | udp | NETX Agent | [Brett_Dolecheck] | [Brett_Dolecheck] | ||||||
| emprise-lsc | 3586 | tcp | License Server Console | [James_J_Diaz] | [James_J_Diaz] | 2002-08 | |||||
| emprise-lsc | 3586 | udp | License Server Console | [James_J_Diaz] | [James_J_Diaz] | 2002-08 | |||||
| att-mt-sms | 5586 | tcp | Planning to send mobile terminated SMS to the specific port so that the SMS is not visible to the client | [ATT] | [Dhillesh_Sigilipelli] | 2014-08-21 | |||||
| 5586 | udp | Reserved | |||||||||
| 5860-5862 | Unassigned | ||||||||||
| ppsuitemsg | 5863 | tcp | PlanetPress Suite Messeng | [Yannick_Fortin] | [Yannick_Fortin] | 2006-02 | |||||
| ppsuitemsg | 5863 | udp | PlanetPress Suite Messeng | [Yannick_Fortin] | [Yannick_Fortin] | 2006-02 | |||||
| 5864-5867 | Unassigned | ||||||||||
| diameters | 5868 | tcp | Diameter over TLS/TCP | [IESG] | [IETF_Chair] | [RFC6733] | |||||
| 5868 | udp | Reserved | |||||||||
| diameters | 5868 | sctp | Diameter over DTLS/SCTP | [IESG] | [IETF_Chair] | [RFC6733] | |||||
| 5869-5882 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [ATT] | AT&T | mailto:ds978v&att.com | 2014-08-21 | |
| [Brett_Dolecheck] | Brett Dolecheck | mailto:Dolecheck&ipmetrics.com | ||
| [Dhillesh_Sigilipelli] | Dhillesh Sigilipelli | AT&T | mailto:ds978v&att.com | 2014-08-21 |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [James_J_Diaz] | James J. Diaz | mailto:JDiaz&emprisecorporation.com | 2002-08 | |
| [Sandeep_K_Singhal] | Sandeep K. Singhal | mailto:singhal&cs.stanford.edu | ||
| [Yannick_Fortin] | Yannick Fortin | mailto:fortiny&ca.objectiflune.com | 2006-02 |