Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-11
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
914c-g 211 tcp Texas Instruments 914C/G Terminal

IANA assigned this well-formed service name as a replacement for "914c/g".
[Bill_Harrell] [Bill_Harrell]
914c/g 211 tcp Texas Instruments 914C/G Terminal [Bill_Harrell] [Bill_Harrell] This entry is an alias to "914c-g". This entry is now historic, not usable for use with many common service discovery mechanisms.
914c-g 211 udp Texas Instruments 914C/G Terminal

IANA assigned this well-formed service name as a replacement for "914c/g".
[Bill_Harrell] [Bill_Harrell]
914c/g 211 udp Texas Instruments 914C/G Terminal [Bill_Harrell] [Bill_Harrell] This entry is an alias to "914c-g". This entry is now historic, not usable for use with many common service discovery mechanisms.
914 tcp Reserved
rift-lies 914 udp Routing in Fat Trees Link Information Element [IESG] [IETF_Chair] 2023-02-17 2024-06-07 [RFC9692]
elm-momentum 1914 tcp Elm-Momentum [Willie_Wu] [Willie_Wu]
elm-momentum 1914 udp Elm-Momentum [Willie_Wu] [Willie_Wu]
gamelobby 2914 tcp Game Lobby [Paul_Ford_Hutchinson] [Paul_Ford_Hutchinson]
gamelobby 2914 udp Game Lobby [Paul_Ford_Hutchinson] [Paul_Ford_Hutchinson]
listcrt-port-2 3914 tcp ListCREATOR Port 2 [Tomokazu_Asai] [Tomokazu_Asai] 2003-11
listcrt-port-2 3914 udp ListCREATOR Port 2 [Tomokazu_Asai] [Tomokazu_Asai] 2003-11
bones 4914 tcp Bones Remote Control [Andreas_Foedrowitz] [Andreas_Foedrowitz] 2008-06-18
bones 4914 udp Bones Remote Control [Andreas_Foedrowitz] [Andreas_Foedrowitz] 2008-06-18
ipsdtls 5914 tcp Security for Internet Protocol Suite [International_Civil_Aviation_Organisation] [Nathan_Lackey] 2024-11-19 Defined TXT keys: IPSDTLS
ipsdtls 5914 udp Security for Internet Protocol Suite [International_Civil_Aviation_Organisation] [Nathan_Lackey] 2024-11-19 Defined TXT keys: IPSDTLS
ipsdtls 5914 sctp Security for Internet Protocol Suite [International_Civil_Aviation_Organisation] [Nathan_Lackey] 2024-11-19 Defined TXT keys: IPSDTLS
7914-7931 Unassigned
8914-8936 Unassigned
49002-49149 Unassigned
est-coaps udp EST over secure CoAP (EST-coaps) [Toerless_Eckert_3] [Toerless_Eckert_3] 2022-05-03 2022-05-04 [RFC9148]. Defined TXT keys: None
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 Organization Contact URI Last Updated
[Andreas_Foedrowitz] Andreas Foedrowitz mailto:andreas.foedrowitz&thomson.net 2008-06-18
[Bill_Harrell] Bill Harrell
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[International_Civil_Aviation_Organisation] International Civil Aviation Organisation (ICAO) mailto:gisinbox&icao.int 2024-11-19
[Nathan_Lackey] Nathan Lackey mailto:nathan.lackey&boeing.com 2024-11-19
[Patrick_Stein] Patrick Stein mailto:Patrick.Stein&jinx.eu 2011-10-24
[Paul_Ford_Hutchinson] Paul Ford-Hutchinson mailto:paulfordh&uk.ibm.com 2003-01
[Toerless_Eckert_3] Toerless Eckert mailto:tte&cs.fau.de 2022-05-03
[Tomokazu_Asai] Tomokazu Asai mailto:asai.tomokazu&pfu.fujitsu.com 2003-11
[Willie_Wu] Willie Wu mailto:willie&mds.com