Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-02
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell,
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
904-909 Unassigned
fjicl-tep-c 1904 tcp Fujitsu ICL Terminal Emulator Program C [Bob_Lyon] [Bob_Lyon]
fjicl-tep-c 1904 udp Fujitsu ICL Terminal Emulator Program C [Bob_Lyon] [Bob_Lyon]
m2ua 2904 tcp M2UA [Lyndon_Ong] [Lyndon_Ong]
m2ua 2904 udp M2UA [Lyndon_Ong] [Lyndon_Ong]
m2ua 2904 sctp M2UA [Lyndon_Ong] [Lyndon_Ong]
omnilink-port 3904 tcp Arnet Omnilink Port [Ronen_Shaul] [Ronen_Shaul] 2003-10
omnilink-port 3904 udp Arnet Omnilink Port [Ronen_Shaul] [Ronen_Shaul] 2003-10
ag-swim 5904 tcp Air-Ground SWIM [International_Civil_Aviation_Organisation] [Greg_Saccone] 2022-06-03 Defined TXT keys: AG-SWIM
ag-swim 5904 udp Air-Ground SWIM [International_Civil_Aviation_Organisation] [Greg_Saccone] 2022-06-03 Defined TXT keys: AG-SWIM
ag-swim 5904 sctp Air-Ground SWIM [International_Civil_Aviation_Organisation] [Greg_Saccone] 2022-06-03 Defined TXT keys: AG-SWIM
7904-7912 Unassigned
9027-9049 Unassigned
9904-9908 Unassigned
25904-25953 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Bob_Lyon] Bob Lyon mailto:bl&oasis.icl.co.uk
[Greg_Saccone] Greg Saccone mailto:gregory.t.saccone&boeing.com 2022-08-08
[International_Civil_Aviation_Organisation] International Civil Aviation Organisation (ICAO) mailto:gisinbox&icao.int 2024-11-19
[Lyndon_Ong] Lyndon Ong mailto:LyOng&ciena.com
[Ronen_Shaul] Ronen Shaul mailto:ronen&arnetsystems.com 2003-10