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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| spsc | 478 | tcp | spsc | [Mike_Rieker] | [Mike_Rieker] | ||||||
| spsc | 478 | udp | spsc | [Mike_Rieker] | [Mike_Rieker] | ||||||
| ms-sna-base | 1478 | tcp | ms-sna-base | [Gordon_Mangione] | [Gordon_Mangione] | ||||||
| ms-sna-base | 1478 | udp | ms-sna-base | [Gordon_Mangione] | [Gordon_Mangione] | ||||||
| ssm-cssps | 2478 | tcp | SecurSight Authentication Server (SSL) | ||||||||
| ssm-cssps | 2478 | udp | SecurSight Authentication Server (SSL) | ||||||||
| stun | 3478 | tcp | Session Traversal Utilities for NAT (STUN) port | [IESG] | [IETF_Chair] | 2019-03-28 | [RFC8489] | ||||
| stun | 3478 | udp | Session Traversal Utilities for NAT (STUN) port | [IESG] | [IETF_Chair] | 2019-03-28 | [RFC8489] | ||||
| turn | 3478 | tcp | TURN over TCP | 2019-08-02 | [RFC8656] | ||||||
| turn | 3478 | udp | TURN over UDP | 2019-08-02 | [RFC8656] | ||||||
| stun-behavior | 3478 | tcp | STUN Behavior Discovery over TCP | [RFC5780] | |||||||
| stun-behavior | 3478 | udp | STUN Behavior Discovery over UDP | [RFC5780] | |||||||
| 4775-4783 | Unassigned | ||||||||||
| bfd-multi-ctl | 4784 | tcp | BFD Multihop Control | [Dave_Katz][Dave_Ward] | [Dave_Katz][Dave_Ward] | 2006-02 | |||||
| bfd-multi-ctl | 4784 | udp | BFD Multihop Control | [Dave_Katz][Dave_Ward] | [Dave_Katz][Dave_Ward] | 2006-02 | |||||
| 4785 | tcp | Reserved | |||||||||
| cncp | 4785 | udp | Cisco Nexus Control Protocol | [Joseph_Swaminathan] | [Joseph_Swaminathan] | 2009-04-01 | |||||
| smart-install | 4786 | tcp | Smart Install Service | [Amit_Nigam] | [Amit_Nigam] | 2009-08-24 | |||||
| 4786 | udp | Reserved | |||||||||
| sia-ctrl-plane | 4787 | tcp | Service Insertion Architecture (SIA) Control-Plane | [Shree_Murthy] | [Shree_Murthy] | 2009-10-29 | |||||
| 4787 | udp | Reserved | |||||||||
| xmcp | 4788 | tcp | eXtensible Messaging Client Protocol | [Cisco] | [Glenn_Matthews] | 2011-05-23 | 2011-10-25 | Defined TXT keys: txtvers=1 (as described in the draft) protovers=<comma-separated list of major/minor versions supported> (examples: "protovers=1.0" "protovers=1.1,2.0" | |||
| 4788 | udp | Reserved | |||||||||
| vxlan | 4789 | udp | Virtual eXtensible Local Area Network (VXLAN) | [Lawrence_Kreeger] | [Lawrence_Kreeger] | 2013-04-19 | 2014-06-17 | [RFC7348] | |||
| 4789 | tcp | Reserved | |||||||||
| openit | 7478 | tcp | IT Asset Management | [OpeniT_Inc] | [Monette_Maano] | 2016-11-17 | |||||
| 7478 | udp | Reserved | |||||||||
| 47625-47805 | Unassigned | ||||||||||
| ap | 47806 | tcp | ALC Protocol | [Dave_Robin] | [Dave_Robin] | ||||||
| ap | 47806 | udp | ALC Protocol | [Dave_Robin] | [Dave_Robin] | ||||||
| 47807 | Unassigned | ||||||||||
| bacnet | 47808 | tcp | Building Automation and Control Networks | [Coleman_Brumley] | [Coleman_Brumley] | 2011-02-10 | |||||
| bacnet | 47808 | udp | Building Automation and Control Networks | [Coleman_Brumley] | [Coleman_Brumley] | 2011-02-10 | |||||
| presonus-ucnet | 47809 | udp | PreSonus Universal Control Network Protocol | [PreSonus_Audio_Electronics_Inc] | [Matthias_Juwan] | 2013-07-12 | |||||
| 47809 | tcp | Reserved | |||||||||
| 47810-47999 | Unassigned |