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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| mngsuite | 9535 | tcp | Management Suite Remote Control | [Trevor_Perkes] | [Trevor_Perkes] | 2010-02-01 | |||||
| mngsuite | 9535 | udp | Management Suite Remote Control | [Trevor_Perkes] | [Trevor_Perkes] | 2010-02-01 | |||||
| laes-bf | 9536 | tcp | Surveillance buffering function | [Glen_Myers] | [Glen_Myers] | 2007-05 | |||||
| laes-bf | 9536 | udp | Surveillance buffering function | [Glen_Myers] | [Glen_Myers] | 2007-05 | |||||
| 9537-9554 | Unassigned | ||||||||||
| trispen-sra | 9555 | tcp | Trispen Secure Remote Access | [Jaco_Botha] | [Jaco_Botha] | 2004-11 | |||||
| trispen-sra | 9555 | udp | Trispen Secure Remote Access | [Jaco_Botha] | [Jaco_Botha] | 2004-11 | |||||
| 9556-9558 | Unassigned | ||||||||||
| p4runtime | 9559 | tcp | P4Runtime gRPC Service | [Open_Networking_Foundation] | [Antonin_Bas] | 2020-09-22 | |||||
| 9559 | udp | Reserved | |||||||||
| 9560-9591 | Unassigned | ||||||||||
| ldgateway | 9592 | tcp | LANDesk Gateway | [Alan_Butt] | [Alan_Butt] | 2006-03 | |||||
| ldgateway | 9592 | udp | LANDesk Gateway | [Alan_Butt] | [Alan_Butt] | 2006-03 | |||||
| cba8 | 9593 | tcp | LANDesk Management Agent (cba8) | [Trevor_Perkes] | [Trevor_Perkes] | 2010-02-01 | |||||
| cba8 | 9593 | udp | LANDesk Management Agent (cba8) | [Trevor_Perkes] | [Trevor_Perkes] | 2010-02-01 | |||||
| msgsys | 9594 | tcp | Message System | [Alan_Butt] | [Alan_Butt] | ||||||
| msgsys | 9594 | udp | Message System | [Alan_Butt] | [Alan_Butt] | ||||||
| pds | 9595 | tcp | Ping Discovery Service | [Alan_Butt] | [Alan_Butt] | ||||||
| pds | 9595 | udp | Ping Discovery Service | [Alan_Butt] | [Alan_Butt] | ||||||
| mercury-disc | 9596 | tcp | Mercury Discovery | [Paul_Mclachlan] | [Paul_Mclachlan] | 2005-11 | |||||
| mercury-disc | 9596 | udp | Mercury Discovery | [Paul_Mclachlan] | [Paul_Mclachlan] | 2005-11 | |||||
| pd-admin | 9597 | tcp | PD Administration | [Duk_Loi] | [Duk_Loi] | 2005-11 | |||||
| pd-admin | 9597 | udp | PD Administration | [Duk_Loi] | [Duk_Loi] | 2005-11 | |||||
| vscp | 9598 | tcp | Very Simple Ctrl Protocol | [Ake_Hedman] | [Ake_Hedman] | 2005-11 | |||||
| vscp | 9598 | udp | Very Simple Ctrl Protocol | [Ake_Hedman] | [Ake_Hedman] | 2005-11 | |||||
| robix | 9599 | tcp | Robix | [Evan_Rosen] | [Evan_Rosen] | 2005-11 | |||||
| robix | 9599 | udp | Robix | [Evan_Rosen] | [Evan_Rosen] | 2005-11 | |||||
| ccnx | 9695 | tcp | Content Centric Networking | [Van_Jacobson_2][Simon_Barber] | [Van_Jacobson_2][Simon_Barber] | 2009-09-29 | |||||
| ccnx | 9695 | udp | Content Centric Networking | [Van_Jacobson_2][Simon_Barber] | [Van_Jacobson_2][Simon_Barber] | 2009-09-29 | |||||
| x510 | 9877 | tcp | The X.510 wrapper protocol | [ITU_TSB_ITU-T_Study_Group_17] | [Erik_Andersen] | 2019-09-30 | [ITU-T X.510 / ISO/IEC 9584-11] | ||||
| sctp-tunneling | 9899 | udp | SCTP TUNNELING | [IESG] | [IETF_Chair] | 2013-04-10 | [RFC6951] | ||||
| apc-9950 | 9950 | tcp | APC 9950 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-9950 | 9950 | udp | APC 9950 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-9951 | 9951 | tcp | APC 9951 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-9951 | 9951 | udp | APC 9951 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-9952 | 9952 | tcp | APC 9952 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-9952 | 9952 | udp | APC 9952 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| acis | 9953 | tcp | 9953 | [Thomas_Guth] | [Thomas_Guth] | 2006-01 | |||||
| acis | 9953 | udp | 9953 | [Thomas_Guth] | [Thomas_Guth] | 2006-01 | |||||
| hinp | 9954 | tcp | HaloteC Instrument Network Protocol | [HaloteC_Instruments] | [Michel_Stam] | 2012-02-07 | |||||
| 9954 | udp | Reserved | |||||||||
| alljoyn-stm | 9955 | tcp | Contact Port for AllJoyn standard messaging | [Qualcomm_Innovation_Center] | [Craig_Dowell] | 2012-03-14 | |||||
| alljoyn-mcm | 9955 | udp | Contact Port for AllJoyn multiplexed constrained messaging | [Qualcomm_Innovation_Center] | [Craig_Dowell] | 2012-03-14 | |||||
| 9956 | tcp | Reserved | |||||||||
| alljoyn | 9956 | udp | Alljoyn Name Service | [Qualcomm_Innovation_Center] | [Craig_Dowell] | 2011-12-21 | |||||
| 9957-9965 | Unassigned | ||||||||||
| palace-4 | 9995 | tcp | Palace-4 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| palace-4 | 9995 | udp | Palace-4 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| weave | 11095 | tcp | Nest device-to-device and device-to-service application protocol | [Nest_Labs_Inc] | [Grant_Erickson] | 2014-01-16 | |||||
| weave | 11095 | udp | Nest device-to-device and device-to-service application protocol | [Nest_Labs_Inc] | [Grant_Erickson] | 2014-01-16 | |||||
| 11752-11795 | Unassigned | ||||||||||
| 13895-13928 | Unassigned | ||||||||||
| sgcip | 16950 | tcp | Simple Generic Client Interface Protocol | [John_Aquilino] | [John_Aquilino] | ||||||
| sgcip | 16950 | udp | Simple Generic Client Interface Protocol | [John_Aquilino] | [John_Aquilino] | ||||||
| 16951-16990 | Unassigned | ||||||||||
| 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 | |||||
| 19195-19219 | Unassigned | ||||||||||
| 19413-19538 | Unassigned | ||||||||||
| fxuptp | 19539 | tcp | FXUPTP | [Keiji_Okuma] | [Keiji_Okuma] | 2005-08 | |||||
| fxuptp | 19539 | udp | FXUPTP | [Keiji_Okuma] | [Keiji_Okuma] | 2005-08 | |||||
| sxuptp | 19540 | tcp | SXUPTP | [Keiji_Okuma] | [Keiji_Okuma] | 2002-08 | |||||
| sxuptp | 19540 | udp | SXUPTP | [Keiji_Okuma] | [Keiji_Okuma] | 2002-08 | |||||
| jcp | 19541 | tcp | JCP Client | [Yuji_Sasaki] | [Yuji_Sasaki] | ||||||
| jcp | 19541 | udp | JCP Client | [Yuji_Sasaki] | [Yuji_Sasaki] | ||||||
| 19542-19787 | Unassigned | ||||||||||
| 22801-22950 | Unassigned | ||||||||||
| brf-gw | 22951 | tcp | Telerate Information Platform WAN | [Timo_Sivonen] | [Timo_Sivonen] | ||||||
| brf-gw | 22951 | udp | Telerate Information Platform WAN | [Timo_Sivonen] | [Timo_Sivonen] | ||||||
| 22952-22999 | Unassigned | ||||||||||
| 23295-23332 | Unassigned | ||||||||||
| 25904-25953 | Unassigned | ||||||||||
| bf-game | 25954 | udp | Bitfighter game server | [Christopher_Eykamp] | [Christopher_Eykamp] | 2012-08-16 | |||||
| 25954 | tcp | Reserved | |||||||||
| bf-master | 25955 | udp | Bitfighter master server | [Christopher_Eykamp] | [Christopher_Eykamp] | 2012-08-16 | |||||
| 25955 | tcp | Reserved | |||||||||
| 25956-25999 | Unassigned | ||||||||||
| 31950-32033 | Unassigned | ||||||||||
| 32812-32895 | Unassigned | ||||||||||
| crestron-ctp | 41795 | tcp | Crestron Terminal Port | [Crestron_Electronics] | [John_Pavlik] | 2003-01 | 2019-10-17 | ||||
| crestron-ctp | 41795 | udp | Crestron Terminal Port | [Crestron_Electronics] | [John_Pavlik] | 2003-01 | 2019-10-17 | ||||
| brski-proxy | tcp | The Bootstrapping Remote Secure Key Infrastructure Proxy | [IESG] | [IETF_Chair] | 2020-04-29 | [RFC8995] | Defined TXT keys: None | ||||
| brski-registrar | tcp | The Bootstrapping Remote Secure Key Infrastructure Registrar | [IESG] | [IETF_Chair] | 2020-04-29 | [RFC8995] | Defined TXT keys: None | ||||
| dccp-ping | dccp | ping/traceroute using DCCP | [Samuel_Jero] | [Samuel_Jero] | 2012-11-14 | 1885957735 | Defined TXT keys: None | ||||
| wot | tcp | W3C WoT Thing Description or Directory | [W3C_Web_of_Things_Working_Group] | [Kazuyuki_Ashimura] | 2022-11-22 | 2022-12-15 |
Defined TXT keys: td: Absolute pathname of the Thing Description of the Thing or Thing Description of the Thing Description Directory. type: Type of the Thing Description, i.e. "Thing" or "Directory". If omitted, the type is assumed to be Thing. scheme: Scheme part of URL. One of the following values can be specified, with the standard registered URI interpretations [RFC7595]: http (HTTP over TCP),https (HTTP over TLS/TCP), coap+tcp (CoAP over TCP), or coaps+tcp (CoAP over TLS/TCP). If omitted, the scheme is assumed to be http. |
||||
| wot | udp | W3C WoT Thing Description or Directory | [W3C_Web_of_Things_Working_Group] | [Kazuyuki_Ashimura] | 2022-11-22 | 2022-12-15 |
Defined TXT keys: td: Absolute pathname of the Thing Description of the Thing or Thing Description of the Thing Description Directory. type: Type of the Thing Description, i.e. "Thing" or "Directory". If omitted, the type is assumed to be Thing. scheme: Scheme part of URL. One of the following values can be specified, with the standard registered URI interpretations [RFC7595]: coap (CoAP over UDP), coaps CoAP over DTLS/UDP. If omitted, the scheme is assumed to be coap. |