Service Name and Transport Protocol Port Number Registry

Last Updated
2025-09-29
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
8 tcp Unassigned
8 udp Unassigned
daytime 13 tcp Daytime [Jon_Postel] [Jon_Postel] [RFC867]
daytime 13 udp Daytime [Jon_Postel] [Jon_Postel] [RFC867]
msp 18 tcp Message Send Protocol (historic) [Rina_Nethaniel] [Rina_Nethaniel]
msp 18 udp Message Send Protocol (historic) [Rina_Nethaniel] [Rina_Nethaniel]
telnet 23 tcp Telnet [Jon_Postel] [Jon_Postel] [RFC854] Defined TXT keys: u=<username> p=<password>
telnet 23 udp Telnet [Jon_Postel] [Jon_Postel] [RFC854] Defined TXT keys: u=<username> p=<password>
28 tcp Unassigned
28 udp Unassigned
rap 38 tcp Route Access Protocol [Robert_Ullmann] [Robert_Ullmann]
rap 38 udp Route Access Protocol [Robert_Ullmann] [Robert_Ullmann]
47 tcp Reserved 2017-05-18 This entry has been removed on 2017-05-18.
47 udp Reserved 2017-05-18 This entry has been removed on 2017-05-18.
auditd 48 tcp Digital Audit Daemon [Larry_Scott] [Larry_Scott]
auditd 48 udp Digital Audit Daemon [Larry_Scott] [Larry_Scott]
xns-mail 58 tcp XNS Mail [Susie_Armstrong] [Susie_Armstrong]
xns-mail 58 udp XNS Mail [Susie_Armstrong] [Susie_Armstrong]
61 tcp Reserved 2017-05-18 This entry has been removed on 2017-05-18.
61 udp Reserved 2017-05-18 This entry has been removed on 2017-05-18.
bootpc 68 tcp Bootstrap Protocol Client [Bill_Croft] [Bill_Croft]
bootpc 68 udp Bootstrap Protocol Client [Bill_Croft] [Bill_Croft]
vettcp 78 tcp vettcp [Christopher_Leong] [Christopher_Leong]
vettcp 78 udp vettcp [Christopher_Leong] [Christopher_Leong]
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>
81 Unassigned 2007-09-06
xfer 82 tcp XFER Utility [Thomas_M_Smith] [Thomas_M_Smith]
xfer 82 udp XFER Utility [Thomas_M_Smith] [Thomas_M_Smith]
mit-ml-dev 83 tcp MIT ML Device [David_Reed] [David_Reed]
mit-ml-dev 83 udp MIT ML Device [David_Reed] [David_Reed]
ctf 84 tcp Common Trace Facility [Hugh_Thomas] [Hugh_Thomas]
ctf 84 udp Common Trace Facility [Hugh_Thomas] [Hugh_Thomas]
mit-ml-dev 85 tcp MIT ML Device [David_Reed] [David_Reed]
mit-ml-dev 85 udp MIT ML Device [David_Reed] [David_Reed]
mfcobol 86 tcp Micro Focus Cobol [Simon_Edwards] [Simon_Edwards]
mfcobol 86 udp Micro Focus Cobol [Simon_Edwards] [Simon_Edwards]
87 tcp any private terminal link [Jon_Postel] [Jon_Postel]
87 udp any private terminal link [Jon_Postel] [Jon_Postel]
kerberos 88 tcp Kerberos [B_Clifford_Neuman] [B_Clifford_Neuman] 2022-02-18 [RFC4120]
kerberos 88 udp Kerberos [B_Clifford_Neuman] [B_Clifford_Neuman] 2022-02-18 [RFC4120]
su-mit-tg 89 tcp SU/MIT Telnet Gateway [Mark_Crispin] [Mark_Crispin]
su-mit-tg 89 udp SU/MIT Telnet Gateway [Mark_Crispin] [Mark_Crispin]
tacnews 98 tcp TAC News [Jon_Postel] [Jon_Postel]
tacnews 98 udp TAC News [Jon_Postel] [Jon_Postel]
snagas 108 tcp SNA Gateway Access Server [Kevin_Murphy] [Kevin_Murphy]
snagas 108 udp SNA Gateway Access Server [Kevin_Murphy] [Kevin_Murphy]
sqlserv 118 tcp SQL Services [Larry_Barnes] [Larry_Barnes]
sqlserv 118 udp SQL Services [Larry_Barnes] [Larry_Barnes]
gss-xlicen 128 tcp GSS X License Verification [John_Light] [John_Light]
gss-xlicen 128 udp GSS X License Verification [John_Light] [John_Light]
netbios-dgm 138 tcp NETBIOS Datagram Service
netbios-dgm 138 udp NETBIOS Datagram Service
jargon 148 tcp Jargon [Bill_Weinman] [Bill_Weinman]
jargon 148 udp Jargon [Bill_Weinman] [Bill_Weinman]
pcmail-srv 158 tcp PCMail Server [Mark_L_Lambert] [Mark_L_Lambert]
pcmail-srv 158 udp PCMail Server [Mark_L_Lambert] [Mark_L_Lambert]
rsvd 168 tcp RSVD [Alan_Sandell] [Alan_Sandell] 2008-05-01
rsvd 168 udp RSVD [Alan_Sandell] [Alan_Sandell] 2008-05-01
nextstep 178 tcp NextStep Window Server [Leo_Hourvitz] [Leo_Hourvitz]
nextstep 178 udp NextStep Window Server [Leo_Hourvitz] [Leo_Hourvitz]
ris 180 tcp Intergraph [Dave_Buehmann] [Dave_Buehmann]
ris 180 udp Intergraph [Dave_Buehmann] [Dave_Buehmann]
unify 181 tcp Unify [Daegis_Inc] [Chris_Anderson] 2012-07-31
unify 181 udp Unify [Daegis_Inc] [Chris_Anderson] 2012-07-31
audit 182 tcp Unisys Audit SITP [Gil_Greenbaum] [Gil_Greenbaum]
audit 182 udp Unisys Audit SITP [Gil_Greenbaum] [Gil_Greenbaum]
ocbinder 183 tcp OCBinder
ocbinder 183 udp OCBinder
ocserver 184 tcp OCServer [Jerrilynn_Okamura] [Jerrilynn_Okamura]
ocserver 184 udp OCServer [Jerrilynn_Okamura] [Jerrilynn_Okamura]
remote-kis 185 tcp Remote-KIS
remote-kis 185 udp Remote-KIS
kis 186 tcp KIS Protocol [Ralph_Droms] [Ralph_Droms]
kis 186 udp KIS Protocol [Ralph_Droms] [Ralph_Droms]
aci 187 tcp Application Communication Interface [Rick_Carlos] [Rick_Carlos]
aci 187 udp Application Communication Interface [Rick_Carlos] [Rick_Carlos]
mumps 188 tcp Plus Five's MUMPS [Hokey_Stenn] [Hokey_Stenn]
mumps 188 udp Plus Five's MUMPS [Hokey_Stenn] [Hokey_Stenn]
qft 189 tcp Queued File Transport [Wayne_Schroeder] [Wayne_Schroeder]
qft 189 udp Queued File Transport [Wayne_Schroeder] [Wayne_Schroeder]
dls-mon 198 tcp Directory Location Service Monitor [Scott_Bellew] [Scott_Bellew]
dls-mon 198 udp Directory Location Service Monitor [Scott_Bellew] [Scott_Bellew]
at-8 208 tcp AppleTalk Unused [Rob_Chandhok] [Rob_Chandhok]
at-8 208 udp AppleTalk Unused [Rob_Chandhok] [Rob_Chandhok]
mpp 218 tcp Netix Message Posting Protocol [Shannon_Yeh] [Shannon_Yeh]
mpp 218 udp Netix Message Posting Protocol [Shannon_Yeh] [Shannon_Yeh]
bhfhs 248 tcp bhfhs [John_Kelly] [John_Kelly]
bhfhs 248 udp bhfhs [John_Kelly] [John_Kelly]
258 Unassigned 2006-09-13
td-replica 268 tcp Tobit David Replica [Franz_Josef_Leuders] [Franz_Josef_Leuders]
td-replica 268 udp Tobit David Replica [Franz_Josef_Leuders] [Franz_Josef_Leuders]
manet 269 tcp MANET Protocols [RFC5498]
manet 269 udp MANET Protocols [RFC5498]
pt-tls 271 tcp IETF Network Endpoint Assessment (NEA) Posture Transport Protocol over TLS (PT-TLS) [IESG] [IETF_Chair] 2012-07-31 [RFC6876]

Contact Information

ID Name Organization Contact URI Last Updated
[Alan_Sandell] Alan Sandell mailto:alan.sandell&ist.co.uk 2008-05-01
[B_Clifford_Neuman] B. Clifford Neuman mailto:bcn&isi.edu 2022-02-18
[Bill_Croft] Bill Croft mailto:Croft&sumex-aim.stanford.edu
[Bill_Weinman] Bill Weinman mailto:wew&bearnet.com
[Chris_Anderson] Chris Anderson Daegis, Inc. mailto:ianaportmaster&daegis.com 2012-07-31
[Christopher_Leong] Christopher Leong mailto:leong&kolmod.mlo.dec.com
[Daegis_Inc] Daegis, Inc. mailto:ianaportmaster&daegis.com 2012-07-31
[Dave_Buehmann] Dave Buehmann mailto:ingr!daveb&uunet.uu.net
[David_Reed] David Reed
[Franz_Josef_Leuders] Franz-Josef Leuders mailto:development&tobit.com
[Gil_Greenbaum] Gil Greenbaum mailto:gcole&nisd.cam.unisys.com
[Hokey_Stenn] Hokey Stenn mailto:hokey&plus5.com
[Hugh_Thomas] Hugh Thomas mailto:thomas&oils.enet.dec.com
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jerrilynn_Okamura] Jerrilynn Okamura
[John_Kelly] John Kelly mailto:johnk&bellhow.com
[John_Light] John Light mailto:johnl&gssc.gss.com
[Jon_Postel] Jon Postel mailto:postel&isi.edu
[Kevin_Murphy] Kevin Murphy mailto:murphy&sevens.lkg.dec.com
[Larry_Barnes] Larry Barnes mailto:barnes&broke.enet.dec.com
[Larry_Scott] Larry Scott mailto:scott&zk3.dec.com
[Leo_Hourvitz] Leo Hourvitz mailto:leo&next.com
[Mark_Crispin] Mark Crispin mailto:MRC&panda.com
[Mark_L_Lambert] Mark L. Lambert mailto:markl&ptt.lcs.mit.edu
[Ralph_Droms] Ralph Droms mailto:rdroms&nri.reston.va.us
[Randall_Stewart] Randall Stewart IETF TSVWG mailto:rrs&lakerest.net
[Rick_Carlos] Rick Carlos mailto:rick&ticipa.csc.ti.com
[Rina_Nethaniel] Rina Nethaniel
[Rob_Chandhok] Rob Chandhok mailto:chandhok&gnome.cs.cmu.edu
[Robert_Ullmann] Robert Ullmann mailto:ariel&world.std.com
[Scott_Bellew] Scott Bellew mailto:smb&cs.purdue.edu
[Shannon_Yeh] Shannon Yeh mailto:yeh&netix.com
[Simon_Edwards] Simon Edwards mailto:sedwards&rocketsoftware.com 2024-10-11
[Susie_Armstrong] Susie Armstrong mailto:Armstrong.wbst128@xerox
[Thomas_M_Smith] Thomas M. Smith mailto:Thomas.M.Smith&lmco.com
[Tim_Berners_Lee] Tim Berners-Lee mailto:timbl&w3.org
[Wayne_Schroeder] Wayne Schroeder mailto:schroeder&sds.sdsc.edu