Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2025-01-23
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
opsec-ela 18187 udp OPSEC ELA [Alon_Kantor] [Alon_Kantor]
18669-18768 Unassigned
ique 18769 tcp IQue Protocol [Avi_Drissman] [Avi_Drissman] 2002-07
ique 18769 udp IQue Protocol [Avi_Drissman] [Avi_Drissman] 2002-07
18770-18880 Unassigned
18882-18887 Unassigned
19542-19787 Unassigned
iec-104-sec 19998 tcp IEC 60870-5-104 process control - secure [Grant_Gilchrist] [Grant_Gilchrist] 2010-10-18
24387-24464 Unassigned
exoconfig 26487 tcp EXOconfig [Urban_Fosseus] [Urban_Fosseus] 2008-12-24
exoconfig 26487 udp EXOconfig [Urban_Fosseus] [Urban_Fosseus] 2008-12-24
27783-27875 Unassigned
astrolink 27876 tcp Astrolink Protocol [Alanax_Technologies_Inc] [Wesley_Eddy] 2013-01-14
27876 udp Reserved
27877-27998 Unassigned
mtrace 33435 udp IP Multicast Traceroute [IESG] [IETF_Chair] 2017-12-13 2019-08-09 [RFC8487] Known Unauthorized Use on port 33435
38639-38799 Unassigned
43001-43187 Unassigned
44323 udp Unassigned "pcp" assignment withdrawn, moved to port 5351 per RFC6887
dns-push-tls tcp DNS Push Notification Service Type [IESG] [IETF_Chair] 2019-11-25 [RFC8765, Section 6.1] Defined TXT Keys: None

Contact Information

ID Name Organization Contact URI Last Updated
[Alanax_Technologies_Inc] Alanax Technologies, Inc mailto:brian.barritt&alanax.com 2013-01-14
[Alon_Kantor] Alon Kantor mailto:alonk&checkpoint.com
[Avi_Drissman] Avi Drissman mailto:ique-protocol&harrisbaseview.com 2002-07
[Grant_Gilchrist] Grant Gilchrist mailto:grant&enernex.com 2010-10-18
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Urban_Fosseus] Urban Fosseus mailto:urban.fosseus&regin.se 2008-12-24
[Wesley_Eddy] Wesley Eddy Alanax Technologies, Inc mailto:wesley.eddy&alanax.com 2013-01-14