Service Name and Transport Protocol Port Number Registry

Last Updated
2026-08-11
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell,
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
cadlock2 1000 tcp
cadlock2 1000 udp
pkix-cmc 5318 tcp PKIX Certificate Management using CMS (CMC) [IESG] [IETF_Chair] 2026-02-13 [RFC10003]
ndmp 10000 tcp Network Data Management Protocol [Brian_Ehrmantraut] [Brian_Ehrmantraut]
ndmp 10000 udp Network Data Management Protocol [Brian_Ehrmantraut] [Brian_Ehrmantraut]
scp-config 10001 tcp SCP Configuration [Michael_Benz] [Michael_Benz] 2010-08-06
scp-config 10001 udp SCP Configuration [Michael_Benz] [Michael_Benz] 2010-08-06
documentum 10002 tcp EMC-Documentum Content Server Product [Reza_Bagherian] [Reza_Bagherian] 2007-07-19
documentum 10002 udp EMC-Documentum Content Server Product [Reza_Bagherian] [Reza_Bagherian] 2007-07-19
documentum-s 10003 tcp EMC-Documentum Content Server Product

IANA assigned this well-formed service name as a replacement for "documentum_s".
[Reza_Bagherian] [Reza_Bagherian] 2007-07-19
documentum_s 10003 tcp EMC-Documentum Content Server Product [Reza_Bagherian] [Reza_Bagherian] 2007-07-19 This entry is an alias to "documentum-s". This entry is now historic, not usable for use with many common service discovery mechanisms.
documentum-s 10003 udp EMC-Documentum Content Server Product

IANA assigned this well-formed service name as a replacement for "documentum_s".
[Reza_Bagherian] [Reza_Bagherian] 2007-07-19
documentum_s 10003 udp EMC-Documentum Content Server Product [Reza_Bagherian] [Reza_Bagherian] 2007-07-19 This entry is an alias to "documentum-s". This entry is now historic, not usable for use with many common service discovery mechanisms.
emcrmirccd 10004 tcp EMC Replication Manager Client [Robert_Boudrie] [Robert_Boudrie] 2008-06-09
10004 udp Reserved
emcrmird 10005 tcp EMC Replication Manager Server [Robert_Boudrie] [Robert_Boudrie] 2008-06-09
10005 udp Reserved
netapp-sync 10006 tcp Sync replication protocol among different NetApp platforms [NetApp_2] [Paul_Mu] 2014-08-07
10006 udp Reserved
mvs-capacity 10007 tcp MVS Capacity [Donna_Dillenberger] [Donna_Dillenberger]
mvs-capacity 10007 udp MVS Capacity [Donna_Dillenberger] [Donna_Dillenberger]
octopus 10008 tcp Octopus Multiplexer [Chris_Koeritz_2] [Chris_Koeritz_2] 2002-10
octopus 10008 udp Octopus Multiplexer [Chris_Koeritz_2] [Chris_Koeritz_2] 2002-10
swdtp-sv 10009 tcp Systemwalker Desktop Patrol [Akira_Ide] [Akira_Ide] 2006-03
swdtp-sv 10009 udp Systemwalker Desktop Patrol [Akira_Ide] [Akira_Ide] 2006-03
irisa 11000 tcp IRISA [V_A_Brauner] [V_A_Brauner]
irisa 11000 udp IRISA [V_A_Brauner] [V_A_Brauner]
irtrans 21000 tcp IRTrans Control [Marcus_Mueller] [Marcus_Mueller] 2004-11
irtrans 21000 udp IRTrans Control [Marcus_Mueller] [Marcus_Mueller] 2004-11
31000-31015 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Akira_Ide] Akira Ide mailto:ide.akira&jp.fujitsu.com 2006-09
[Brian_Ehrmantraut] Brian Ehrmantraut mailto:bae&netapp.com
[Chris_Koeritz_2] Chris Koeritz mailto:fred&gruntose.com 2002-10
[Donna_Dillenberger] Donna Dillenberger mailto:engd&us.ibm.com
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Marcus_Mueller] Marcus Mueller mailto:marcus&irtrans.de 2004-11
[Michael_Benz] Michael Benz mailto:michael.benz&lsi.com 2010-08-06
[NetApp_2] NetApp mailto:pmu&netapp.com. 2014-08-12
[Paul_Mu] Paul Mu NetApp mailto:pmu&netapp.com 2014-08-07
[Reza_Bagherian] Reza Bagherian mailto:bagherian_reza&emc.com 2007-07-19
[Robert_Boudrie] Robert Boudrie mailto:boudrie_rob&emc.com 2008-06-09
[V_A_Brauner] V. A. Brauner mailto:info&datamedia.fr