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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| openremote-ctrl | 8688 | tcp | OpenRemote Controller HTTP/REST | [OpenRemote_Inc] | [Juha_Lindfors] | 2012-12-18 | |||||
| 8688 | udp | Reserved | |||||||||
| 8689-8698 | Unassigned | ||||||||||
| sandpolis | 8768 | tcp | Sandpolis Server | [Tyler_Cook] | [Tyler_Cook] | 2019-11-22 | |||||
| 8768 | udp | Reserved | |||||||||
| tec5-sdctp | 9668 | tcp | tec5 Spectral Device Control Protocol | [Michael_Muth] | [Michael_Muth] | 2009-05-11 | |||||
| tec5-sdctp | 9668 | udp | tec5 Spectral Device Control Protocol | [Michael_Muth] | [Michael_Muth] | 2009-05-11 | |||||
| 11368-11370 | Unassigned | ||||||||||
| 11968-11970 | Unassigned | ||||||||||
| cawas | 12168 | tcp | CA Web Access Service | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
| cawas | 12168 | udp | CA Web Access Service | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
| netserialext4 | 16368 | tcp | Network Serial Extension Ports Four | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
| netserialext4 | 16368 | udp | Network Serial Extension Ports Four | [Michael_J_Hoy] | [Michael_J_Hoy] | ||||||
| 16790-16899 | Unassigned | ||||||||||
| vdmmesh | 18668 | tcp | Manufacturing Execution Systems Mesh Communication | [Van_Doren_MES] | [Edwin_van_de_Burgt] | 2016-10-31 | |||||
| vdmmesh-disc | 18668 | udp | Manufacturing Execution Systems Mesh Communication | [Van_Doren_MES] | [Edwin_van_de_Burgt] | 2016-10-31 | |||||
| 18669-18768 | Unassigned | ||||||||||
| 20168-20201 | Unassigned | ||||||||||
| tcc-http | 24680 | tcp | TCC User HTTP Service | [Brian_Kennedy] | [Brian_Kennedy] | 2006-08 | |||||
| tcc-http | 24680 | udp | TCC User HTTP Service | [Brian_Kennedy] | [Brian_Kennedy] | 2006-08 | |||||
| 24681-24726 | Unassigned | ||||||||||
| 29168 | tcp | Reserved | |||||||||
| 29168 | udp | Reserved | |||||||||
| sbcap | 29168 | sctp | SBcAP in 3GPP | [_3GPP_Specifications] | [_3GPP_Specifications] | 2009-06-11 | |||||
| 31621-31684 | Unassigned | ||||||||||
| dsx-monitor | 31685 | tcp | DS Expert Monitor IANA assigned this well-formed service name as a replacement for "dsx_monitor". |
[John_Lowery] | [John_Lowery] | 2008-08-21 | |||||
| dsx_monitor | 31685 | tcp | DS Expert Monitor | [John_Lowery] | [John_Lowery] | 2008-08-21 | This entry is an alias to "dsx-monitor". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| 31685 | udp | Reserved | |||||||||
| 31686-31764 | Unassigned | ||||||||||
| filenet-tms | 32768 | tcp | Filenet TMS | [Daniel_Whelan] | [Daniel_Whelan] | ||||||
| filenet-tms | 32768 | udp | Filenet TMS | [Daniel_Whelan] | [Daniel_Whelan] | ||||||
| 34568-34961 | Unassigned | ||||||||||
| 36701-36864 | Unassigned | ||||||||||
| kastenxpipe | 36865 | tcp | KastenX Pipe | [Guy_Cheng] | [Guy_Cheng] | ||||||
| kastenxpipe | 36865 | udp | KastenX Pipe | [Guy_Cheng] | [Guy_Cheng] | ||||||
| 36866-37471 | Unassigned | ||||||||||
| 39064-39680 | Unassigned | ||||||||||
| turbonote-1 | 39681 | tcp | TurboNote Default Port | [Peter_Hyde] | [Peter_Hyde] | ||||||
| turbonote-1 | 39681 | udp | TurboNote Default Port | [Peter_Hyde] | [Peter_Hyde] | ||||||
| 39682-39999 | Unassigned | ||||||||||
| 44323 | udp | Unassigned | "pcp" assignment withdrawn, moved to port 5351 per RFC6887 |