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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| iclcnet-locate | 886 | tcp | ICL coNETion locate server | [Bob_Lyon] | [Bob_Lyon] | ||||||
| iclcnet-locate | 886 | udp | ICL coNETion locate server | [Bob_Lyon] | [Bob_Lyon] | ||||||
| leoip | 1886 | tcp | Leonardo over IP | [Dietmar_Finkler] | [Dietmar_Finkler] | ||||||
| leoip | 1886 | udp | Leonardo over IP | [Dietmar_Finkler] | [Dietmar_Finkler] | ||||||
| responselogic | 2886 | tcp | RESPONSELOGIC | [Bruce_Casey] | [Bruce_Casey] | ||||||
| responselogic | 2886 | udp | RESPONSELOGIC | [Bruce_Casey] | [Bruce_Casey] | ||||||
| nei-management | 3886 | tcp | NEI management port | [Kevin_Murphy_2] | [Kevin_Murphy_2] | 2003-10 | |||||
| nei-management | 3886 | udp | NEI management port | [Kevin_Murphy_2] | [Kevin_Murphy_2] | 2003-10 | |||||
| 4886-4887 | Unassigned | ||||||||||
| 7881-7886 | Unassigned | ||||||||||
| 38801-38864 | Unassigned | ||||||||||
| secrmmsafecopya | 38865 | tcp | Security approval process for use of the secRMM SafeCopy program | [Squadra_Technologies] | [Anthony_LaMark] | 2012-03-14 | |||||
| 38865 | udp | Reserved | |||||||||
| 38866-39062 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Anthony_LaMark] | Anthony LaMark | Squadra Technologies | mailto:anthony&squadratechnologies.com | 2012-03-14 |
| [Bob_Lyon] | Bob Lyon | mailto:bl&oasis.icl.co.uk | ||
| [Bruce_Casey] | Bruce Casey | mailto:bcasey&responselogic.com | ||
| [Dietmar_Finkler] | Dietmar Finkler | mailto:d.finkler&hermstedt.de | ||
| [Kevin_Murphy_2] | Kevin Murphy | mailto:kevin.murphy&networkengines.com | 2003-10 | |
| [Squadra_Technologies] | Squadra Technologies | mailto:anthony&squadratechnologies.com | 2012-03-14 |