Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-09-05
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
ideafarm-door | 902 | tcp | self documenting Telnet Door | ||||||||
ideafarm-door | 902 | udp | self documenting Door: send 0x00 for info | ||||||||
fjicl-tep-b | 1902 | tcp | Fujitsu ICL Terminal Emulator Program B | [Bob_Lyon] | [Bob_Lyon] | ||||||
fjicl-tep-b | 1902 | udp | Fujitsu ICL Terminal Emulator Program B | [Bob_Lyon] | [Bob_Lyon] | ||||||
netaspi | 2902 | tcp | NET ASPI | [Johnson_Luo] | [Johnson_Luo] | ||||||
netaspi | 2902 | udp | NET ASPI | [Johnson_Luo] | [Johnson_Luo] | ||||||
itu-bicc-stc | 3097 | sctp | ITU-T Q.1902.1/Q.2150.3 | [Greg_Sidebottom] | [Greg_Sidebottom] | ||||||
nimaux | 3902 | tcp | NIMsh Auxiliary Port | [Paul_B_Finley] | [Paul_B_Finley] | 2003-10 | |||||
nimaux | 3902 | udp | NIMsh Auxiliary Port | [Paul_B_Finley] | [Paul_B_Finley] | 2003-10 | |||||
magiccontrol | 4902 | tcp | magicCONROL RF and Data Interface | [Andreas_Spalenski] | [Andreas_Spalenski] | 2008-11-24 | |||||
4902 | udp | Reserved | |||||||||
5901-5902 | Unassigned | ||||||||||
6902-6923 | Unassigned | ||||||||||
tnos-dp | 7902 | tcp | TNOS shell Protocol | [Rene_Kurt] | [Rene_Kurt] | 2005-08 | |||||
tnos-dp | 7902 | udp | TNOS shell Protocol | [Rene_Kurt] | [Rene_Kurt] | 2005-08 | |||||
8902-8907 | Unassigned | ||||||||||
tambora | 9020 | tcp | TAMBORA | [Jason_van_Zyl] | [Jason_van_Zyl] | 2002-03 | |||||
tambora | 9020 | udp | TAMBORA | [Jason_van_Zyl] | [Jason_van_Zyl] | 2002-03 | |||||
panagolin-ident | 9021 | tcp | Pangolin Identification | [William_Benner_2] | [William_Benner_2] | 2002-03 | |||||
panagolin-ident | 9021 | udp | Pangolin Identification | [William_Benner_2] | [William_Benner_2] | 2002-03 | |||||
paragent | 9022 | tcp | PrivateArk Remote Agent | [Gal_Cucuy] | [Gal_Cucuy] | 2002-03 | |||||
paragent | 9022 | udp | PrivateArk Remote Agent | [Gal_Cucuy] | [Gal_Cucuy] | 2002-03 | |||||
swa-1 | 9023 | tcp | Secure Web Access - 1 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-1 | 9023 | udp | Secure Web Access - 1 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-2 | 9024 | tcp | Secure Web Access - 2 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-2 | 9024 | udp | Secure Web Access - 2 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-3 | 9025 | tcp | Secure Web Access - 3 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-3 | 9025 | udp | Secure Web Access - 3 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-4 | 9026 | tcp | Secure Web Access - 4 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
swa-4 | 9026 | udp | Secure Web Access - 4 | [Tim_McGranaghan] | [Tim_McGranaghan] | ||||||
9027-9049 | Unassigned | ||||||||||
enrp-sctp-tls | 9902 | sctp | enrp/tls server channel | [RFC5353] | |||||||
hip-nat-t | 10500 | udp | HIP NAT-Traversal | [IESG] | [IETF_Chair] | 2020-08-12 | [RFC5770][RFC9028] | ||||
j-link | 19020 | tcp | J-Link TCP/IP Protocol | [SEGGER] | [SEGGER] | ||||||
19020 | udp | Reserved | |||||||||
19021-19190 | Unassigned | ||||||||||
nilinkanalyst | 25902 | tcp | NILinkAnalyst | [Roman_Oliynyk_2] | [Roman_Oliynyk_2] | 2007-08-30 | |||||
nilinkanalyst | 25902 | udp | NILinkAnalyst | [Roman_Oliynyk_2] | [Roman_Oliynyk_2] | 2007-08-30 |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Andreas_Spalenski] | Andreas Spalenski | mailto:andreas.spalenski&trsystems.de | 2008-11-24 | |
[Bob_Lyon] | Bob Lyon | mailto:bl&oasis.icl.co.uk | ||
[Gal_Cucuy] | Gal Cucuy | mailto:galc&cyber-ark.com | 2002-03 | |
[Greg_Sidebottom] | Greg Sidebottom | mailto:gregside&home.com | ||
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Jason_van_Zyl] | Jason van Zyl | mailto:jvanzyl&zenplex.com | 2002-03 | |
[Johnson_Luo] | Johnson Luo | mailto:johnson_luo&mail.sercomm.com.tw | ||
[Paul_B_Finley] | Paul B. Finley | mailto:pfinley&us.ibm.com | 2003-10 | |
[Rene_Kurt] | Rene Kurt | mailto:rene.kurt&adasoft.ch | 2005-08 | |
[Roman_Oliynyk_2] | Roman Oliynyk | mailto:roman&netinst.com | 2007-08-30 | |
[SEGGER] | SEGGER Microcontroller GmbH & Co. KG | mailto:info&segger.com | 2009-01-16 | |
[Tim_McGranaghan] | Tim McGranaghan | mailto:tim_mcgranaghan&mech.disa.mil | ||
[William_Benner_2] | William Benner | mailto:bill&pangolin.com | 2002-03 |