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
repscmd 653 tcp RepCmd [Scott_Dale_2] [Scott_Dale_2]
repscmd 653 udp RepCmd [Scott_Dale_2] [Scott_Dale_2]
alphatech-lm 1653 tcp alphatech-lm [Joseph_Hauk] [Joseph_Hauk]
alphatech-lm 1653 udp alphatech-lm [Joseph_Hauk] [Joseph_Hauk]
sonus 2653 tcp Sonus [Mark_Garti] [Mark_Garti]
sonus 2653 udp Sonus [Mark_Garti] [Mark_Garti]
tsp 3653 tcp Tunnel Setup Protocol [Marc_Blanchet] [Marc_Blanchet] 2003-01 [RFC5572]
tsp 3653 udp Tunnel Setup Protocol [Marc_Blanchet] [Marc_Blanchet] 2003-01 [RFC5572]
openflow 6653 tcp OpenFlow [Open_Networking_Foundation] [Puneet_Agarwal] 2013-07-18
openflow 6653 udp OpenFlow [Open_Networking_Foundation] [Puneet_Agarwal] 2013-07-18
37602-37653 Unassigned
robotraconteur 48653 tcp Robot Raconteur transport [Wason_Technology_LLC] [John_Wason] 2014-01-27
robotraconteur 48653 udp Robot Raconteur transport [Wason_Technology_LLC] [John_Wason] 2014-01-27

Contact Information

ID Name Organization Contact URI Last Updated
[John_Wason] John Wason Wason Technology, LLC mailto:wason&wasontech.com 2014-01-27
[Joseph_Hauk] Joseph Hauk mailto:joseph.hauk&alphatech.com
[Marc_Blanchet] Marc Blanchet mailto:marc.blanchet&viagenie.ca 2003-01
[Mark_Garti] Mark Garti mailto:mgarti&sonusnet.com
[Open_Networking_Foundation] Open Networking Foundation mailto:iana&opennetworking.org 2013-07-18
[Puneet_Agarwal] Puneet Agarwal mailto:pagarwal&broadcom.com 2013-07-18
[Scott_Dale_2] Scott Dale mailto:scott&tioga.com
[Wason_Technology_LLC] Wason Technology, LLC mailto:wason&wasontech.com 2014-01-27