Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-08-26
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
fln-spx | 221 | tcp | Berkeley rlogind with SPX auth | ||||||||
fln-spx | 221 | udp | Berkeley rlogind with SPX auth | ||||||||
sweetware-apps | 1221 | tcp | SweetWARE Apps | [David_Dunetz] | [David_Dunetz] | ||||||
sweetware-apps | 1221 | udp | SweetWARE Apps | [David_Dunetz] | [David_Dunetz] | ||||||
noaaport | 2210 | tcp | NOAAPORT Broadcast Network | ||||||||
noaaport | 2210 | udp | NOAAPORT Broadcast Network | ||||||||
emwin | 2211 | tcp | EMWIN | [Antonio_Querubin] | [Antonio_Querubin] | 2008-03-10 | |||||
emwin | 2211 | udp | EMWIN | [Antonio_Querubin] | [Antonio_Querubin] | 2008-03-10 | |||||
leecoposserver | 2212 | tcp | LeeCO POS Server Service | [Patrick_Lee] | [Patrick_Lee] | 2008-03-10 | |||||
leecoposserver | 2212 | udp | LeeCO POS Server Service | [Patrick_Lee] | [Patrick_Lee] | 2008-03-10 | |||||
kali | 2213 | tcp | Kali | [Jay_Cotton] | [Jay_Cotton] | ||||||
kali | 2213 | udp | Kali | [Jay_Cotton] | [Jay_Cotton] | ||||||
rpi | 2214 | tcp | RDQ Protocol Interface | [Les_Mather] | [Les_Mather] | 2005-12 | |||||
rpi | 2214 | udp | RDQ Protocol Interface | [Les_Mather] | [Les_Mather] | 2005-12 | |||||
ipcore | 2215 | tcp | IPCore.co.za GPRS | [Administrator] | [Administrator] | 2005-12 | |||||
ipcore | 2215 | udp | IPCore.co.za GPRS | [Administrator] | [Administrator] | 2005-12 | |||||
vtu-comms | 2216 | tcp | VTU data service | [David_Barrass] | [David_Barrass] | 2006-01 | |||||
vtu-comms | 2216 | udp | VTU data service | [David_Barrass] | [David_Barrass] | 2006-01 | |||||
gotodevice | 2217 | tcp | GoToDevice Device Management | [John_Lisek] | [John_Lisek] | 2006-01 | |||||
gotodevice | 2217 | udp | GoToDevice Device Management | [John_Lisek] | [John_Lisek] | 2006-01 | |||||
bounzza | 2218 | tcp | Bounzza IRC Proxy | [Danko_Alexeyev] | [Danko_Alexeyev] | 2006-02 | |||||
bounzza | 2218 | udp | Bounzza IRC Proxy | [Danko_Alexeyev] | [Danko_Alexeyev] | 2006-02 | |||||
netiq-ncap | 2219 | tcp | NetIQ NCAP Protocol | [Roger_Huebner] | [Roger_Huebner] | 2010-08-25 | |||||
netiq-ncap | 2219 | udp | NetIQ NCAP Protocol | [Roger_Huebner] | [Roger_Huebner] | 2010-08-25 | |||||
ethernet-ip-s | 2221 | tcp | EtherNet/IP over TLS | [ODVA_Inc] | [Brian_Batke_3] | 2015-05-28 | |||||
ethernet-ip-s | 2221 | udp | EtherNet/IP over DTLS | [ODVA_Inc] | [Brian_Batke_3] | 2015-05-28 | |||||
xnm-clear-text | 3221 | tcp | XML NM over TCP | [Mark_Trostler] | [Mark_Trostler] | ||||||
xnm-clear-text | 3221 | udp | XML NM over TCP | [Mark_Trostler] | [Mark_Trostler] | ||||||
3exmp | 5221 | tcp | 3eTI Extensible Management Protocol for OAMP | [Bill_Rettig] | [Bill_Rettig] | 2010-05-19 | |||||
5221 | udp | Reserved | |||||||||
6210-6221 | Unassigned | ||||||||||
9218-9221 | Unassigned | ||||||||||
avdecc | 17221 | tcp | IEEE 1722.1 AVB Discovery, Enumeration, Connection management, and Control | [IEEE_1722_1] | [Jeffrey_Daniel_Koftinoff] | 2011-11-01 | |||||
avdecc | 17221 | udp | IEEE 1722.1 AVB Discovery, Enumeration, Connection management, and Control | [IEEE_1722_1] | [Jeffrey_Daniel_Koftinoff] | 2011-11-01 | |||||
19221-19282 | Unassigned | ||||||||||
20203-20221 | Unassigned | ||||||||||
aigairserver | 21221 | tcp | Services for Air Server | [AIG_S.L.] | [Edelmiro_Gonzalez_Martinez] | 2017-03-16 | |||||
21221 | udp | Reserved | |||||||||
22006-22124 | Unassigned | ||||||||||
dcap | 22125 | tcp | dCache Access Protocol | [Christoph_Anton_Mitt] | [Christoph_Anton_Mitt] | 2009-03-10 | |||||
22125 | udp | Reserved | |||||||||
22126-22127 | Unassigned | ||||||||||
gsidcap | 22128 | tcp | GSI dCache Access Protocol | [Christoph_Anton_Mitt] | [Christoph_Anton_Mitt] | 2009-03-10 | |||||
22128 | udp | Reserved | |||||||||
22129-22221 | Unassigned |