Service Name and Transport Protocol Port Number Registry

Last Updated
2020-03-27
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Allison Mankin, Markku Kojo, Kumiko Ono, Martin Stiemerling, 
Lars Eggert, Alexey Melnikov, Wes Eddy, Alexander Zimmermann, Brian Trammell, and Jana Iyengar
SCTP: Allison Mankin and 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 difference uses of these ranges is 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.                                                   *
************************************************************************
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 Defined TXT keys: u=<username> p=<password> path=<path to document>
http 80 udp World Wide Web HTTP Defined TXT keys: u=<username> p=<password> path=<path to document>
www 80 tcp World Wide Web HTTP This is a duplicate of the "http" service and should not be used for discovery purposes.
www 80 udp World Wide Web HTTP 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] [RFC4960] 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]
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]
ipps 631 tcp Internet Printing Protocol over HTTPS [IESG] [IETF_Chair] 2018-07-06 [RFC8011]
webpush 1001 tcp HTTP Web Push [IESG] [IETF_Chair] 2016-11-01 [RFC8030]
httpx 4180 tcp HTTPX [Paul_McGough] [Paul_McGough] 2007-02
httpx 4180 udp HTTPX [Paul_McGough] [Paul_McGough] 2007-02 2016-01-05
xmpp-bosh 5280 tcp Bidirectional-streams Over Synchronous HTTP (BOSH) [Peter_Saint_Andre] [Peter_Saint_Andre] 2009-11-25
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
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]
http-alt 8008 udp HTTP Alternate [James_Gettys] [James_Gettys]
http-alt 8080 tcp HTTP Alternate (see port 80) [Stephen_Casner] [Stephen_Casner]
http-alt 8080 udp HTTP Alternate (see port 80) [Stephen_Casner] [Stephen_Casner]
websnp 8084 tcp Snarl Network Protocol over HTTP [full_phat_products] [Chris_Peel_2] 2019-08-08
radan-http 8088 tcp Radan HTTP [Steve_Hay] [Steve_Hay] 2008-06-13
radan-http 8088 udp Radan HTTP [Steve_Hay] [Steve_Hay] 2008-06-13
synapse-nhttp 8280 tcp Synapse Non Blocking HTTP [Ruwan_Linton] [Ruwan_Linton] 2008-06-05
synapse-nhttp 8280 udp Synapse Non Blocking HTTP [Ruwan_Linton] [Ruwan_Linton] 2008-06-05
bveapi 10880 tcp BVEssentials HTTP API [Tri_Tech_Computers_Ltd] [James_Emerton] 2012-11-19
bveapi 10880 udp BVEssentials HTTP API [Tri_Tech_Computers_Ltd] [James_Emerton] 2012-11-19
tcc-http 24680 tcp TCC User HTTP Service [Brian_Kennedy] [Brian_Kennedy] 2006-08
tcc-http 24680 udp TCC User HTTP Service [Brian_Kennedy] [Brian_Kennedy] 2006-08
timezone tcp Time Zone Data Distribution Service - non-TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the http service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
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]).

People

ID Name Organization Contact URI Last Updated
[Adrian_Pell] Adrian Pell mailto:PELL_ADRIAN/HP-UnitedKingdom_om6@hplb.hpl.hp.com
[Brian_Kennedy] Brian Kennedy mailto:BrianK&targetedconvergence.com 2006-08
[Chris_Peel_2] Chris Peel mailto:chris.gsi&fullphat.net 2014-05-16
[Clay_Maeckel] Clay Maeckel mailto:clay_maeckel&filemaker.com
[full_phat_products] full phat products mailto:chris.gsi&fullphat.net 2019-08-08
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[James_Emerton] James Emerton Tri Tech Computers Ltd. mailto:james&tri-tech.com 2012-11-19
[James_Gettys] James Gettys mailto:jg&w3.org
[Jim_Kateley] Jim Kateley mailto:asr-dev&group.apple.com 2006-01
[Paul_McGough] Paul McGough mailto:paulmcgough&yahoo.com 2016-01-05
[Paul_Sterk] Paul Sterk mailto:paul.sterk&sun.com 2006-03
[Peter_Saint_Andre] Peter Saint-Andre mailto:stpeter&stpeter.im 2009-11-25
[Randall_Stewart] Randall Stewart IETF TSVWG mailto:rrs&lakerest.net
[Ruwan_Linton] Ruwan Linton mailto:ruwan&wso2.com 2008-08-20
[Shantonu_Sen] Shantonu Sen mailto:ssen&apple.com
[Stephen_Casner] Stephen Casner mailto:casner&precpt.com
[Steve_Hay] Steve Hay mailto:SteveHay&planit.com 2008-06-13
[Tim_Berners_Lee] Tim Berners-Lee mailto:timbl&w3.org
[Tri_Tech_Computers_Ltd] Tri Tech Computers Ltd. mailto:admins&tri-tech.com 2012-11-19