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
h323hostcall 1720 tcp H.323 Call Control Signalling [ITU-T] [ITU-T_TSB] 2013-01-31
h323hostcall 1720 udp H.323 Call Control Signalling [ITU-T] [ITU-T_TSB] 2013-01-31
h323hostcall 1720 sctp H.323 Call Control [ITU-T] 2014-07-30
mcagent 1820 tcp mcagent [Ryoichi_Shinohara] [Ryoichi_Shinohara]
mcagent 1820 udp mcagent [Ryoichi_Shinohara] [Ryoichi_Shinohara]
can-ferret 1920 tcp IBM Tivoli Directory Service - FERRET [Nic_Catrambone] [Nic_Catrambone]
can-ferret 1920 udp IBM Tivoli Directory Service - FERRET [Nic_Catrambone] [Nic_Catrambone]
cisco-sccp 2000 tcp Cisco SCCP [Dan_Wing] [Dan_Wing] 2003-11
cisco-sccp 2000 udp Cisco SCCp [Dan_Wing] [Dan_Wing] 2003-11
dc 2001 tcp
wizard 2001 udp curry
globe 2002 tcp
globe 2002 udp
brutus 2003 tcp Brutus Server [Johannes_Skov_Frands] [Johannes_Skov_Frands] 2008-02-28
brutus 2003 udp Brutus Server [Johannes_Skov_Frands] [Johannes_Skov_Frands] 2008-02-28
mailbox 2004 tcp
emce 2004 udp CCWS mm conf
berknet 2005 tcp
oracle 2005 udp
invokator 2006 tcp
raid-cd 2006 udp raid
dectalk 2007 tcp
raid-am 2007 udp
conf 2008 tcp
terminaldb 2008 udp
news 2009 tcp
whosockami 2009 udp
search 2010 tcp
pipe-server 2010 udp

IANA assigned this well-formed service name as a replacement for "pipe_server".
pipe_server 2010 udp This entry is an alias to "pipe-server". This entry is now historic, not usable for use with many common service discovery mechanisms.
raid-cc 2011 tcp raid
servserv 2011 udp
ttyinfo 2012 tcp
raid-ac 2012 udp
raid-am 2013 tcp
raid-cd 2013 udp
troff 2014 tcp
raid-sf 2014 udp
cypress 2015 tcp
raid-cs 2015 udp
bootserver 2016 tcp
bootserver 2016 udp
cypress-stat 2017 tcp
bootclient 2017 udp
terminaldb 2018 tcp
rellpack 2018 udp
whosockami 2019 tcp
about 2019 udp
xinupageserver 2020 tcp
xinupageserver 2020 udp
servexec 2021 tcp
xinuexpansion1 2021 udp
down 2022 tcp
xinuexpansion2 2022 udp
xinuexpansion3 2023 tcp
xinuexpansion3 2023 udp
xinuexpansion4 2024 tcp
xinuexpansion4 2024 udp
ellpack 2025 tcp
xribs 2025 udp
scrabble 2026 tcp
scrabble 2026 udp
shadowserver 2027 tcp
shadowserver 2027 udp
submitserver 2028 tcp
submitserver 2028 udp
hsrpv6 2029 tcp Hot Standby Router Protocol IPv6 [Ian_Wilson] [Ian_Wilson] 2004-11
hsrpv6 2029 udp Hot Standby Router Protocol IPv6 [Ian_Wilson] [Ian_Wilson] 2004-11
device2 2030 tcp
device2 2030 udp
mobrien-chat 2031 tcp mobrien-chat [Mike_O_Brien] [Mike_O_Brien] 2004-11
mobrien-chat 2031 udp mobrien-chat [Mike_O_Brien] [Mike_O_Brien] 2004-11
blackboard 2032 tcp
blackboard 2032 udp
glogger 2033 tcp
glogger 2033 udp
scoremgr 2034 tcp
scoremgr 2034 udp
imsldoc 2035 tcp
imsldoc 2035 udp
e-dpnet 2036 tcp Ethernet WS DP network [Peter_Kaever] [Peter_Kaever] 2005-08
e-dpnet 2036 udp Ethernet WS DP network [Peter_Kaever] [Peter_Kaever] 2005-08
applus 2037 tcp APplus Application Server [Alfred_Weindl] [Marcus_Schairer] 2008-06-06 2021-07-20 Unauthorized Use Known on port 2037 Formerly was P2plus Application Server
applus 2037 udp APplus Application Server [Alfred_Weindl] [Marcus_Schairer] 2008-06-06 2021-07-20 Unauthorized Use Known on port 2037 Formerly was P2plus Application Server
objectmanager 2038 tcp
objectmanager 2038 udp
prizma 2039 tcp Prizma Monitoring Service [Dotan_Ofek] [Dotan_Ofek] 2005-12
prizma 2039 udp Prizma Monitoring Service [Dotan_Ofek] [Dotan_Ofek] 2005-12
lam 2040 tcp
lam 2040 udp
interbase 2041 tcp
interbase 2041 udp
isis 2042 tcp isis
isis 2042 udp isis
isis-bcast 2043 tcp isis-bcast [Ken_Chapman] [Ken_Chapman]
isis-bcast 2043 udp isis-bcast [Ken_Chapman] [Ken_Chapman]
rimsl 2044 tcp
rimsl 2044 udp
cdfunc 2045 tcp
cdfunc 2045 udp
sdfunc 2046 tcp

Contact Information

ID Name Organization Contact URI Last Updated
[Alfred_Weindl] Alfred Weindl mailto:alfred.weindl&assecosol.com 2021-08-09
[Dan_Wing] Dan Wing mailto:danwing&gmail.com 2022-11-07
[Dotan_Ofek] Dotan Ofek mailto:dotan.ofek&prizmasoft.com 2005-12
[ITU-T] ITU-T mailto:tsbsg16&itu.int 2013-01-31
[ITU-T_TSB] ITU-T TSB ITU-T mailto:tsbsg16&itu.int 2013-01-31
[Ian_Wilson] Ian Wilson mailto:hsrp-info&cisco.com 2004-11
[Johannes_Skov_Frands] Johannes Skov Frandsen mailto:joe&42tools.com 2008-02-28
[Ken_Chapman] Ken Chapman mailto:kchapman&isis.com
[Marcus_Schairer] Marcus Schairer mailto:marcus.schairer&assecosol.com 2021-08-09
[Mike_O_Brien] Mike O'Brien mailto:mike&mobrien.com 2004-11
[Nic_Catrambone] Nic Catrambone mailto:ncatramb&us.ibm.com 2003-01
[Peter_Kaever] Peter Kaever mailto:kaever.peter&westfalia.com 2005-08
[Ryoichi_Shinohara] Ryoichi Shinohara mailto:shinohara&vnet.ibm.com