Service Name and Transport Protocol Port Number Registry

Last Updated
2021-02-25
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
pop3s 995 tcp POP3 over TLS protocol [IESG] [IETF_Chair] 2017-12-12 [RFC8314]
pop3s 995 udp pop3 protocol over TLS/SSL (was spop3) [Gordon_Mangione] [Gordon_Mangione]
perf-port 1995 tcp cisco perf port
perf-port 1995 udp cisco perf port
idrs 2995 tcp IDRS [Jeff_Eaton] [Jeff_Eaton]
idrs 2995 udp IDRS [Jeff_Eaton] [Jeff_Eaton]
iss-mgmt-ssl 3995 tcp ISS Management Svcs SSL [Wes_Wilson] [Wes_Wilson] 2003-10
iss-mgmt-ssl 3995 udp ISS Management Svcs SSL [Wes_Wilson] [Wes_Wilson] 2003-10
apc-9950 9950 tcp APC 9950 [American_Power_Conve] [American_Power_Conve]
apc-9950 9950 udp APC 9950 [American_Power_Conve] [American_Power_Conve]
apc-9951 9951 tcp APC 9951 [American_Power_Conve] [American_Power_Conve]
apc-9951 9951 udp APC 9951 [American_Power_Conve] [American_Power_Conve]
apc-9952 9952 tcp APC 9952 [American_Power_Conve] [American_Power_Conve]
apc-9952 9952 udp APC 9952 [American_Power_Conve] [American_Power_Conve]
acis 9953 tcp 9953 [Thomas_Guth] [Thomas_Guth] 2006-01
acis 9953 udp 9953 [Thomas_Guth] [Thomas_Guth] 2006-01
hinp 9954 tcp HaloteC Instrument Network Protocol [HaloteC_Instruments] [Michel_Stam] 2012-02-07
9954 udp Reserved
alljoyn-stm 9955 tcp Contact Port for AllJoyn standard messaging [Qualcomm_Innovation_Center] [Craig_Dowell] 2012-03-14
alljoyn-mcm 9955 udp Contact Port for AllJoyn multiplexed constrained messaging [Qualcomm_Innovation_Center] [Craig_Dowell] 2012-03-14
9956 tcp Reserved
alljoyn 9956 udp Alljoyn Name Service [Qualcomm_Innovation_Center] [Craig_Dowell] 2011-12-21
9957-9965 Unassigned
palace-4 9995 tcp Palace-4 [Douglas_Crockford] [Douglas_Crockford]
palace-4 9995 udp Palace-4 [Douglas_Crockford] [Douglas_Crockford]
amt-redir-tls 16995 tcp Intel(R) AMT Redirection/TLS [Nimrod_Diamant] [Nimrod_Diamant] 2005-02
amt-redir-tls 16995 udp Intel(R) AMT Redirection/TLS [Nimrod_Diamant] [Nimrod_Diamant] 2005-02

Contact Information

ID Name Organization Contact URI Last Updated
[American_Power_Conve] American Power Conversion mailto:ports&apcc.com 2002-02
[Craig_Dowell] Craig Dowell Qualcomm Innovation Center, Inc. mailto:cdowell&quicinc.com 2011-12-21
[Douglas_Crockford] Douglas Crockford mailto:douglas&crockford.com
[Gordon_Mangione] Gordon Mangione mailto:gordm&microsoft.com
[HaloteC_Instruments] HaloteC Instruments B.V. mailto:michel.stam&halotec.com 2012-02-07
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jeff_Eaton] Jeff Eaton mailto:jeaton&intermec.com
[Michel_Stam] Michel Stam HaloteC Instruments B.V. mailto:michel.stam&halotec.com 2012-02-07
[Nimrod_Diamant] Nimrod Diamant mailto:nimrod.diamant&intel.com 2005-02
[Qualcomm_Innovation_Center] Qualcomm Innovation Center, Inc. mailto:cdowell&quicinc.com 2011-12-21
[Thomas_Guth] Thomas Guth mailto:t.guth&zeiss.de 2006-01
[Wes_Wilson] Wes Wilson mailto:wwilson&iss.net 2003-10