Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-01
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
http 80 tcp World Wide Web HTTP [IESG] [IETF_Chair] 2021-10-01 [RFC9110] Defined TXT keys: u=<username> p=<password> path=<path to document>
http 80 udp World Wide Web HTTP [IESG] [IETF_Chair] 2021-10-01 [RFC9110] Defined TXT keys: u=<username> p=<password> path=<path to document>
www 80 tcp World Wide Web HTTP [IESG] [IETF_Chair] 2021-10-01 [RFC9110] This is a duplicate of the "http" service and should not be used for discovery purposes.
www 80 udp World Wide Web HTTP [IESG] [IETF_Chair] 2021-10-01 [RFC9110] This is a duplicate of the "http" service and should not be used for discovery purposes.
https 443 tcp http protocol over TLS/SSL [IESG] [IETF_Chair] 2021-10-01 [RFC9110]
https 443 udp http protocol over TLS/SSL [IESG] [IETF_Chair] 2021-10-01 [RFC9110]
xact-backup 911 tcp xact-backup [Bill_Carroll] [Bill_Carroll]
xact-backup 911 udp xact-backup [Bill_Carroll] [Bill_Carroll]
mtp 1911 tcp Starlight Networks Multimedia Transport Protocol [Bruce_Lieberman] [Bruce_Lieberman]
mtp 1911 udp Starlight Networks Multimedia Transport Protocol [Bruce_Lieberman] [Bruce_Lieberman]
blockade 2911 tcp Blockade [Blockade] [Blockade]
blockade 2911 udp Blockade [Blockade] [Blockade]
prnstatus 3911 tcp Printer Status Port [Brett_Green] [Brett_Green] 2003-11
prnstatus 3911 udp Printer Status Port [Brett_Green] [Brett_Green] 2003-11
4903-4911 Unassigned
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
manyone-xml 8911 tcp manyone-xml [Matt_King] [Matt_King] 2002-04
manyone-xml 8911 udp manyone-xml [Matt_King] [Matt_King] 2002-04
9108-9110 Unassigned
hexxorecore 9111 tcp Multiple Purpose, Distributed Message Bus [Hexxore] [Patrick_Roozeboom] 2018-07-31
hexxorecore 9111 udp Multiple Purpose, Distributed Message Bus [Hexxore] [Patrick_Roozeboom] 2018-07-31
9112-9118 Unassigned
mxit 9119 tcp MXit Instant Messaging [Marnus_Freeman] [Marnus_Freeman] 2006-02
mxit 9119 udp MXit Instant Messaging [Marnus_Freeman] [Marnus_Freeman] 2006-02
sype-transport 9911 tcp SYPECom Transport Protocol [Sylvain_Pedneault] [Sylvain_Pedneault] 2003-03
sype-transport 9911 udp SYPECom Transport Protocol [Sylvain_Pedneault] [Sylvain_Pedneault] 2003-03
29001-29117 Unassigned
29118 tcp Reserved
29118 udp Reserved
sgsap 29118 sctp SGsAP in 3GPP [_3GPP_Specifications] [_3GPP_Specifications] 2009-06-11
29119-29166 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Bill_Carroll] Bill Carroll mailto:billc&xactlabs.com
[Blockade] VP - Research & Development mailto:development&blockade.com
[Brett_Green] Brett Green mailto:brett_green&hp.com 2003-11
[Bruce_Lieberman] Bruce Lieberman mailto:brucel&iserver.starlight.com
[Eivan_Cerasi] Eivan Cerasi mailto:eivan.cerasi&eurocontrol.int 2022-08-08
[_3GPP_Specifications] Dongwook Kim 3GPP Specifications Manager mailto:dongwook.kim&etsi.org 2026-01-23
[Greg_Saccone] Greg Saccone mailto:gregory.t.saccone&boeing.com 2022-08-08
[Hexxore] Hexxore mailto:info&hexxore.nl 2018-07-31
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Justin_Yu] Justin Yu mailto:yyu&mitre.org 2011-05-25
[Marnus_Freeman] Marnus Freeman mailto:marnus&swistgroup.com 2006-02
[Matt_King] Matt King mailto:m&manyone.net 2002-04
[Patrick_Roozeboom] Patrick Roozeboom mailto:info&hexxore.nl 2018-07-31
[Sylvain_Pedneault] Sylvain Pedneault mailto:sylvain&sypecom.qc.ca 2003-03