Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-12-20
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
codemeter | 22350 | udp | CodeMeter Standard | [Wolfgang_Voelker] | [Wolfgang_Voelker] | 2007-06 | |||||
codemeter-cmwan | 22351 | tcp | TPC/IP requests of copy protection software to a server | [WIBU-SYSTEMS_AG] | [Wolfgang_Völker_2] | 2013-06-25 | |||||
22351 | udp | Reserved | |||||||||
22352-22536 | Unassigned | ||||||||||
caldsoft-backup | 22537 | tcp | CaldSoft Backup server file transfer | [CaldSoft] | [Mark_Caldwell] | 2011-08-12 | |||||
22537 | udp | Reserved | |||||||||
22538-22554 | Unassigned | ||||||||||
vocaltec-wconf | 22555 | tcp | Vocaltec Web Conference | [Scott_Petrack] | [Scott_Petrack] | ||||||
vocaltec-phone | 22555 | udp | Vocaltec Internet Phone | [Scott_Petrack] | [Scott_Petrack] | ||||||
22556-22762 | Unassigned | ||||||||||
talikaserver | 22763 | tcp | Talika Main Server | [Laxman_C_Marathe] | [Laxman_C_Marathe] | 2006-12 | |||||
talikaserver | 22763 | udp | Talika Main Server | [Laxman_C_Marathe] | [Laxman_C_Marathe] | 2006-12 | |||||
22764-22799 | Unassigned | ||||||||||
aws-brf | 22800 | tcp | Telerate Information Platform LAN | [Timo_Sivonen] | [Timo_Sivonen] | ||||||
aws-brf | 22800 | udp | Telerate Information Platform LAN | [Timo_Sivonen] | [Timo_Sivonen] | ||||||
22801-22950 | Unassigned | ||||||||||
brf-gw | 22951 | tcp | Telerate Information Platform WAN | [Timo_Sivonen] | [Timo_Sivonen] | ||||||
brf-gw | 22951 | udp | Telerate Information Platform WAN | [Timo_Sivonen] | [Timo_Sivonen] | ||||||
22952-22999 | Unassigned | ||||||||||
hid | 24322 | udp | Transport of Human Interface Device data streams | [Freebox_SAS] | [Nicolas_Pouillon] | 2012-12-14 | |||||
24322 | tcp | Reserved | |||||||||
find | 24922 | tcp | Find Identification of Network Devices | [Jean_Paul_Moreaux] | [Jean_Paul_Moreaux] | ||||||
find | 24922 | udp | Find Identification of Network Devices | [Jean_Paul_Moreaux] | [Jean_Paul_Moreaux] | ||||||
32035-32248 | Unassigned | ||||||||||
t1distproc60 | 32249 | tcp | T1 Distributed Processor | [Peter_Beahan] | [Peter_Beahan] | 2004-11 | |||||
t1distproc60 | 32249 | udp | T1 Distributed Processor | [Peter_Beahan] | [Peter_Beahan] | 2004-11 | |||||
32250-32399 | Unassigned | ||||||||||
33061-33122 | Unassigned | ||||||||||
36422 | tcp | Reserved | |||||||||
36422 | udp | Reserved | |||||||||
x2-control | 36422 | sctp | X2-Control Plane (3GPP) | [Kimmo_Kymalainen] | [Kimmo_Kymalainen] | 2009-09-01 | |||||
38422 | tcp | Reserved | |||||||||
38422 | udp | Reserved | |||||||||
xn-control | 38422 | sctp | Xn Control Plane (3GPP) | [Luis_Lopes] | [Luis_Lopes] | 2017-05-18 | 2017-05-19 | ||||
40001-40022 | Unassigned | ||||||||||
41122-41229 | Unassigned | ||||||||||
43442-44122 | Unassigned | ||||||||||
pmcdproxy | 44322 | tcp | PCP server (pmcd) proxy | [Ken_McDonell] | [Ken_McDonell] | 2003-07 | 2010-12-20 | ||||
pmcdproxy | 44322 | udp | PCP server (pmcd) proxy | [Ken_McDonell] | [Ken_McDonell] | 2003-07 | 2010-12-20 | ||||
jnx-kcsync | tcp | jollys keychain cloud sync protocol | [Patrick_Stein] | [Patrick_Stein] | 2011-10-24 | Defined TXT keys: hash=<40hex characters> salt=<40hex characters> uuid=<40hex characters> Example: hash=5e7580598c0d7064d4fc79faaeb42585e1a675f8 salt=f0164cb3a0c3d7efe75abea8fda86d2d56c8dda9 uuid=db61dc092922252e45bbb264f59147138c7fd5fa |