Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-12-06
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
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.
www-http 80 tcp World Wide Web HTTP [Tim_Berners_Lee] [Tim_Berners_Lee] This is a duplicate of the "http" service and should not be used for discovery purposes. u=<username> p=<password> path=<path to document> (see txtrecords.html#http) Known Subtypes: _printer NOTE: The meaning of this service type, though called just "http", actually denotes something more precise than just "any data transported using HTTP". The DNS-SD service type "http" should only be used to advertise content that: * is served over HTTP, * can be displayed by "typical" web browser client software, and * is intented primarily to be viewed by a human user. Of course, the definition of "typical web browser" is subjective, and may change over time, but for practical purposes the DNS-SD service type "http" can be understood as meaning "human-readable HTML content served over HTTP". In some cases other widely-supported content types may also be appropriate, such as plain text over HTTP, or JPEG image over HTTP. Content types not intented primarily for viewing by a human user, or not widely-supported in web browsing clients, should not be advertised as DNS-SD service type "http", even if they do happen to be transported over HTTP. Such types should be advertised as their own logical service type with their own DNS-SD service type, for example, XUL (XML User Interface Language) transported over HTTP is advertised explicitly as DNS-SD service type "xul-http".
www-http 80 udp World Wide Web HTTP [Tim_Berners_Lee] [Tim_Berners_Lee] This is a duplicate of the "http" service and should not be used for discovery purposes. u=<username> p=<password> path=<path to document> (see txtrecords.html#http) Known Subtypes: _printer NOTE: The meaning of this service type, though called just "http", actually denotes something more precise than just "any data transported using HTTP". The DNS-SD service type "http" should only be used to advertise content that: * is served over HTTP, * can be displayed by "typical" web browser client software, and * is intented primarily to be viewed by a human user. Of course, the definition of "typical web browser" is subjective, and may change over time, but for practical purposes the DNS-SD service type "http" can be understood as meaning "human-readable HTML content served over HTTP". In some cases other widely-supported content types may also be appropriate, such as plain text over HTTP, or JPEG image over HTTP. Content types not intented primarily for viewing by a human user, or not widely-supported in web browsing clients, should not be advertised as DNS-SD service type "http", even if they do happen to be transported over HTTP. Such types should be advertised as their own logical service type with their own DNS-SD service type, for example, XUL (XML User Interface Language) transported over HTTP is advertised explicitly as DNS-SD service type "xul-http".
http 80 sctp HTTP [Randall_Stewart] [Randall_Stewart] 2022-02-07 [RFC9260] Defined TXT keys: u=<username> p=<password> path=<path to document>
http-mgmt 280 tcp http-mgmt [Adrian_Pell] [Adrian_Pell]
http-mgmt 280 udp http-mgmt [Adrian_Pell] [Adrian_Pell]
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]
gss-http 488 tcp gss-http [Doug_Rosenthal] [Doug_Rosenthal]
gss-http 488 udp gss-http [Doug_Rosenthal] [Doug_Rosenthal]
http-alt 591 tcp FileMaker, Inc. - HTTP Alternate (see Port 80) [Clay_Maeckel] [Clay_Maeckel]
http-alt 591 udp FileMaker, Inc. - HTTP Alternate (see Port 80) [Clay_Maeckel] [Clay_Maeckel]
http-rpc-epmap 593 tcp HTTP RPC Ep Map [Edward_Reus] [Edward_Reus]
http-rpc-epmap 593 udp HTTP RPC Ep Map [Edward_Reus] [Edward_Reus]
oob-ws-http 623 tcp DMTF out-of-band web services management protocol [Jim_Davis] [Jim_Davis] 2007-06
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
multiling-http 777 tcp Multiling HTTP [Alejandro_Bonet] [Alejandro_Bonet]
multiling-http 777 udp Multiling HTTP [Alejandro_Bonet] [Alejandro_Bonet]
netconfsoaphttp 832 tcp NETCONF for SOAP over HTTPS [RFC4743]
netconfsoaphttp 832 udp NETCONF for SOAP over HTTPS [RFC4743]
webpush 1001 tcp HTTP Web Push [IESG] [IETF_Chair] 2016-11-01 [RFC8030]
saphostctrl 1128 tcp SAPHostControl over SOAP/HTTP
saphostctrl 1128 udp SAPHostControl over SOAP/HTTP
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-http 1183 tcp LL Surfup HTTP
llsurfup-http 1183 udp LL Surfup HTTP
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]
event-port 2069 tcp HTTP Event Port [Larry_Emlich] [Larry_Emlich]
event-port 2069 udp HTTP Event Port [Larry_Emlich] [Larry_Emlich]
cpq-wbem 2301 tcp Compaq HTTP [Scott_Shaffer] [Scott_Shaffer]
cpq-wbem 2301 udp Compaq HTTP [Scott_Shaffer] [Scott_Shaffer]
compaq-https 2381 tcp Compaq HTTPS [Scott_Shaffer] [Scott_Shaffer]
compaq-https 2381 udp Compaq HTTPS [Scott_Shaffer] [Scott_Shaffer]
md-cg-http 2688 tcp md-cf-http [Lyndon_Nerenberg] [Lyndon_Nerenberg]
md-cg-http 2688 udp md-cf-http [Lyndon_Nerenberg] [Lyndon_Nerenberg]
webemshttp 2851 tcp webemshttp [Stephen_Tsun] [Stephen_Tsun]
webemshttp 2851 udp webemshttp [Stephen_Tsun] [Stephen_Tsun]
cardbox-http 3106 tcp Cardbox HTTP [Martin_Kochanski] [Martin_Kochanski]
cardbox-http 3106 udp Cardbox HTTP [Martin_Kochanski] [Martin_Kochanski]
dwnmshttp 3227 tcp DiamondWave NMS Server
dwnmshttp 3227 udp DiamondWave NMS Server
sunlps-http 3816 tcp Sun Local Patch Server [Barry_Greenberg] [Barry_Greenberg] 2004-04
sunlps-http 3816 udp Sun Local Patch Server [Barry_Greenberg] [Barry_Greenberg] 2004-04
wap-push-http 4035 tcp WAP Push OTA-HTTP port
wap-push-http 4035 udp WAP Push OTA-HTTP port
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]
httpx 4180 tcp HTTPX [Paul_McGough] [Paul_McGough] 2007-02
httpx 4180 udp HTTPX [Paul_McGough] [Paul_McGough] 2007-02 2016-01-05
rid 4590 tcp RID over HTTP/TLS [IESG] [IETF_Chair] [RFC6546]
appserv-http 4848 tcp App Server - Admin HTTP
appserv-http 4848 udp App Server - Admin HTTP
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
xmpp-bosh 5280 tcp Bidirectional-streams Over Synchronous HTTP (BOSH) [Peter_Saint_Andre] [Peter_Saint_Andre] 2009-11-25
presence 5298 tcp XMPP Link-Local Messaging [Eric_St_Onge] [Eric_St_Onge] 2008-01-14 Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html
presence 5298 udp XMPP Link-Local Messaging [Eric_St_Onge] [Eric_St_Onge] 2008-01-14 Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html
spss 5443 tcp Pearson HTTPS [Pearson] [Pearson] 2008-01-17
spss 5443 udp Pearson HTTPS [Pearson] [Pearson] 2008-01-17
sgi-esphttp 5554 tcp SGI ESP HTTP [Vladimir_Legalov] [Vladimir_Legalov]
sgi-esphttp 5554 udp SGI ESP HTTP [Vladimir_Legalov] [Vladimir_Legalov]
wsman 5985 tcp WBEM WS-Management HTTP [Jim_Davis] [Jim_Davis] 2006-11
wsman 5985 udp WBEM WS-Management HTTP [Jim_Davis] [Jim_Davis] 2006-11
wsmans 5986 tcp WBEM WS-Management HTTP over TLS/SSL [Jim_Davis] [Jim_Davis] 2006-11
wsmans 5986 udp WBEM WS-Management HTTP over TLS/SSL [Jim_Davis] [Jim_Davis] 2006-11
wbem-http 5988 tcp WBEM CIM-XML (HTTP) [Jim_Davis] [Jim_Davis]
wbem-http 5988 udp WBEM CIM-XML (HTTP) [Jim_Davis] [Jim_Davis]
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
sun-sr-http 6480 tcp Service Registry Default HTTP Domain [Paul_Sterk] [Paul_Sterk] 2006-03
sun-sr-http 6480 udp Service Registry Default HTTP Domain [Paul_Sterk] [Paul_Sterk] 2006-03
plysrv-http 6770 tcp PolyServe http [Mike_Spitzer] [Mike_Spitzer] 2005-08
plysrv-http 6770 udp PolyServe http [Mike_Spitzer] [Mike_Spitzer] 2005-08
plysrv-https 6771 tcp PolyServe https [Mike_Spitzer] [Mike_Spitzer] 2005-08
plysrv-https 6771 udp PolyServe https [Mike_Spitzer] [Mike_Spitzer] 2005-08
smc-http 6788 tcp SMC-HTTP [Ratnadeep_Bhattachar] [Ratnadeep_Bhattachar] 2002-11
smc-http 6788 udp SMC-HTTP [Ratnadeep_Bhattachar] [Ratnadeep_Bhattachar] 2002-11
netmo-http 6842 tcp Netmo HTTP [Urs_Bertschinger] [Urs_Bertschinger]
netmo-http 6842 udp Netmo HTTP [Urs_Bertschinger] [Urs_Bertschinger]
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
soap-http 7627 tcp SOAP Service Port [Donald_Dylla] [Donald_Dylla] 2004-12
soap-http 7627 udp SOAP Service Port [Donald_Dylla] [Donald_Dylla] 2004-12
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
asr 7800 tcp Apple Software Restore [Jim_Kateley][Shantonu_Sen] [Jim_Kateley][Shantonu_Sen] 2006-01 Defined TXT keys: image=<HTTP URL of disk image>
asr 7800 udp Apple Software Restore [Jim_Kateley][Shantonu_Sen] [Jim_Kateley][Shantonu_Sen] 2006-01 Defined TXT keys: image=<HTTP URL of disk image>
http-alt 8008 tcp HTTP Alternate [James_Gettys] [James_Gettys]

Contact Information

ID Name Organization Contact URI Last Updated
[Abhijit_Kumar] Abhijit Kumar mailto:as-iana-ports&sun.com 2005-11
[Adrian_Pell] Adrian Pell mailto:PELL_ADRIAN/HP-UnitedKingdom_om6@hplb.hpl.hp.com
[Alejandro_Bonet] Alejandro Bonet mailto:babel&ctv.es
[Barry_Greenberg] Barry Greenberg mailto:barry.greenberg&sun.com 2004-04
[Broadband_Forum] Broadband Forum mailto:help&broadband-forum.org 2020-03-17
[Clay_Maeckel] Clay Maeckel mailto:clay&claris.com 2023-09-12
[David_McMarlin] David McMarlin mailto:david.mcmarlin&oracle.com 2006-08
[Denise_Eckstein] Denise Eckstein mailto:denise.eckstein&hp.com 2004-11
[Donald_Dylla] Donald Dylla mailto:donald.dylla&hp.com 2004-12
[Doug_Rosenthal] Doug Rosenthal mailto:rosenthl&krypton.einet.net
[Edward_Reus] Edward Reus mailto:edwardr&microsoft.com
[Eric_St_Onge] Eric St. Onge mailto:stonge&apple.com 2008-01-14
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[James_Gettys] James Gettys mailto:jg&w3.org
[Jim_Davis] Jim Davis mailto:jim.davis&wbemsolutions.com 2007-06
[Jim_Kateley] Jim Kateley mailto:asr-dev&group.apple.com 2006-01
[Katy_Lynn_McCullough] Katy Lynn McCullough mailto:KatyM&laplink.com
[Larry_Emlich] Larry Emlich mailto:larry.emlich&compaq.com
[Lyndon_Nerenberg] Lyndon Nerenberg mailto:lyndon&execmail.ca
[Martin_Kochanski] Martin Kochanski mailto:martin&cardbox.co.uk
[Matthieu_Lachance] Matthieu Lachance mailto:matthieu.lachance&openwave.com
[Mike_Spitzer] Mike Spitzer mailto:mjs&polyserve.com 2005-08
[Muscarella_Fabrizio] Muscarella Fabrizio mailto:fabrizio.muscarella&sap.com 2006-04
[Paul_McGough] Paul McGough mailto:paulmcgough&yahoo.com 2016-01-05
[Paul_Sterk] Paul Sterk mailto:paul.sterk&sun.com 2006-03
[Pearson] Pearson mailto:chad.smith&pearson.com 2008-01-17
[Peter_Saint_Andre] Peter Saint-Andre mailto:stpeter&stpeter.im 2009-11-25
[Randall_Stewart] Randall Stewart IETF TSVWG mailto:rrs&lakerest.net
[Ratnadeep_Bhattachar] Ratnadeep Bhattacharjee mailto:ratnadeep.bhattacharjee&sun.com 2002-11
[Scott_Shaffer] Scott Shaffer mailto:scott.shaffer&hp.com
[Shantonu_Sen] Shantonu Sen mailto:ssen&apple.com
[Sreeram_Duvvuru] Sreeram Duvvuru mailto:sduv&sfbay.sun.com 2002-04
[Stephen_Tsun] Stephen Tsun mailto:stsun&jetstream.com
[Tim_Berners_Lee] Tim Berners-Lee mailto:timbl&w3.org
[Urs_Bertschinger] Urs Bertschinger mailto:urs&netmosphere.com
[Vladimir_Legalov] Vladimir Legalov mailto:legalov&sgi.com