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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dec-notes | 3333 | tcp | DEC Notes | [Kim_Moraros] | [Kim_Moraros] | ||||||
| dec-notes | 3333 | udp | DEC Notes | [Kim_Moraros] | [Kim_Moraros] | ||||||
| elxmgmt | 23333 | tcp | Emulex HBAnyware Remote Management | [Maziar_Tamadon] | [Maziar_Tamadon] | 2007-11-06 | |||||
| elxmgmt | 23333 | udp | Emulex HBAnyware Remote Management | [Maziar_Tamadon] | [Maziar_Tamadon] | 2007-11-06 | |||||
| 33124-33330 | Unassigned | ||||||||||
| diamondport | 33331 | tcp | DiamondCentral Interface | [Edward_Browdy] | [Edward_Browdy] | 2002-07 | |||||
| diamondport | 33331 | udp | DiamondCentral Interface | [Edward_Browdy] | [Edward_Browdy] | 2002-07 | |||||
| 33332 | Unassigned | ||||||||||
| dgi-serv | 33333 | tcp | Digital Gaslight Service | [George_Flanagin] | [George_Flanagin] | 2010-03-02 | |||||
| 33333 | udp | Reserved | |||||||||
| speedtrace | 33334 | tcp | SpeedTrace TraceAgent | [Holger_Heinrich] | [Holger_Heinrich] | 2012-02-01 | |||||
| speedtrace-disc | 33334 | udp | SpeedTrace TraceAgent Discovery | [Holger_Heinrich] | [Holger_Heinrich] | 2012-02-01 | |||||
| 33335-33433 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Edward_Browdy] | Edward Browdy | mailto:ebrowdy&cryptek.com | 2002-07 |
| [George_Flanagin] | George Flanagin | mailto:gflanagi&richmond.edu | 2010-10-30 |
| [Holger_Heinrich] | Holger Heinrich | mailto:holger2222&googlemail.com | 2012-02-01 |
| [Kim_Moraros] | Kim Moraros | mailto:moraros&via.enet.dec.com | |
| [Maziar_Tamadon] | Maziar Tamadon | mailto:maziar.tamadon&emulex.com | 2007-11-06 |