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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 9910 | Unassigned | ||||||||||
| sype-transport | 9911 | tcp | SYPECom Transport Protocol | [Sylvain_Pedneault] | [Sylvain_Pedneault] | 2003-03 | |||||
| sype-transport | 9911 | udp | SYPECom Transport Protocol | [Sylvain_Pedneault] | [Sylvain_Pedneault] | 2003-03 | |||||
| 9912-9924 | Unassigned | ||||||||||
| osm-oev | 9991 | tcp | OSM Event Server | [Vinay_Gupta] | [Vinay_Gupta] | 2003-08 | |||||
| osm-oev | 9991 | udp | OSM Event Server | [Vinay_Gupta] | [Vinay_Gupta] | 2003-08 | |||||
| 10991-10999 | 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] | ||||||
| 19021-19190 | Unassigned | ||||||||||
| opsec-uaa | 19191 | tcp | OPSEC UAA | [Reuven_Harrison] | [Reuven_Harrison] | ||||||
| opsec-uaa | 19191 | udp | OPSEC UAA | [Reuven_Harrison] | [Reuven_Harrison] | ||||||
| 19192-19193 | Unassigned | ||||||||||
| ua-secureagent | 19194 | tcp | UserAuthority SecureAgent | [Reuven_Harrison_2] | [Reuven_Harrison_2] | 2003-01 | |||||
| ua-secureagent | 19194 | udp | UserAuthority SecureAgent | [Reuven_Harrison_2] | [Reuven_Harrison_2] | 2003-01 | |||||
| 19195-19219 | Unassigned | ||||||||||
| 19791-19997 | Unassigned | ||||||||||
| 21591-21799 | Unassigned | ||||||||||
| 29001-29117 | Unassigned | ||||||||||
| 29118 | tcp | Reserved | |||||||||
| 29118 | udp | Reserved | |||||||||
| sgsap | 29118 | sctp | SGsAP in 3GPP | [_3GPP_Specifications] | [_3GPP_Specifications] | 2009-06-11 | |||||
| 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 | [_3GPP_Specifications] | [_3GPP_Specifications] | 2009-06-11 | |||||
| iuhsctpassoc | 29169 | sctp | HNBAP and RUA Common Association | [Dongwook_Kim] | [Dongwook_Kim] | 2009-09-08 | 2026-01-23 | ||||
| 29170-29998 | Unassigned | ||||||||||
| 33891-34248 | Unassigned | ||||||||||
| noit-transport | 43191 | tcp | Reconnoiter Agent Data Transport | [Theo_Schlossnagle] | [Theo_Schlossnagle] | 2009-05-19 | |||||
| 43191 | udp | Reserved | |||||||||
| 49002-49149 | Unassigned | ||||||||||
| inspider | 49150 | tcp | InSpider System | [AnRobot] | [Zhang_Xinnan] | 2017-11-06 | |||||
| 49150 | udp | Reserved | |||||||||
| 49151 | Reserved | 2024-12-20 | [RFC6335] | ||||||||
| core-rd | tcp | Resource Directory accessed using CoAP over TCP | [IESG] | [IETF_Chair] | 2021-03-16 | [RFC9176] | Defined TXT keys: None | ||||
| core-rd | udp | Resource Directory accessed using CoAP | [IESG] | [IETF_Chair] | 2021-03-16 | [RFC9176] | Defined TXT keys: None | ||||
| core-rd-tls | tcp | Resource Directory accessed using CoAP over TLS | [IESG] | [IETF_Chair] | 2021-03-16 | 2022-04-14 | [RFC9176] | Defined TXT keys: None | |||
| core-rd-dtls | udp | Resource Directory accessed using CoAP over DTLS | [IESG] | [IETF_Chair] | 2021-03-16 | [RFC9176] | Defined TXT keys: None | ||||
| est-coaps | udp | EST over secure CoAP (EST-coaps) | [Toerless_Eckert_3] | [Toerless_Eckert_3] | 2022-05-03 | 2022-05-04 | [RFC9148]. Defined TXT keys: None | ||||
| 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 |