Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-11-10

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

  • RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

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 basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.

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.

Registration Forms

Available Formats

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-Rivera Gustavo Rodriguez-Rivera
gcmonitor 2660 udp GC Monitor Gustavo Rodriguez-Rivera Gustavo Rodriguez-Rivera
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

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