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
sst 266 tcp SCSI on ST [Donald_D_Woelz] [Donald_D_Woelz]
sst 266 udp SCSI on ST [Donald_D_Woelz] [Donald_D_Woelz]
dellpwrappks 1266 tcp DELLPWRAPPKS [David_Troeger] [David_Troeger]
dellpwrappks 1266 udp DELLPWRAPPKS [David_Troeger] [David_Troeger]
mfserver 2266 tcp M-Files Server [Samppa_Lahtinen] [Samppa_Lahtinen] 2004-06
mfserver 2266 udp M-files Server [Samppa_Lahtinen] [Samppa_Lahtinen] 2004-06
gcmonitor 2660 tcp GC Monitor [Gustavo_Rodriguez_Ri] [Gustavo_Rodriguez_Ri]
gcmonitor 2660 udp GC Monitor [Gustavo_Rodriguez_Ri] [Gustavo_Rodriguez_Ri]
olhost 2661 tcp OLHOST [Robert_Ripberger] [Robert_Ripberger]
olhost 2661 udp OLHOST [Robert_Ripberger] [Robert_Ripberger]
bintec-capi 2662 tcp BinTec-CAPI Unauthorized Use Known on port 2662
bintec-capi 2662 udp BinTec-CAPI Unauthorized Use Known on port 2662
bintec-tapi 2663 tcp BinTec-TAPI
bintec-tapi 2663 udp BinTec-TAPI
patrol-mq-gm 2664 tcp Patrol for MQ GM
patrol-mq-gm 2664 udp Patrol for MQ GM
patrol-mq-nm 2665 tcp Patrol for MQ NM [Portnoy_Boxman] [Portnoy_Boxman]
patrol-mq-nm 2665 udp Patrol for MQ NM [Portnoy_Boxman] [Portnoy_Boxman]
extensis 2666 tcp extensis [Milton_Sagen] [Milton_Sagen]
extensis 2666 udp extensis [Milton_Sagen] [Milton_Sagen]
alarm-clock-s 2667 tcp Alarm Clock Server
alarm-clock-s 2667 udp Alarm Clock Server
alarm-clock-c 2668 tcp Alarm Clock Client
alarm-clock-c 2668 udp Alarm Clock Client
toad 2669 tcp TOAD [Michael_Marking] [Michael_Marking]
toad 2669 udp TOAD [Michael_Marking] [Michael_Marking]
ns-cfg-server 3266 tcp NS CFG Server [Aivi_Lie] [Aivi_Lie]
ns-cfg-server 3266 udp NS CFG Server [Aivi_Lie] [Aivi_Lie]
5266-5268 Unassigned
6254-6266 Unassigned
8266 tcp Reserved
espeasy-p2p 8266 udp ESPeasy peer-2-peer communication [ESPeasy] [Gijs_Noorlander] 2018-11-28

Contact Information

ID Name Organization Contact URI Last Updated
[Aivi_Lie] Aivi Lie mailto:LIEA&netsoft.com
[David_Troeger] David Troeger mailto:David_Troeger&dell.com
[Donald_D_Woelz] Donald D. Woelz mailto:don&genroco.com
[ESPeasy] ESPeasy mailto:gijs.noorlander&gmail.com 2018-11-28
[Gijs_Noorlander] Gijs Noorlander mailto:gijs.noorlander&gmail.com 2018-11-28
[Gustavo_Rodriguez_Ri] Gustavo Rodriguez-Rivera mailto:grr&geodesic.com
[Michael_Marking] Michael Marking mailto:marking&tatanka.com
[Milton_Sagen] Milton Sagen mailto:msagen&extensis.com
[Portnoy_Boxman] Portnoy Boxman mailto:portnoy_boxman&bmc.com 2005-01
[Robert_Ripberger] Robert Ripberger mailto:rip&lan-aces.com 2017-02-08
[Samppa_Lahtinen] Samppa Lahtinen mailto:samppa.lahtinen&motivesys.com 2004-06