Service Name and Transport Protocol Port Number Registry

Last Updated
2026-08-17
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
compaq-evm 619 tcp Compaq EVM [Jem_Treadwell] [Jem_Treadwell]
compaq-evm 619 udp Compaq EVM [Jem_Treadwell] [Jem_Treadwell]
xs-openstorage 1619 tcp xs-openstorage [XuiS_Software_Ltd] [XuiS_Software_Ltd]
xs-openstorage 1619 udp xs-openstorage [XuiS_Software_Ltd] [XuiS_Software_Ltd]
bruce 2619 tcp bruce [Alec_Muffett] [Alec_Muffett]
bruce 2619 udp bruce [Alec_Muffett] [Alec_Muffett]
aairnet-2 3619 tcp AAIR-Network 2 [James_Mealey] [James_Mealey] 2002-10
aairnet-2 3619 udp AAIR-Network 2 [James_Mealey] [James_Mealey] 2002-10
5619-5626 Unassigned
6164-6199 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]
9619-9627 Unassigned
xoms 16619 tcp X509 Objects Management Service [Francis_GASCHET] [Francis_GASCHET] 2008-09-08
16619 udp Reserved
31458-31619 Unassigned
iqobject 48619 tcp iqobject [Bjorn_de_Bonnenfant] [Bjorn_de_Bonnenfant] 2003-11
iqobject 48619 udp iqobject [Bjorn_de_Bonnenfant] [Bjorn_de_Bonnenfant] 2003-11

Contact Information

ID Name Organization Contact URI Last Updated
[Alec_Muffett] Alec Muffett mailto:alecm&sun.com
[Bjorn_de_Bonnenfant] Bjorn de Bonnenfant mailto:bdeb&iqobject.com 2003-11
[Francis_GASCHET] Francis GASCHET NUMLOG mailto:fg&numlog.fr 2008-09-08
[Ieuan_Friend] Ieuan Friend mailto:ieuan.friend&dip.co.uk 2006-03
[James_Mealey] James Mealey mailto:jymealey&yahoo.com 2002-10
[Jem_Treadwell] Jem Treadwell mailto:Jem.Treadwell&compaq.com
[XuiS_Software_Ltd] XuiS Software Ltd. mailto:100322.2376&compuserve.com