Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-07
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| mftp | 349 | tcp | mftp | [Dave_Feinleib] | [Dave_Feinleib] | ||||||
| mftp | 349 | udp | mftp | [Dave_Feinleib] | [Dave_Feinleib] | ||||||
| sbook | 1349 | tcp | Registration Network Protocol | ||||||||
| sbook | 1349 | udp | Registration Network Protocol | ||||||||
| redstorm-diag | 2349 | tcp | Diagnostics Port IANA assigned this well-formed service name as a replacement for "redstorm_diag". |
[David_Weinstein] | [David_Weinstein] | ||||||
| redstorm_diag | 2349 | tcp | Diagnostics Port | [David_Weinstein] | [David_Weinstein] | This entry is an alias to "redstorm-diag". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
| redstorm-diag | 2349 | udp | Diagnostics Port IANA assigned this well-formed service name as a replacement for "redstorm_diag". |
[David_Weinstein] | [David_Weinstein] | ||||||
| redstorm_diag | 2349 | udp | Diagnostics Port | [David_Weinstein] | [David_Weinstein] | This entry is an alias to "redstorm-diag". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
| chevinservices | 3349 | tcp | Chevin Services | [Gus_McNaughton] | [Gus_McNaughton] | ||||||
| chevinservices | 3349 | udp | Chevin Services | [Gus_McNaughton] | [Gus_McNaughton] | ||||||
| colubris | 3490 | tcp | Colubris Management Port | [Gilbert_Moineau] | [Gilbert_Moineau] | 2002-05 | |||||
| colubris | 3490 | udp | Colubris Management Port | [Gilbert_Moineau] | [Gilbert_Moineau] | 2002-05 | |||||
| swr-port | 3491 | tcp | SWR Port | [Ian_Manning] | [Ian_Manning] | 2002-05 | |||||
| swr-port | 3491 | udp | SWR Port | [Ian_Manning] | [Ian_Manning] | 2002-05 | |||||
| tvdumtray-port | 3492 | tcp | TVDUM Tray Port | [Peter_Boers] | [Peter_Boers] | 2002-05 | |||||
| tvdumtray-port | 3492 | udp | TVDUM Tray Port | [Peter_Boers] | [Peter_Boers] | 2002-05 | |||||
| nut | 3493 | tcp | Network UPS Tools | [Network_UPS_Tools_Project] | [Evgeny_Klimov] | 2002-05 | 2022-05-18 | [RFC9271] | |||
| nut | 3493 | udp | Network UPS Tools | [Network_UPS_Tools_Project] | [Evgeny_Klimov] | 2002-05 | 2020-12-16 | ||||
| ibm3494 | 3494 | tcp | IBM 3494 | [Jeffrey_Pilch] | [Jeffrey_Pilch] | ||||||
| ibm3494 | 3494 | udp | IBM 3494 | [Jeffrey_Pilch] | [Jeffrey_Pilch] | ||||||
| seclayer-tcp | 3495 | tcp | securitylayer over tcp | ||||||||
| seclayer-tcp | 3495 | udp | securitylayer over tcp | ||||||||
| seclayer-tls | 3496 | tcp | securitylayer over tls | [Arno_Hollosi] | [Arno_Hollosi] | 2002-03 | |||||
| seclayer-tls | 3496 | udp | securitylayer over tls | [Arno_Hollosi] | [Arno_Hollosi] | 2002-03 | |||||
| ipether232port | 3497 | tcp | ipEther232Port | [Marcus_Leufgen] | [Marcus_Leufgen] | 2002-05 | |||||
| ipether232port | 3497 | udp | ipEther232Port | [Marcus_Leufgen] | [Marcus_Leufgen] | 2002-05 | |||||
| dashpas-port | 3498 | tcp | DASHPAS user port | [Albrecht_Mayer] | [Albrecht_Mayer] | 2002-05 | |||||
| dashpas-port | 3498 | udp | DASHPAS user port | [Albrecht_Mayer] | [Albrecht_Mayer] | 2002-05 | |||||
| sccip-media | 3499 | tcp | SccIP Media | [David_Yon_2] | [David_Yon_2] | 2002-05 | |||||
| sccip-media | 3499 | udp | SccIP Media | [David_Yon_2] | [David_Yon_2] | 2002-05 | |||||
| fsportmap | 4349 | tcp | File System Port Map | [Ron_Minnich_2] | [Ron_Minnich_2] | ||||||
| fsportmap | 4349 | udp | File System Port Map | [Ron_Minnich_2] | [Ron_Minnich_2] | ||||||
| stuns | 5349 | tcp | Session Traversal Utilities for NAT (STUN) port | [IESG] | [IETF_Chair] | 2019-03-28 | [RFC8489] | ||||
| stuns | 5349 | udp | STUN over DTLS | [IESG] | [IETF_Chair] | 2014-07-03 | [RFC7350] | This service name was initially created by [RFC5389]. | |||
| turns | 5349 | tcp | TURN over TLS | 2019-08-02 | [RFC8656] | ||||||
| turns | 5349 | udp | TURN over DTLS | [IESG] | [IETF_Chair] | 2019-08-02 | [RFC7350] | This service name was initially created by [RFC8656]. | |||
| stun-behaviors | 5349 | tcp | STUN Behavior Discovery over TLS | [RFC5780] | |||||||
| stun-behaviors | 5349 | udp | Reserved for a future enhancement of STUN-BEHAVIOR | [RFC5780] | |||||||
| 6348-6349 | Unassigned | ||||||||||
| 22348-22349 | Unassigned | ||||||||||
| 34568-34961 | Unassigned | ||||||||||
| profinet-rt | 34962 | tcp | PROFInet RT Unicast | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2004-11 | 2026-03-16 | ||||
| profinet-rt | 34962 | udp | PROFInet RT Unicast | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2004-11 | 2026-03-16 | ||||
| profinet-rtm | 34963 | tcp | PROFInet RT Multicast | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2004-11 | 2026-03-16 | ||||
| profinet-rtm | 34963 | udp | PROFInet RT Multicast | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2004-11 | 2026-03-16 | ||||
| profinet-cm | 34964 | tcp | PROFInet Context Manager | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2004-11 | 2026-03-16 | ||||
| profinet-cm | 34964 | udp | PROFInet Context Manager | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2004-11 | 2026-03-16 | ||||
| profinet-cm-sec | 34965 | tcp | PROFINET secure connection management and key provisioning | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2026-03-10 | |||||
| profinet-cm-sec | 34965 | udp | PROFINET secure connection management and key provisioning | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2026-03-10 | |||||
| 34966 | tcp | Reserved | |||||||||
| profinet-rt-sec | 34966 | udp | PROFINET secure real-time data transfer over UDP (unicast and multicast) | [PNO_PROFIBUS_Nutzerorganisation_e.V.] | [Dietmar_Bohn] | 2026-03-10 | |||||
| 34967-34979 | Unassigned | ||||||||||
| ethercat | 34980 | tcp | EtherCAT Port | [Martin_Rostan] | [Martin_Rostan] | 2003-11 | |||||
| ethercat | 34980 | udp | EtherCAT Port | [Martin_Rostan] | [Martin_Rostan] | 2003-11 | |||||
| 34981-34999 | Unassigned |