Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-08-07
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
sgcip | 16950 | udp | Simple Generic Client Interface Protocol | [John_Aquilino] | [John_Aquilino] | ||||||
16951-16990 | Unassigned | ||||||||||
intel-rci-mp | 16991 | tcp | INTEL-RCI-MP | [Jane_Dashevsky] | [Jane_Dashevsky] | ||||||
intel-rci-mp | 16991 | udp | INTEL-RCI-MP | [Jane_Dashevsky] | [Jane_Dashevsky] | ||||||
amt-soap-http | 16992 | tcp | Intel(R) AMT SOAP/HTTP | [David_T_Hines] | [David_T_Hines] | 2005-02 | |||||
amt-soap-http | 16992 | udp | Intel(R) AMT SOAP/HTTP | [David_T_Hines] | [David_T_Hines] | 2005-02 | |||||
amt-soap-https | 16993 | tcp | Intel(R) AMT SOAP/HTTPS | [David_T_Hines] | [David_T_Hines] | 2005-02 | |||||
amt-soap-https | 16993 | udp | Intel(R) AMT SOAP/HTTPS | [David_T_Hines] | [David_T_Hines] | 2005-02 | |||||
amt-redir-tcp | 16994 | tcp | Intel(R) AMT Redirection/TCP | [Nimrod_Diamant] | [Nimrod_Diamant] | 2005-02 | |||||
amt-redir-tcp | 16994 | udp | Intel(R) AMT Redirection/TCP | [Nimrod_Diamant] | [Nimrod_Diamant] | 2005-02 | |||||
amt-redir-tls | 16995 | tcp | Intel(R) AMT Redirection/TLS | [Nimrod_Diamant] | [Nimrod_Diamant] | 2005-02 | |||||
amt-redir-tls | 16995 | udp | Intel(R) AMT Redirection/TLS | [Nimrod_Diamant] | [Nimrod_Diamant] | 2005-02 | |||||
16996-17006 | Unassigned | ||||||||||
18516 | tcp | Reserved | |||||||||
heythings | 18516 | udp | HeyThings Device communicate service | [Guangdong_OPPO_Mobile_Telecommunications_Corp_Ltd] | [Zhai_Zhaoxuan] | 2020-05-13 | Defined TXT keys: heythings | ||||
19316-19397 | Unassigned | ||||||||||
20058-20166 | Unassigned | ||||||||||
tolfab | 20167 | tcp | TOLfab Data Change | [Pierre_Couderc] | [Pierre_Couderc] | 2006-03 | |||||
tolfab | 20167 | udp | TOLfab Data Change | [Pierre_Couderc] | [Pierre_Couderc] | 2006-03 | |||||
20168-20201 | Unassigned | ||||||||||
chlenix | 27016 | tcp | Cloud hosting environment network | [Vlad_Bondarenko] | [Vlad_Bondarenko] | 2024-09-23 | |||||
27016 | udp | Reserved | |||||||||
29119-29166 | Unassigned | ||||||||||
otmp | 29167 | tcp | ObTools Message Protocol | [Paul_Clark] | [Paul_Clark] | 2006-02 | |||||
otmp | 29167 | udp | ObTools Message Protocol | [Paul_Clark] | [Paul_Clark] | 2006-02 | |||||
29168 | tcp | Reserved | |||||||||
29168 | udp | Reserved | |||||||||
sbcap | 29168 | sctp | SBcAP in 3GPP | [GPP_Specifications] | [GPP_Specifications] | 2009-06-11 | |||||
iuhsctpassoc | 29169 | sctp | HNBAP and RUA Common Association | [John_Meredith] | [John_Meredith] | 2009-09-08 | |||||
ka-sddp | 31016 | tcp | Kollective Agent Secure Distributed Delivery Protocol | [Kollective_Technology_Inc] | [John_Wainwright] | 2016-12-11 | |||||
ka-kdp | 31016 | udp | Kollective Agent Kollective Delivery Protocol | [Kollective_Technology_Inc] | [John_Wainwright] | 2016-12-11 | |||||
xqosd | 31416 | tcp | XQoS network monitor | [Joe_Elliott] | [Joe_Elliott] | 2002-06 | |||||
xqosd | 31416 | udp | XQoS network monitor | [Joe_Elliott] | [Joe_Elliott] | 2002-06 | |||||
31458-31619 | Unassigned | ||||||||||
lm-mon | 31620 | tcp | lm mon | [System_Administrator] | [System_Administrator] | 2003-06 | |||||
lm-mon | 31620 | udp | lm mon | [System_Administrator] | [System_Administrator] | 2003-06 | |||||
31621-31684 | Unassigned | ||||||||||
dsx-monitor | 31685 | tcp | DS Expert Monitor IANA assigned this well-formed service name as a replacement for "dsx_monitor". |
[John_Lowery] | [John_Lowery] | 2008-08-21 | |||||
dsx_monitor | 31685 | tcp | DS Expert Monitor | [John_Lowery] | [John_Lowery] | 2008-08-21 | This entry is an alias to "dsx-monitor". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
31685 | udp | Reserved | |||||||||
31686-31764 | Unassigned | ||||||||||
44446-44543 | Unassigned | Known UNAUTHORIZED USE: Ports 44515 & 44516 | |||||||||
jnx-kcsync | tcp | jollys keychain cloud sync protocol | [Patrick_Stein] | [Patrick_Stein] | 2011-10-24 | Defined TXT keys: hash=<40hex characters> salt=<40hex characters> uuid=<40hex characters> Example: hash=5e7580598c0d7064d4fc79faaeb42585e1a675f8 salt=f0164cb3a0c3d7efe75abea8fda86d2d56c8dda9 uuid=db61dc092922252e45bbb264f59147138c7fd5fa |