Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-07
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| sonar | 572 | tcp | sonar | [Keith_Moore] | [Keith_Moore] | ||||||
| sonar | 572 | udp | sonar | [Keith_Moore] | [Keith_Moore] | ||||||
| chip-lm | 1572 | tcp | Chipcom License Manager | ||||||||
| chip-lm | 1572 | udp | Chipcom License Manager | ||||||||
| ibp | 2572 | tcp | IBP | [Jonathan_Downes] | [Jonathan_Downes] | ||||||
| ibp | 2572 | udp | IBP | [Jonathan_Downes] | [Jonathan_Downes] | ||||||
| megaregsvrport | 3572 | tcp | Registration Server Port | [Sreenivas_Bagalkote] | [Sreenivas_Bagalkote] | 2002-08 | |||||
| megaregsvrport | 3572 | udp | Registration Server Port | [Sreenivas_Bagalkote] | [Sreenivas_Bagalkote] | 2002-08 | |||||
| tsp | 3653 | tcp | Tunnel Setup Protocol | [Marc_Blanchet] | [Marc_Blanchet] | 2003-01 | [RFC5572] | ||||
| tsp | 3653 | udp | Tunnel Setup Protocol | [Marc_Blanchet] | [Marc_Blanchet] | 2003-01 | [RFC5572] | ||||
| 4571-4572 | Unassigned | ||||||||||
| 5570-5572 | Unassigned | Known UNAUTHORIZED USE on Port 5570 | |||||||||
| ms-licensing | 5720 | tcp | MS-Licensing | [Thomas_Lindeman] | [Thomas_Lindeman] | 2002-11 | |||||
| ms-licensing | 5720 | udp | MS-Licensing | [Thomas_Lindeman] | [Thomas_Lindeman] | 2002-11 | |||||
| dtpt | 5721 | tcp | Desktop Passthru Service | [Dan_Leising] | [Dan_Leising] | 2005-01 | |||||
| dtpt | 5721 | udp | Desktop Passthru Service | [Dan_Leising] | [Dan_Leising] | 2005-01 | |||||
| msdfsr | 5722 | tcp | Microsoft DFS Replication Service | [Guhan_Suriyanarayana] | [Guhan_Suriyanarayana] | 2006-03 | |||||
| msdfsr | 5722 | udp | Microsoft DFS Replication Service | [Guhan_Suriyanarayana] | [Guhan_Suriyanarayana] | 2006-03 | |||||
| omhs | 5723 | tcp | Operations Manager - Health Service | [Gerardo_Dilillo] | [Gerardo_Dilillo] | 2006-08 | |||||
| omhs | 5723 | udp | Operations Manager - Health Service | [Gerardo_Dilillo] | [Gerardo_Dilillo] | 2006-08 | |||||
| omsdk | 5724 | tcp | Operations Manager - SDK Service | [Gerardo_Dilillo] | [Gerardo_Dilillo] | 2006-08 | |||||
| omsdk | 5724 | udp | Operations Manager - SDK Service | [Gerardo_Dilillo] | [Gerardo_Dilillo] | 2006-08 | |||||
| ms-ilm | 5725 | tcp | Microsoft Identity Lifecycle Manager | [Rob_Ward] | [Rob_Ward] | ||||||
| 5725 | udp | Reserved | 2008-05-02 | ||||||||
| ms-ilm-sts | 5726 | tcp | Microsoft Lifecycle Manager Secure Token Service | [Rob_Ward] | [Rob_Ward] | ||||||
| 5726 | udp | Reserved | 2008-05-02 | ||||||||
| asgenf | 5727 | tcp | ASG Event Notification Framework | [Arman_Bedonian] | [Arman_Bedonian] | 2009-07-15 | |||||
| 5727 | udp | Reserved | |||||||||
| io-dist-data | 5728 | tcp | Dist. I/O Comm. Service Data and Control | [Harish_Kuttan] | [Harish_Kuttan] | 2010-03-22 | |||||
| io-dist-group | 5728 | udp | Dist. I/O Comm. Service Group Membership | [Harish_Kuttan] | [Harish_Kuttan] | 2010-03-22 | |||||
| openmail | 5729 | tcp | Openmail User Agent Layer | [OpenMail_Encyclopedi][Don_Loughry] | [OpenMail_Encyclopedi][Don_Loughry] | ||||||
| openmail | 5729 | udp | Openmail User Agent Layer | [OpenMail_Encyclopedi][Don_Loughry] | [OpenMail_Encyclopedi][Don_Loughry] | ||||||
| sztp | tcp | This service name is used to construct the SRV service label "_sztp" for discovering SZTP bootstrap servers. | [IESG] | [IETF_Chair] | 2019-01-17 | [RFC8572] | This protocol uses HTTPS as a substrate. |