Service Name and Transport Protocol Port Number Registry

Last Updated
2025-10-30
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
hap 661 tcp HAP [Igor_Plotnikov] [Igor_Plotnikov]
hap 661 udp HAP [Igor_Plotnikov] [Igor_Plotnikov]
netview-aix-1 1661 tcp netview-aix-1
netview-aix-1 1661 udp netview-aix-1
radsec 2083 tcp Secure Radius Service [IESG] [IETF_Chair] 2005-05 [RFC6614] The TCP port 2083 was already previously assigned by IANA for "RadSec", an early implementation of RADIUS/TLS, prior to issuance of this RFC. This early implementation can be configured to be compatible to RADIUS/TLS as specified by the IETF. See [RFC6614], Appendix A for details.
olhost 2661 tcp OLHOST [Robert_Ripberger] [Robert_Ripberger]
olhost 2661 udp OLHOST [Robert_Ripberger] [Robert_Ripberger]
can-ferret-ssl 3661 tcp IBM Tivoli Directory Service using SSL [Nic_Catrambone] [Nic_Catrambone] 2003-01
can-ferret-ssl 3661 udp IBM Tivoli Directory Service using SSL [Nic_Catrambone] [Nic_Catrambone] 2003-01
kar2ouche 4661 tcp Kar2ouche Peer location service [Andy_Krouwel] [Andy_Krouwel]
kar2ouche 4661 udp Kar2ouche Peer location service [Andy_Krouwel] [Andy_Krouwel]
6603-6618 Unassigned
odette-ftps 6619 tcp ODETTE-FTP over TLS/SSL [Ieuan_Friend] [Ieuan_Friend] 2006-03 [RFC5024]
odette-ftps 6619 udp ODETTE-FTP over TLS/SSL [Ieuan_Friend] [Ieuan_Friend] 2006-03 [RFC5024]
mipv6tls 7872 udp TLS-based Mobile IPv6 Security [IESG] [IETF_Chair] 2012-04-12 [RFC6618]
15661-15739 Unassigned
16386-16618 Unassigned
xoms 16619 tcp X509 Objects Management Service [Francis_GASCHET] [Francis_GASCHET] 2008-09-08
16619 udp Reserved

Contact Information

ID Name Organization Contact URI Last Updated
[Andy_Krouwel] Andy Krouwel mailto:andy&kar2ouche.com
[Francis_GASCHET] Francis GASCHET NUMLOG mailto:fg&numlog.fr 2008-09-08
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Ieuan_Friend] Ieuan Friend mailto:ieuan.friend&dip.co.uk 2006-03
[Igor_Plotnikov] Igor Plotnikov mailto:igor&uroam.com
[Nic_Catrambone] Nic Catrambone mailto:ncatramb&us.ibm.com 2003-01
[Robert_Ripberger] Robert Ripberger mailto:rip&lan-aces.com 2017-02-08