Service Name and Transport Protocol Port Number Registry

Last Updated
2020-09-18
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>
ris 180 tcp Intergraph [Dave_Buehmann] [Dave_Buehmann]
ris 180 udp Intergraph [Dave_Buehmann] [Dave_Buehmann]
http-mgmt 280 tcp http-mgmt [Adrian_Pell] [Adrian_Pell]
http-mgmt 280 udp http-mgmt [Adrian_Pell] [Adrian_Pell]
is99s 380 tcp TIA/EIA/IS-99 modem server [Frank_Quick] [Frank_Quick]
is99s 380 udp TIA/EIA/IS-99 modem server [Frank_Quick] [Frank_Quick]
iafdbase 480 tcp iafdbase [Rick_Yazwinski] [Rick_Yazwinski]
iafdbase 480 udp iafdbase [Rick_Yazwinski] [Rick_Yazwinski]
sntp-heartbeat 580 tcp SNTP HEARTBEAT [Louis_Mamakos_2] [Louis_Mamakos_2]
sntp-heartbeat 580 udp SNTP HEARTBEAT [Louis_Mamakos_2] [Louis_Mamakos_2]
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]
ipp 631 tcp IPP (Internet Printing Protocol) [IESG] [IETF_Chair] 2018-07-06 [RFC8011] Defined TXT keys: See BonjourPrinting.pdf.
ipp 631 udp IPP (Internet Printing Protocol) [IESG] [IETF_Chair] 2018-07-06 [RFC8011] Defined TXT keys: See BonjourPrinting.pdf.
ipps 631 tcp Internet Printing Protocol over HTTPS [IESG] [IETF_Chair] 2018-07-06 [RFC8011]
entrust-aaas 680 tcp entrust-aaas
entrust-aaas 680 udp entrust-aaas
wpgs 780 tcp [Josyula_R_Rao] [Josyula_R_Rao]
wpgs 780 udp [Josyula_R_Rao] [Josyula_R_Rao]
mdbs-daemon 800 tcp

IANA assigned this well-formed service name as a replacement for "mdbs_daemon".
mdbs_daemon 800 tcp This entry is an alias to "mdbs-daemon". This entry is now historic, not usable for use with many common service discovery mechanisms.
mdbs-daemon 800 udp

IANA assigned this well-formed service name as a replacement for "mdbs_daemon".
mdbs_daemon 800 udp This entry is an alias to "mdbs-daemon". This entry is now historic, not usable for use with many common service discovery mechanisms.
device 801 tcp
device 801 udp
mbap-s 802 tcp Modbus Application Protocol Secure [modbus.org] [Dennis_Dube] 2014-06-10
mbap-s 802 udp Modbus Application Protocol Secure [modbus.org] [Dennis_Dube] 2014-06-10
803-809 Unassigned
domain-s 853 tcp DNS query-response protocol run over TLS/DTLS [IESG] [IETF_Chair] 2015-10-08 2017-01-23 [RFC7858][RFC8094]
domain-s 853 udp DNS query-response protocol run over TLS/DTLS [IESG] [IETF_Chair] 2015-10-08 2017-01-23 [RFC7858][RFC8094]
webpush 1001 tcp HTTP Web Push [IESG] [IETF_Chair] 2016-11-01 [RFC8030]
socks 1080 tcp Socks [Ying_Da_Lee] [Ying_Da_Lee]
socks 1080 udp Socks [Ying_Da_Lee] [Ying_Da_Lee]
mc-client 1180 tcp Millicent Client Proxy [Steve_Glassman] [Steve_Glassman]
mc-client 1180 udp Millicent Client Proxy [Steve_Glassman] [Steve_Glassman]
pictrography 1280 tcp Pictrography [Takashi_Hoshino] [Takashi_Hoshino]
pictrography 1280 udp Pictrography [Takashi_Hoshino] [Takashi_Hoshino]
telesis-licman 1380 tcp Telesis Network License Manager [Karl_Schendel_Jr] [Karl_Schendel_Jr]
telesis-licman 1380 udp Telesis Network License Manager [Karl_Schendel_Jr] [Karl_Schendel_Jr]
pacerforum 1480 tcp PacerForum [Peter_Caswell] [Peter_Caswell]
pacerforum 1480 udp PacerForum [Peter_Caswell] [Peter_Caswell]
tn-tl-r1 1580 tcp tn-tl-r1
tn-tl-r2 1580 udp tn-tl-r2 [Ed_Kress] [Ed_Kress]
microcom-sbp 1680 tcp microcom-sbp [Boris_B_Maiden] [Boris_B_Maiden]
microcom-sbp 1680 udp microcom-sbp [Boris_B_Maiden] [Boris_B_Maiden]
dpkeyserv 1780 tcp dpkeyserv [Yasunari_Gon_Yamasit] [Yasunari_Gon_Yamasit]
dpkeyserv 1780 udp dpkeyserv [Yasunari_Gon_Yamasit] [Yasunari_Gon_Yamasit]
ansys-lm 1800 tcp ANSYS-License manager [Suzanne_Lorrin_2] [Suzanne_Lorrin_2]
ansys-lm 1800 udp ANSYS-License manager [Suzanne_Lorrin_2] [Suzanne_Lorrin_2]
msmq 1801 tcp Microsoft Message Que [Amnon_Horowitz] [Amnon_Horowitz]
msmq 1801 udp Microsoft Message Que [Amnon_Horowitz] [Amnon_Horowitz]
concomp1 1802 tcp ConComp1 [Ed_Vincent] [Ed_Vincent]
concomp1 1802 udp ConComp1 [Ed_Vincent] [Ed_Vincent]
hp-hcip-gwy 1803 tcp HP-HCIP-GWY [Allen_Baker] [Allen_Baker]
hp-hcip-gwy 1803 udp HP-HCIP-GWY [Allen_Baker] [Allen_Baker]
enl 1804 tcp ENL [Brian_Olson] [Brian_Olson]
enl 1804 udp ENL [Brian_Olson] [Brian_Olson]
enl-name 1805 tcp ENL-Name [Brian_Olson] [Brian_Olson]
enl-name 1805 udp ENL-Name [Brian_Olson] [Brian_Olson]
musiconline 1806 tcp Musiconline [Craig_Weeks] [Craig_Weeks]
musiconline 1806 udp Musiconline [Craig_Weeks] [Craig_Weeks]
fhsp 1807 tcp Fujitsu Hot Standby Protocol [Eiki_Iwata] [Eiki_Iwata]
fhsp 1807 udp Fujitsu Hot Standby Protocol [Eiki_Iwata] [Eiki_Iwata]
oracle-vp2 1808 tcp Oracle-VP2 [Craig_Fowler] [Craig_Fowler]
oracle-vp2 1808 udp Oracle-VP2 [Craig_Fowler] [Craig_Fowler]
oracle-vp1 1809 tcp Oracle-VP1 [Craig_Fowler] [Craig_Fowler]
oracle-vp1 1809 udp Oracle-VP1 [Craig_Fowler] [Craig_Fowler]
vsat-control 1880 tcp Gilat VSAT Control [Yariv_Kaplan] [Yariv_Kaplan]
vsat-control 1880 udp Gilat VSAT Control [Yariv_Kaplan] [Yariv_Kaplan]
pearldoc-xact 1980 tcp PearlDoc XACT [Chris_Vertonghen] [Chris_Vertonghen]
pearldoc-xact 1980 udp PearlDoc XACT [Chris_Vertonghen] [Chris_Vertonghen]
autodesk-nlm 2080 tcp Autodesk NLM (FLEXlm) [Greg_Suppes] [Greg_Suppes]
autodesk-nlm 2080 udp Autodesk NLM (FLEXlm) [Greg_Suppes] [Greg_Suppes]
mc-gt-srv 2180 tcp Millicent Vendor Gateway Server [Steve_Glassman] [Steve_Glassman]
mc-gt-srv 2180 udp Millicent Vendor Gateway Server [Steve_Glassman] [Steve_Glassman]
lnvpoller 2280 tcp LNVPOLLER
lnvpoller 2280 udp LNVPOLLER
etcd-server 2380 tcp etcd server to server communication [CoreOS] [Brian_Harrington] 2014-07-09
2380 udp Reserved
powerexchange 2480 tcp Informatica PowerExchange Listener [Dale_Norman] [Dale_Norman]
powerexchange 2480 udp Informatica PowerExchange Listener [Dale_Norman] [Dale_Norman]
tributary 2580 tcp Tributary [Louis_Lu] [Louis_Lu]
tributary 2580 udp Tributary [Louis_Lu] [Louis_Lu]
pxc-sapxom 2680 tcp pxc-sapxom [Hideki_Kiriyama] [Hideki_Kiriyama]
pxc-sapxom 2680 udp pxc-sapxom [Hideki_Kiriyama] [Hideki_Kiriyama]
lbc-control 2780 tcp LBC Control [Keiji_Michine] [Keiji_Michine]
lbc-control 2780 udp LBC Control [Keiji_Michine] [Keiji_Michine]
acc-raid 2800 tcp ACC RAID [Scott_St_Clair] [Scott_St_Clair]
acc-raid 2800 udp ACC RAID [Scott_St_Clair] [Scott_St_Clair]
igcp 2801 tcp IGCP [David_Hampson] [David_Hampson]
igcp 2801 udp IGCP [David_Hampson] [David_Hampson]
veritas-tcp1 2802 tcp Veritas TCP1
veritas-udp1 2802 udp Veritas UDP1 [Russ_Thrasher] [Russ_Thrasher]

Contact Information

ID Name Organization Contact URI Last Updated
[Adrian_Pell] Adrian Pell mailto:PELL_ADRIAN/HP-UnitedKingdom_om6@hplb.hpl.hp.com
[Allen_Baker] Allen Baker mailto:abaker&boi.hp.com
[Amnon_Horowitz] Amnon Horowitz mailto:amnonh&microsoft.com
[Boris_B_Maiden] Boris B. Maiden mailto:Boris_Maiden&smtp.microcom.com
[Brian_Harrington] Brian Harrington CoreOS mailto:brian.harrington&coreos.com 2014-07-09
[Brian_Olson] Brian Olson mailto:briolson&pacbell.net
[Chris_Vertonghen] Chris Vertonghen mailto:chrisv&pearldoc.com
[Clay_Maeckel] Clay Maeckel mailto:clay_maeckel&filemaker.com
[CoreOS] CoreOS mailto:brian.harrington&coreos.com 2014-07-09
[Craig_Fowler] Craig Fowler mailto:cfowler&us.oracle.com
[Craig_Weeks] Craig Weeks mailto:cweeks&syspace.co.uk
[Dale_Norman] Dale Norman mailto:dnorman&informatica.com
[Dave_Buehmann] Dave Buehmann mailto:ingr!daveb&uunet.uu.net
[David_Hampson] David Hampson mailto:davidha&codemasters.com
[Dennis_Dube] Dennis Dube mailto:dennis.dube&schneider-electric.com 2014-06-10
[Ed_Kress] Ed Kress mailto:eskress&thinknet.com
[Ed_Vincent] Ed Vincent mailto:edv&concomp.com
[Eiki_Iwata] Eiki Iwata mailto:eiki&nd.net.fujitsu.co.jp
[Frank_Quick] Frank Quick mailto:fquick&qualcomm.com
[Greg_Suppes] Greg Suppes mailto:greg.suppes&autodesk.com
[Hideki_Kiriyama] Hideki Kiriyama mailto:kiriyama&cp10.es.xerox.com
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Josyula_R_Rao] Josyula R. Rao mailto:jrrao&watson.ibm.com
[Karl_Schendel_Jr] Karl Schendel, Jr. mailto:wiz&telesis.com
[Keiji_Michine] Keiji Michine mailto:michine&net.paso.fujitsu.co.jp
[Louis_Lu] Louis Lu mailto:LouisL&bristol.com
[Louis_Mamakos_2] Louis Mamakos mailto:louie&uu.net
[modbus.org] modbus.org mailto:rbelliardi&modbus.org 2014-06-10
[Peter_Caswell] Peter Caswell mailto:pfc&pacvax.pacersoft.com
[Randall_Stewart] Randall Stewart IETF TSVWG mailto:rrs&lakerest.net
[Rick_Yazwinski] Rick Yazwinski mailto:ricky&solect.com
[Russ_Thrasher] Russ Thrasher mailto:Russell.Thrasher&veritas.com
[Scott_St_Clair] Scott St. Clair mailto:stclair&ntc.adaptec.com
[Steve_Glassman] Steve Glassman mailto:steveg&pa.dec.com
[Suzanne_Lorrin_2] Suzanne Lorrin mailto:sml&ansyspo.ansys.com
[Takashi_Hoshino] Takashi Hoshino mailto:hoshino&miya.fujifilm.co.jp
[Tim_Berners_Lee] Tim Berners-Lee mailto:timbl&w3.org
[Yariv_Kaplan] Yariv Kaplan mailto:yarivk&gilat.com
[Yasunari_Gon_Yamasit] Yasunari Gon Yamasita mailto:yamasita&omronsoft.co.jp
[Ying_Da_Lee] Ying-Da Lee mailto:ylee&syl.dl.nec.com