Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-07
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
apex-edge 913 tcp APEX endpoint-relay service [RFC3340]
apex-edge 913 udp APEX endpoint-relay service [RFC3340]
armadp 1913 tcp armadp [Kevin_Welton] [Kevin_Welton]
armadp 1913 udp armadp [Kevin_Welton] [Kevin_Welton]
boosterware 2913 tcp Booster Ware [Ido_Ben_David] [Ido_Ben_David]
boosterware 2913 udp Booster Ware [Ido_Ben_David] [Ido_Ben_David]
listcrt-port 3913 tcp ListCREATOR Port [Tomokazu_Asai] [Tomokazu_Asai] 2003-11
listcrt-port 3913 udp ListCREATOR Port [Tomokazu_Asai] [Tomokazu_Asai] 2003-11
dots-signal 4646 tcp Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Protocol. The service name is used to construct the SRV service names "_dots-signal._udp" and "_dots-signal._tcp" for discovering DOTS servers used to establish DOTS signal channel. [IESG] [IETF_Chair] 2020-01-16 2021-06-14 [RFC8973][RFC9132]
dots-signal 4646 udp Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Protocol. The service name is used to construct the SRV service names "_dots-signal._udp" and "_dots-signal._tcp" for discovering DOTS servers used to establish DOTS signal channel. [IESG] [IETF_Chair] 2020-01-16 2021-06-14 [RFC8973][RFC9132]
lutcp 4913 tcp LUTher Control Protocol [Markus_Loeffler] [Markus_Loeffler] 2007-07-03
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
qo-secure 7913 tcp QuickObjects secure port [Jonas_Bovin] [Jonas_Bovin]
qo-secure 7913 udp QuickObjects secure port [Jonas_Bovin] [Jonas_Bovin]
dragonfly 8913 tcp Dragonfly System Service [Paul_Hodara] [Paul_Hodara] 2005-11
dragonfly 8913 udp Dragonfly System Service [Paul_Hodara] [Paul_Hodara] 2005-11
9124-9130 Unassigned
dddp 9131 tcp Dynamic Device Discovery [Shane_Dick] [Shane_Dick] 2005-08
dddp 9131 udp Dynamic Device Discovery [Shane_Dick] [Shane_Dick] 2005-08
9132-9159 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[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
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Ido_Ben_David] Ido Ben-David mailto:dgntcom&netvision.net.il
[Jonas_Bovin] Jonas Bovin mailto:jonas.bovin&quickobjects.com
[Justin_Yu] Justin Yu mailto:yyu&mitre.org 2011-05-25
[Kevin_Welton] Kevin Welton mailto:Kevin.Welton&armltd.co.uk
[Markus_Loeffler] Markus Loeffler mailto:markus.loeffler&thomson.net 2009-02-17
[Paul_Hodara] Paul Hodara mailto:phodara&netwave.com 2005-11
[Shane_Dick] Shane Dick mailto:shane.dick&amx.com 2005-08
[Tomokazu_Asai] Tomokazu Asai mailto:asai.tomokazu&pfu.fujitsu.com 2003-11