Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-07-01
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
astronova-main | 2864 | tcp | main 5001 cmd | [AstroNova_Inc] | [Chris_Tate] | 2020-03-03 | |||||
astronova-main | 2864 | udp | main 5001 cmd | [AstroNova_Inc] | [Chris_Tate] | 2020-03-03 | |||||
commplex-link | 5001 | tcp | |||||||||
commplex-link | 5001 | udp | |||||||||
15001 | Unassigned | ||||||||||
icl-twobase2 | 25001 | tcp | icl-twobase2 | [J_A_Sever] | [J_A_Sever] | ||||||
icl-twobase2 | 25001 | udp | icl-twobase2 | [J_A_Sever] | [J_A_Sever] | ||||||
rt-viewer | 35001 | tcp | ReadyTech Viewer | [ReadyTech_Corporation] | [Kevin_Woodward] | 2013-09-13 | |||||
rt-viewer | 35001 | udp | ReadyTech Viewer | [ReadyTech_Corporation] | [Kevin_Woodward] | 2013-09-13 | |||||
asmps | 45001 | tcp | Nuance AutoStore Status Monitoring Protocol (secure data transfer) | [Nuance_Communications_Inc4] | [Andrew_Andrews] | 2011-09-01 | 2017-04-26 | ||||
45001 | udp | Reserved |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Andrew_Andrews] | Andrew Andrews | mailto:Andrew.Andrews&Nuance.com | 2017-04-26 | |
[AstroNova_Inc] | AstroNova, Inc. | mailto:ctate&astronovainc.com | 2020-03-03 | |
[Chris_Tate] | Chris Tate | mailto:ctate&astronovainc.com | 2020-03-03 | |
[J_A_Sever] | J. A. (Tony) Sever | mailto:J.A.Sever&bra0119.wins.icl.co.uk | ||
[Kevin_Woodward] | Kevin Woodward | ReadyTech Corporation | mailto:kwoodward&readytech.com | 2013-09-13 |
[Nuance_Communications_Inc4] | Nuance Communications, Inc. | mailto:dev&nsius.com | 2017-04-26 | |
[ReadyTech_Corporation] | ReadyTech Corporation | mailto:kwoodward&readytech.com | 2013-09-13 |