Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-04-19
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
http-alt | 591 | tcp | FileMaker, Inc. - HTTP Alternate (see Port 80) | [Clay_Maeckel] | [Clay_Maeckel] | ||||||
http-alt | 591 | udp | FileMaker, Inc. - HTTP Alternate (see Port 80) | [Clay_Maeckel] | [Clay_Maeckel] | ||||||
ncpm-pm | 1591 | tcp | ncpm-pm | [Ted_Power] | [Ted_Power] | ||||||
ncpm-pm | 1591 | udp | ncpm-pm | [Ted_Power] | [Ted_Power] | ||||||
maytagshuffle | 2591 | tcp | Maytag Shuffle | [Ken_Ksiazek] | [Ken_Ksiazek] | ||||||
maytagshuffle | 2591 | udp | Maytag Shuffle | [Ken_Ksiazek] | [Ken_Ksiazek] | ||||||
gtrack-server | 3591 | tcp | LOCANIS G-TRACK Server | ||||||||
gtrack-server | 3591 | udp | LOCANIS G-TRACK Server | ||||||||
l3t-at-an | 4591 | tcp | HRPD L3T (AT-AN) | [Avi_Lior] | [Avi_Lior] | 2009-02-27 | |||||
l3t-at-an | 4591 | udp | HRPD L3T (AT-AN) | [Avi_Lior] | [Avi_Lior] | 2009-02-27 | |||||
ats-atn | 5910 | tcp | Air Traffic Services applications using ATN | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
ats-atn | 5910 | udp | Air Traffic Services applications using ATN | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
cm | 5910 | sctp | Context Management | [Justin_Yu] | [Justin_Yu] | 2011-05-19 | |||||
ats-acars | 5911 | tcp | Air Traffic Services applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
ats-acars | 5911 | udp | Air Traffic Services applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
cpdlc | 5911 | sctp | Controller Pilot Data Link Communication | [Justin_Yu] | [Justin_Yu] | 2011-05-18 | |||||
ais-met | 5912 | tcp | Aeronautical Information Service/Meteorological applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
ais-met | 5912 | udp | Aeronautical Information Service/Meteorological applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
fis | 5912 | sctp | Flight Information Services | [Justin_Yu] | [Justin_Yu] | 2011-05-25 | |||||
aoc-acars | 5913 | tcp | Airline operational communications applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
aoc-acars | 5913 | udp | Airline operational communications applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
ads-c | 5913 | sctp | Automatic Dependent Surveillance | [Justin_Yu] | [Justin_Yu] | 2011-05-25 | |||||
5914-5962 | Unassigned | ||||||||||
9560-9591 | Unassigned | ||||||||||
21591-21799 | Unassigned | ||||||||||
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 |
Contact Information
ID | Name | Contact URI | Last Updated |
---|---|---|---|
[Avi_Lior] | Avi Lior | mailto:avi&bridgewatersystems.com | 2009-02-27 |
[Clay_Maeckel] | Clay Maeckel | mailto:clay&claris.com | 2023-09-12 |
[Eivan_Cerasi] | Eivan Cerasi | mailto:eivan.cerasi&eurocontrol.int | 2022-08-08 |
[Greg_Saccone] | Greg Saccone | mailto:gregory.t.saccone&boeing.com | 2022-08-08 |
[Justin_Yu] | Justin Yu | mailto:yyu&mitre.org | 2011-05-25 |
[Ken_Ksiazek] | Ken Ksiazek | mailto:kksiazek&maytag.com | |
[Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 |
[Ted_Power] | Ted Power | mailto:tedp&hpinpcb.cup.hp.com |