Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-04-12
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
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]
https 443 sctp HTTPS [Randall_Stewart] [Randall_Stewart] 2022-02-07 [RFC9260]
ipps 631 tcp Internet Printing Protocol over HTTPS [IESG] [IETF_Chair] 2018-07-06 [RFC8011]
oob-ws-https 664 tcp DMTF out-of-band secure web services management protocol [Jim_Davis] [Jim_Davis] 2007-06
netconfsoaphttp 832 tcp NETCONF for SOAP over HTTPS [RFC4743]
netconfsoaphttp 832 udp NETCONF for SOAP over HTTPS [RFC4743]
saphostctrls 1129 tcp SAPHostControl over SOAP/HTTPS [Muscarella_Fabrizio] [Muscarella_Fabrizio] 2006-04
saphostctrls 1129 udp SAPHostControl over SOAP/HTTPS [Muscarella_Fabrizio] [Muscarella_Fabrizio] 2006-04
llsurfup-https 1184 tcp LL Surfup HTTPS [Katy_Lynn_McCullough] [Katy_Lynn_McCullough]
llsurfup-https 1184 udp LL Surfup HTTPS [Katy_Lynn_McCullough] [Katy_Lynn_McCullough]
compaq-https 2381 tcp Compaq HTTPS [Scott_Shaffer] [Scott_Shaffer]
compaq-https 2381 udp Compaq HTTPS [Scott_Shaffer] [Scott_Shaffer]
wap-push-https 4036 tcp WAP Push OTA-HTTP secure [Matthieu_Lachance] [Matthieu_Lachance]
wap-push-https 4036 udp WAP Push OTA-HTTP secure [Matthieu_Lachance] [Matthieu_Lachance]
appserv-https 4849 tcp App Server - Admin HTTPS [Sreeram_Duvvuru] [Sreeram_Duvvuru] 2002-04
appserv-https 4849 udp App Server - Admin HTTPS [Sreeram_Duvvuru] [Sreeram_Duvvuru] 2002-04
spss 5443 tcp Pearson HTTPS [Pearson] [Pearson] 2008-01-17
spss 5443 udp Pearson HTTPS [Pearson] [Pearson] 2008-01-17
wbem-https 5989 tcp WBEM CIM-XML (HTTPS) [Jim_Davis] [Jim_Davis]
wbem-https 5989 udp WBEM CIM-XML (HTTPS) [Jim_Davis] [Jim_Davis]
wbem-exp-https 5990 tcp WBEM Export HTTPS [Denise_Eckstein] [Denise_Eckstein] 2004-11
wbem-exp-https 5990 udp WBEM Export HTTPS [Denise_Eckstein] [Denise_Eckstein] 2004-11
sun-sr-https 6443 tcp Service Registry Default HTTPS Domain [Paul_Sterk] [Paul_Sterk] 2006-03
sun-sr-https 6443 udp Service Registry Default HTTPS Domain [Paul_Sterk] [Paul_Sterk] 2006-03
plysrv-https 6771 tcp PolyServe https [Mike_Spitzer] [Mike_Spitzer] 2005-08
plysrv-https 6771 udp PolyServe https [Mike_Spitzer] [Mike_Spitzer] 2005-08
pon-ictp 7202 tcp Inter-Channel Termination Protocol (ICTP) for multi-wavelength PON (Passive Optical Network) systems [Broadband_Forum] [Broadband_Forum] 2017-02-22 2019-12-16 [TR-352][Inter-Channel-Termination protocol (ICTP) is a peer-to-peer protocol with a binary message format that is used by a set of optical line terminal (OLT) channel terminations (CT) comprising a 40-Gigabit-capable next-generation passive optical network (NG-PON2) system to exchange channel profile configuration and status information and to coordinate the operation of tunable optical network units (ONUs) in a multi-wavelength channel environment.]
oracleas-https 7443 tcp Oracle Application Server HTTPS [David_McMarlin] [David_McMarlin] 2006-08
oracleas-https 7443 udp Oracle Application Server HTTPS [David_McMarlin] [David_McMarlin] 2006-08
sun-user-https 7677 tcp Sun App Server - HTTPS [Abhijit_Kumar] [Abhijit_Kumar] 2005-11
sun-user-https 7677 udp Sun App Server - HTTPS [Abhijit_Kumar] [Abhijit_Kumar] 2005-11
synapse-nhttps 8243 tcp Synapse Non Blocking HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-07-10
synapse-nhttps 8243 udp Synapse Non Blocking HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-07-10
pcsync-https 8443 tcp PCsync HTTPS
pcsync-https 8443 udp PCsync HTTPS
https-wmap 8991 tcp webmail HTTPS service [Chris_Newman] [Chris_Newman] 2007-12-03
https-wmap 8991 udp webmail HTTPS service [Chris_Newman] [Chris_Newman] 2007-12-03
armcenterhttps 9295 tcp ARMCenter https Service [Eric_Thiebaut_George] [Eric_Thiebaut_George] 2006-04
armcenterhttps 9295 udp ARMCenter https Service [Eric_Thiebaut_George] [Eric_Thiebaut_George] 2006-04
tungsten-https 9443 tcp WSO2 Tungsten HTTPS [Afkham_Azeez] [Afkham_Azeez] 2006-06
tungsten-https 9443 udp WSO2 Tungsten HTTPS [Afkham_Azeez] [Afkham_Azeez] 2006-06
wso2esb-console 9444 tcp WSO2 ESB Administration Console HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-08-20
wso2esb-console 9444 udp WSO2 ESB Administration Console HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-08-20
amt-soap-https 16993 tcp Intel(R) AMT SOAP/HTTPS [David_T_Hines] [David_T_Hines] 2005-02
amt-soap-https 16993 udp Intel(R) AMT SOAP/HTTPS [David_T_Hines] [David_T_Hines] 2005-02
commtact-https 20003 tcp Commtact HTTPS [Tomas_Svoboda] [Tomas_Svoboda] 2004-12
commtact-https 20003 udp Commtact HTTPS [Tomas_Svoboda] [Tomas_Svoboda] 2004-12
bootstrap tcp Bootstrap service discovery [Pedro_Garcia] [Pedro_Garcia] 2023-03-20 Defined TXT keys: "url": if present, indicates a connection url (i.e. wss://example.com/bootstrap, or https://example.com/bootstrap) to be used by the device for bootstrapping; "namespace": identifies the underlying application-level protocol (should be unique for the application protocol, typically a UUID or a URN)
bootstrap udp Bootstrap service discovery [Pedro_Garcia] [Pedro_Garcia] 2023-03-20 Defined TXT keys: "url": if present, indicates a connection url (i.e. wss://example.com/bootstrap, or https://example.com/bootstrap) to be used by the device for bootstrapping; "namespace": identifies the underlying application-level protocol (should be unique for the application protocol, typically a UUID or a URN)
caldavs tcp Calendaring Extensions to WebDAV (CalDAV) - over TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6764] This is an extension of the https service. Defined TXT keys: path=<context path>
carddavs tcp vCard Extensions to WebDAV (CardDAV) - over TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6352] This is an extension of the https service. Defined TXT keys: path=<context path>
https tcp HTTP over SSL/TLS [Tim_Berners_Lee] [Tim_Berners_Lee] Web browsers like Safari and Internet Explorer (with the Bonjour for Windows plugin) DO NOT browse for DNS-SD service type "_https._tcp" in addition to browsing for "_http._tcp". This is a conscious decision to reduce proliferation of service types, to help keep DNS-SD efficient on the network. Today, if a user types http://www.mybank.com/ into their web browser, the web server automatically redirects the user to https://www.mybank.com/. Rather than having an entirely different DNS-SD service type for https, we recommend using the same redirection mechanism: advertise a plain "http" service, which consists of nothing except an HTTP redirection to the desired "https" URL. Work is currently being done on adding mechanisms to HTTP and TLS to allow the server to tell the client that it needs to activate TLS on the current connection before proceeding. If this becomes widely adopted, it further justifies the decision to not create a separate DNS-SD service type "_https._tcp", because security becomes just another one of the things that is negotiated on a per-connection basis (like content-type negotiation today) rather than being an entirely separate thing.
meshcop udp Thread Mesh Commissioning [Thread_Group_Inc] [Esko_Dijk] 2020-11-20 Defined TXT keys: Thread 1.1 Specification, Section 8.4.1.1.2. https://www.threadgroup.org/ThreadSpec
meshcop-e udp Thread Mesh Commissioning Ephemeral-key [Thread_Group_Inc] [Esko_Dijk] 2024-01-22 Defined TXT keys: TXT records keys, if any, will be defined in Section 8.12 of the Thread Specification. https://www.threadgroup.org/ThreadSpec
mist tcp A Medical Interoperability Service Type, used to identify medical devices providing network interfaces. [Jon_Griffeth] [Jon_Griffeth] 2017-01-12 Defined TXT keys: https://www.praesentia.com/medkit/mist-service-type (dn dt md mf pr sn vn)
pgpkey-https PGP Keyserver using HTTPS [Jeroen_Massar_3] [Jeroen_Massar_3] Defined TXT keys: path=<path on the server where the HKP applications reside> normally: "path=/pks/"
snif-cln tcp End-to-end TLS Relay Client Connection [VESvault_Corp] [Jim_Zubov] 2021-12-15 [https://snif.host/relay-proto#snif-cln] Defined TXT keys: None
snif-fifo tcp End-to-end TLS Relay Cluster [VESvault_Corp] [Jim_Zubov] 2021-12-15 [https://snif.host/relay-proto#snif-fifo] Defined TXT keys: None
snif-srv tcp End-to-end TLS Relay Service Connection [VESvault_Corp] [Jim_Zubov] 2021-12-29 [https://snif.host/relay-proto#snif-srv] Defined TXT keys: None
sztp tcp This service name is used to construct the SRV service label "_sztp" for discovering SZTP bootstrap servers. [IESG] [IETF_Chair] 2019-01-17 [RFC8572] This protocol uses HTTPS as a substrate.
timezones tcp Time Zone Data Distribution Service - over TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the https service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
vapix-http tcp Indicator for VAPIX support over HTTP [Axis_Communications] [Christian_Storm] 2023-04-18 Defined TXT keys: https://help.axis.com/en-us/axis-os#axis-bonjour-implementation
vapix-https tcp Indicator for VAPIX support over HTTPS [Axis_Communications] [Christian_Storm] 2023-04-18 Defined TXT keys: https://help.axis.com/en-us/axis-os#axis-bonjour-implementation
wdp tcp Windows Device Portal [Microsoft_Corporation_5] [Hirsch_Singhal] 2016-03-03 Defined TXT keys: D (device type), S (https port), A (architecture), T (tags)
wot tcp W3C WoT Thing Description or Directory [W3C_Web_of_Things_Working_Group] [Kazuyuki_Ashimura] 2022-11-22 2022-12-15

Defined TXT keys:

td: Absolute pathname of the Thing Description of the Thing or Thing Description of the Thing Description Directory.

type: Type of the Thing Description, i.e. "Thing" or "Directory". If omitted, the type is assumed to be Thing.

scheme: Scheme part of URL. One of the following values can be specified, with the standard registered URI interpretations [RFC7595]: http (HTTP over TCP),https (HTTP over TLS/TCP), coap+tcp (CoAP over TCP), or coaps+tcp (CoAP over TLS/TCP). If omitted, the scheme is assumed to be http.

Contact Information

ID Name Organization Contact URI Last Updated
[Abhijit_Kumar] Abhijit Kumar mailto:as-iana-ports&sun.com 2005-11
[Afkham_Azeez] Afkham Azeez mailto:azeez&wso2.com 2006-06
[Axis_Communications] Axis Communications mailto:christnn&axis.com 2023-04-18
[Broadband_Forum] Broadband Forum mailto:help&broadband-forum.org 2020-03-17
[Chris_Newman] Chris Newman mailto:chris.newman&oracle.com 2017-01-26
[Christian_Storm] Christian Storm Axis Communications mailto:christnn&axis.com 2023-04-18
[David_McMarlin] David McMarlin mailto:david.mcmarlin&oracle.com 2006-08
[David_T_Hines] David T. Hines mailto:david.hines&intel.com 2005-02
[Denise_Eckstein] Denise Eckstein mailto:denise.eckstein&hp.com 2004-11
[Eric_Thiebaut_George] Eric Thiebaut-George mailto:erict&aurema.com 2006-04
[Esko_Dijk] Esko Dijk Thread Group, Inc. mailto:esko.dijk&iotconsultancy.nl 2024-01-22
[Hirsch_Singhal] Hirsch Singhal Microsoft Corporation mailto:hirsin&microsoft.com 2016-03-03
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jeroen_Massar_3] Jeroen Massar mailto:jeroen&unfix.org
[Jim_Davis] Jim Davis mailto:jim.davis&wbemsolutions.com 2007-06
[Jim_Zubov] Jim Zubov VESvault Corp mailto:jz&vesvault.com 2021-12-29
[Jon_Griffeth] Jon Griffeth mailto:griffeth&praesentia.com 2017-01-12
[Katy_Lynn_McCullough] Katy Lynn McCullough mailto:KatyM&laplink.com
[Kazuyuki_Ashimura] Kazuyuki Ashimura mailto:ashimura&w3.org 2022-11-22
[Matthieu_Lachance] Matthieu Lachance mailto:matthieu.lachance&openwave.com
[Microsoft_Corporation_5] Microsoft Corporation mailto:hirsin&microsoft.com 2016-03-03
[Mike_Spitzer] Mike Spitzer mailto:mjs&polyserve.com 2005-08
[Muscarella_Fabrizio] Muscarella Fabrizio mailto:fabrizio.muscarella&sap.com 2006-04
[Paul_Sterk] Paul Sterk mailto:paul.sterk&sun.com 2006-03
[Pearson] Pearson mailto:chad.smith&pearson.com 2008-01-17
[Pedro_Garcia] Pedro Garcia mailto:pedro.garcia&puzzle-star.com 2023-03-20
[Randall_Stewart] Randall Stewart IETF TSVWG mailto:rrs&lakerest.net
[Ruwan_Linton] Ruwan Linton mailto:ruwan&wso2.com 2008-08-20
[Scott_Shaffer] Scott Shaffer mailto:scott.shaffer&hp.com
[Sreeram_Duvvuru] Sreeram Duvvuru mailto:sduv&sfbay.sun.com 2002-04
[Thread_Group_Inc] Thread Group, Inc. mailto:help&threadgroup.org 2024-01-22
[Tim_Berners_Lee] Tim Berners-Lee mailto:timbl&w3.org
[Tomas_Svoboda] Tomas Svoboda mailto:svoboda&infima.cz 2004-12
[VESvault_Corp] VESvault Corp mailto:info&vesvault.com 2021-12-29
[W3C_Web_of_Things_Working_Group] W3C Web of Things Working Group mailto:team-wot&w3.org 2022-11-22