Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-11-22
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
mediaboard1 MediaBoardONE Asset and Information Manager data sharing and synchronization protocol [Thomas_K_Fischer] [Thomas_K_Fischer] Defined TXT keys: None
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
moodring Bonjour Mood Ring tutorial program [Daniel_Steinberg] [Daniel_Steinberg] Defined TXT keys: txtvers=1 mood=<ascii digit from 0-4>
nfs-domainroot tcp NFS service for the domain root, the root of an organization's published file namespace. [IESG] [IETF_Chair] 2012-04-24 [RFC6641] Defined TXT keys: None
objective Means for clients to locate servers in an Objective (http://www.objective.com) instance. [Marc_Bailey] [Marc_Bailey] Defined TXT keys: txtvers='1' type={'production'|'standby'|'test'|'demo'} protocol={['SOAP'],['CORBA']} transport=['iiop']|['http']
oca tcp Insecure OCP.1 protocol, which is the insecure TCP/IP implementation of the Object Control Architecture [OCA_Alliance] [Stephan_van_Tienen] 2012-10-11 Defined TXT keys: txtvers=1 protovers=x
oca udp Insecure OCP.1 protocol, which is the insecure TCP/IP implementation of the Object Control Architecture [OCA_Alliance] [Stephan_van_Tienen] 2012-10-11 Defined TXT keys: txtvers=1 protovers=x
ocasec tcp Secure OCP.1 protocol, which is the secure TCP/IP implementation of the Object Control Architecture [OCA_Alliance] [Stephan_van_Tienen] 2012-10-11 Defined TXT keys: txtvers=1 protovers=x
ocasec udp Secure OCP.1 protocol, which is the secure TCP/IP implementation of the Object Control Architecture [OCA_Alliance] [Stephan_van_Tienen] 2012-10-11 Defined TXT keys: txtvers=1 protovers=x
ocaws tcp Insecure OCP.1 hosted on a WebSocket [OCA_Alliance] [Stephan_van_Tienen] 2017-05-19 Defined TXT keys: txtvers protovers path
olpc-activity1 udp One Laptop per Child activity [One_Laptop_per_Child] [One_Laptop_per_Child] Defined TXT keys: Shared_Activity_Protocol_1.0
owhttpd OWFS (1-wire file system) web server [Paul_H_Alfille] [Paul_H_Alfille] Defined TXT keys: txtvers
pgpkey-http PGP Keyserver using HTTP/1.1 [Jeroen_Massar_3] [Jeroen_Massar_3] Defined TXT keys: path=<path on the server where the HKP applications reside> normally: "path=/pks/"
pres tcp Presence [RFC3861]
pres udp Presence [RFC3861]
presence Peer-to-peer messaging / Link-Local Messaging [XMPP_Registrar] [XMPP_Registrar] Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html Note: Registration updated May 2007. Was formerly listed as "iChat AV" (Apple's IM client for Mac OS X) with TXT keys: txtvers, port.p2pj, phsh, vc, 1st, AIM, msg, status, last When first shipped in Mac OS X 10.2, iChat's peer-to-peer messaging protocol was created to solve the problem of serverless messaging between peers on the same link. However, there is nothing inherent in the protocol that limits it to being only link-local; it was simply an artifact of iChat in Mac OS X 10.2 using link-local Multicast DNS to discover peers. With the advent of Wide-Area DNS-SD, it is also possible to use iChat's peer-to-peer messaging between machines on different links.
psap udp Progal Service Advertising Protocol [Soren_Weber] [Soren_Weber] Defined TXT keys: c0, c1, ..., cn
ptp-req PTP Initiation Request Protocol [Mark_Wood] [Mark_Wood] Defined TXT keys: txtvers, guid, c0, c1, c2, ..., where the number of c_n attributes is variable
recipe-sharing tcp Recipe Sharing Protocol [Daniel_G_Taylor] [Daniel_G_Taylor] 2007-11 Defined TXT keys: [http://www.recipemanager.org/rsp/rsp10draft.html#dnssd]
rfid RFID Reader Mach1(tm) Protocol [Paul_Dietrich] [Paul_Dietrich] Defined TXT keys: None
rgb tcp RGB Spectrum Device Discovery [RGB_Spectrum] [Steve_Hershey] 2011-10-10 Defined TXT keys: Keyboard, Mouse, Option1, Option2, Option3, Option4, ModelName
robustirc tcp Like ircu (RFC1459), but failure tolerant due to strong consistency among n>=3 servers [Michael_Stapelberg] [Michael_Stapelberg] 2015-01-07 Defined TXT keys: None
roku-rcp Roku Control Protocol [Don_Woodward] [Don_Woodward] Defined TXT keys: txtvers=1
see SubEthaEdit 2 [TheCodingMonkeys] [TheCodingMonkeys] Defined TXT keys: txtvers=1, name=<Full Name>, userid=<User ID>, version=2
smimeca tcp Domain signing certificate for S/MIME keys [IESG] [John_Levine] 2016-07-26 [draft-bhjl-x509-srv-01] Defined TXT keys: None
sparql SPARQL Protocol and RDF Query Language [Alex_Tucker] [Alex_Tucker] Defined TXT keys: txtvers=1 path=<relative or absolute URL of endpoint> protovers=<number> [if not specified then default is 1.0, corresponding to SPARQL version] binding=<HTTP | SOAP> [if not specified then default is HTTP] vocabs=<space separated list of URIs> [RDF vocabularies or OWL ontologies used by the endpoint] metadata=<URL> [to fetch RDF/XML description of SPARQL service]
spx-hmp tcp SpinetiX HMP [SpinetiX_S_A] [Diego_Santa_Cruz] 2011-10-18 Defined TXT keys: txtvers=1 cport= the port for the content HTTP server (secondary HTTP server used for content publishing) mode= the mode in which the HMP device is currently operating, one of "normal", "safe" or "recovery" serial= serial number of the HMP device firmware= firmware version string (e.g., 2.1.0-0.1.7844) model= model string (e.g., HMP100)
strobe-sync tcp Strobe Synchronization [Jasper_Morgal] [Richard_Morgal] 2019-06-13 Defined TXT keys: Application will rely upon Bonjour version 3.1.0.1
sugarlock-rcp tcp Remote control protocol for Sugarlock consumer electronics devices [Sugarlock_LLC] [Don_Woodward-Sugarlock] 2016-01-22 Defined TXT keys: txtvers=1
sugarlock-rcp udp Remote control protocol for Sugarlock consumer electronics devices [Sugarlock_LLC] [Don_Woodward-Sugarlock] 2016-01-22 Defined TXT keys: txtvers=1
tbricks tbricks internal protocol [Joakim_Johansson] [Joakim_Johansson] Defined TXT keys: txtvers=1, sesna, seid, setype, cosna, coid, cotype, sysna, syna, syid, subsyid, venid, protocols, pid
tinavigator TI Navigator Hub 1.0 Discovery Service [Stephen_Reid] [Stephen_Reid] Defined TXT keys: None
vedabase tcp Application specific synchronization protocol [Peter_Kollath_2] [Peter_Kollath_2] 2014-05-27 Defined TXT keys: txtvers=1
visel visel Q-System services [Lehpaner_Sasa] [Lehpaner_Sasa] Defined TXT keys: Version=<service version> Type=<service type> Name=<service Name> Zone=<service zone> ID=<serviceID> SString=<serviceString> SString1=<serviceString>
vxi-11 VXI-11 TCP/IP Instrument Protocol [Nick_Barendt_2] [Nick_Barendt_2] Defined TXT keys: None
wormhole Roku Cascade Wormhole Protocol [Don_Woodward] [Don_Woodward] Defined TXT keys: txtvers=1
x510 tcp Security service to protocols [ITU-T_Study_Group_17] [Erik_Andersen] 2019-08-13 Defined TXT keys: None

Contact Information

ID Name Organization Contact URI Last Updated
[Alex_Tucker] Alex Tucker mailto:alex&floop.org.uk
[Daniel_G_Taylor] Daniel G. Taylor mailto:dan&programmer-art.org 2007-11
[Daniel_Steinberg] Daniel Steinberg mailto:daniel&oreilly.com
[Diego_Santa_Cruz] Diego Santa Cruz SpinetiX S.A. mailto:Diego.SantaCruz&spinetix.com 2011-10-18
[Don_Woodward] Don Woodward mailto:dwoodward&rokulabs.com
[Don_Woodward-Sugarlock] Don Woodward mailto:don&sugarlock.comm 2016-01-22
[Erik_Andersen] Erik Andersen mailto:era&x500.eu 2019-08-13
[Esko_Dijk] Esko Dijk Thread Group, Inc. mailto:esko.dijk&iotconsultancy.nl 2024-01-22
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[ITU-T_Study_Group_17] ITU-T Study Group 17 mailto:era&x500.eu 2019-08-13
[Jasper_Morgal] Jasper Morgal mailto:jpmorgal8&gmail.com 2019-06-13
[Jeroen_Massar_3] Jeroen Massar mailto:jeroen&unfix.org
[Joakim_Johansson] Joakim Johansson mailto:joakim.johansson&tbricks.com
[John_Levine] John Levine mailto:standards&taugh.com 2016-07-26
[Lehpaner_Sasa] Lehpaner Sasa mailto:lsasa&visel.it
[Marc_Bailey] Marc Bailey mailto:marc&objective.com
[Mark_Wood] Mark Wood mailto:mark.d.wood&kodak.com
[Michael_Stapelberg] Michael Stapelberg mailto:michael+iana&stapelberg.ch 2015-01-07
[Nick_Barendt_2] Nick Barendt mailto:nbarendt&vxitech.com
[OCA_Alliance] OCA Alliance mailto:tina.lipscomb&oca-alliance.com 2017-05-19
[One_Laptop_per_Child] One Laptop per Child/Collabora Ltd. mailto:devel&lists.laptop.org
[Paul_Dietrich] Paul Dietrich mailto:registrar&impinj.com
[Paul_H_Alfille] Paul H Alfille mailto:paul.alfille&gmail.com
[Peter_Kollath_2] Peter Kollath mailto:root&gopal.home.sk 2014-05-27
[RGB_Spectrum] RGB Spectrum mailto:shershey&rgb.com 2011-10-10
[Richard_Morgal] Richard Morgal mailto:rmorgal&wildblue.net 2019-06-13
[Soren_Weber] Soren Weber mailto:sw&ditec-gmbh.de
[SpinetiX_S_A] SpinetiX S.A. mailto:Diego.SantaCruz&spinetix.com 2011-10-18
[Stephen_Reid] Stephen Reid mailto:sreid&ti.com
[Stephan_van_Tienen] Stephan van Tienen OCA Alliance mailto:stephan.vantienen&bosch.com 2017-05-19
[Steve_Hershey] Steve Hershey RGB Spectrum mailto:shershey&rgb.com 2011-10-10
[Sugarlock_LLC] Sugarlock, LLC mailto:don&sugarlock.com 2016-01-22
[TheCodingMonkeys] TheCodingMonkeys mailto:monkeys&codingmonkeys.de
[Thomas_K_Fischer] Thomas K. Fischer mailto:thomas.fischer&interservices.de
[Thread_Group_Inc] Thread Group, Inc. mailto:help&threadgroup.org 2024-01-22
[XMPP_Registrar] XMPP Registrar mailto:registrar&xmpp.org