Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 22128 | udp | Reserved | |||||||||
| 22129-22221 | Unassigned | ||||||||||
| 28120-28199 | Unassigned | ||||||||||
| 32812-32895 | Unassigned | ||||||||||
| 33061-33122 | Unassigned | ||||||||||
| aurora-balaena | 33123 | tcp | Aurora (Balaena Ltd) | [Andrew_Mather] | [Andrew_Mather] | 2008-02-14 | |||||
| aurora-balaena | 33123 | udp | Aurora (Balaena Ltd) | [Andrew_Mather] | [Andrew_Mather] | 2008-02-14 | |||||
| 33124-33330 | Unassigned | ||||||||||
| 36412 | tcp | Reserved | |||||||||
| 36412 | udp | Reserved | |||||||||
| s1-control | 36412 | sctp | S1-Control Plane (3GPP) | [Kimmo_Kymalainen] | [Kimmo_Kymalainen] | 2009-09-01 | |||||
| 38412 | tcp | Reserved | |||||||||
| 38412 | udp | Reserved | |||||||||
| ng-control | 38412 | sctp | NG Control Plane (3GPP) | [Luis_Lopes] | [Luis_Lopes] | 2017-05-18 | 2017-05-19 | ||||
| 41112-41120 | Unassigned | ||||||||||
| tentacle | 41121 | tcp | Tentacle Server | [Sancho_Lerena] | [Sancho_Lerena] | 2009-06-02 | |||||
| 41121 | udp | Reserved | |||||||||
| 41122-41229 | Unassigned | ||||||||||
| z-wave-s | 41230 | tcp | Z-Wave Protocol over SSL/TLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 | |||||
| z-wave-s | 41230 | udp | Z-Wave Protocol over DTLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 | |||||
| 41231-41793 | Unassigned | ||||||||||
| 43442-44122 | Unassigned | ||||||||||
| z-wave-tunnel | 44123 | tcp | Z-Wave Secure Tunnel | [Sigma_Designs_Inc] | [Anders_Brandt_3] | 2012-10-12 | 2015-06-26 | ||||
| 44123 | udp | Reserved | |||||||||
| 44124-44320 | Unassigned | ||||||||||
| 48051-48127 | Unassigned | ||||||||||
| isnetserv | 48128 | tcp | Image Systems Network Services | [Bengt_Gustafsson] | [Bengt_Gustafsson] | 2006-05 | |||||
| isnetserv | 48128 | udp | Image Systems Network Services | [Bengt_Gustafsson] | [Bengt_Gustafsson] | 2006-05 | |||||
| blp5 | 48129 | tcp | Bloomberg locator | [Albert_Hou] | [Albert_Hou] | 2006-05 | |||||
| blp5 | 48129 | udp | Bloomberg locator | [Albert_Hou] | [Albert_Hou] | 2006-05 | |||||
| lsys-ezcfg | LinkSys EZ Configuration | [Frank_Zerangue] | [Frank_Zerangue] | Defined TXT keys: model=value (string) serial=value (sring) hwversion=value (string) swversion=value (string) ifversion=value (string) type=value (string) mac=value (12 hex digits) | |||||||
| lsys-oamp | LinkSys Operations, Administration, Management, and Provisioning | [Frank_Zerangue] | [Frank_Zerangue] | Defined TXT keys: model=value (string) serial=value (sring) hwversion=value (string) swversion=value (string) ifversion=value (string) type=value (string) mac=value (12 hex digits) | |||||||
| lumiere | tcp | A protocol to remotely control DMX512 devices over the network | [Gangsta_Ltd] | [Jean-Charles_Boude] | 2011-10-13 | Defined TXT keys: None | |||||
| meshcop-e | udp | Thread Mesh Commissioning Ephemeral-key | [Thread_Group_Inc] | [Esko_Dijk] | 2024-01-22 | Defined TXT keys: TXT records keys, if any, will be defined in Section 8.12 of the Thread Specification. https://www.threadgroup.org/ThreadSpec |