Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-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
passgo-tivoli 627 tcp PassGo Tivoli [John_Rainford_2] [John_Rainford_2]
passgo-tivoli 627 udp PassGo Tivoli [John_Rainford_2] [John_Rainford_2]
t128-gateway 1627 tcp T.128 Gateway [Phil_May] [Phil_May]
t128-gateway 1627 udp T.128 Gateway [Phil_May] [Phil_May]
moshebeeri 2627 tcp Moshe Beeri [Moshe_Beeri] [Moshe_Beeri]
moshebeeri 2627 udp Moshe Beeri [Moshe_Beeri] [Moshe_Beeri]
jamserverport 3627 tcp Jam Server Port [Art_Pope] [Art_Pope] 2002-10
jamserverport 3627 udp Jam Server Port [Art_Pope] [Art_Pope] 2002-10
ninaf 5627 tcp Node Initiated Network Association Forma [Thomas_Scholl] [Thomas_Scholl] 2006-03
ninaf 5627 udp Node Initiated Network Association Forma [Thomas_Scholl] [Thomas_Scholl] 2006-03
6270-6299 Unassigned
nexgen 6627 tcp Allied Electronics NeXGen [Lou_Seitchik] [Lou_Seitchik] 2005-08
nexgen 6627 udp Allied Electronics NeXGen [Lou_Seitchik] [Lou_Seitchik] 2005-08
soap-http 7627 tcp SOAP Service Port [Donald_Dylla] [Donald_Dylla] 2004-12
soap-http 7627 udp SOAP Service Port [Donald_Dylla] [Donald_Dylla] 2004-12
9619-9627 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Art_Pope] Art Pope mailto:apope&sarnoff.com 2002-10
[Donald_Dylla] Donald Dylla mailto:donald.dylla&hp.com 2004-12
[John_Rainford_2] John Rainford mailto:john.rainford&passgo.com
[Lou_Seitchik] Lou Seitchik mailto:lou&alliedelectronics.com 2005-08
[Moshe_Beeri] Moshe Beeri mailto:moshe&whale-com.com
[Phil_May] Phil May mailto:pm&datcon.co.uk
[Thomas_Scholl] Thomas Scholl mailto:tscholl&spf.is-is.ca 2006-03