Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-07
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
scp 3820 tcp Siemens AuD SCP [Johann_Arnold] [Johann_Arnold] 2004-10
scp 3820 udp Siemens AuD SCP [Johann_Arnold] [Johann_Arnold] 2004-10
dsmcc-passthru 13820 tcp DSMCC Pass-Thru Messages [Tim_Addington] [Tim_Addington] [ISO/IEC 13818-6 MPEG-2 DSM-CC]
dsmcc-passthru 13820 udp DSMCC Pass-Thru Messages [Tim_Addington] [Tim_Addington] [ISO/IEC 13818-6 MPEG-2 DSM-CC]
38003-38200 Unassigned
galaxy7-data 38201 tcp Galaxy7 Data Tunnel [Tatham_Oddie] [Tatham_Oddie] 2002-09
galaxy7-data 38201 udp Galaxy7 Data Tunnel [Tatham_Oddie] [Tatham_Oddie] 2002-09
fairview 38202 tcp Fairview Message Service [Jim_Lyle] [Jim_Lyle] 2005-11 Defined TXT keys: DevID=<device id>, DevType=<device type>, DevStat=<device status>
fairview 38202 udp Fairview Message Service [Jim_Lyle] [Jim_Lyle] 2005-11 Defined TXT keys: DevID=<device id>, DevType=<device type>, DevStat=<device status>
agpolicy 38203 tcp AppGate Policy Server [Martin_Forssen] [Martin_Forssen] 2004-11
agpolicy 38203 udp AppGate Policy Server [Martin_Forssen] [Martin_Forssen] 2004-11
38204-38411 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Jim_Lyle] Jim Lyle mailto:jim.lyle&siliconimage.com 2005-11
[Johann_Arnold] Johann Arnold mailto:johann.arnold&siemens.com 2004-10
[Martin_Forssen] Martin Forssen mailto:maf&appgate.com 2004-11
[Tatham_Oddie] Tatham Oddie mailto:tatham&e-oddie.com 2002-09
[Tim_Addington] Tim Addington mailto:Tim.Addington&sciatl.com