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
npmp-trap 609 tcp npmp-trap
npmp-trap 609 udp npmp-trap
isysg-lm 1609 tcp isysg-lm [Adam_Curtin] [Adam_Curtin]
isysg-lm 1609 udp isysg-lm [Adam_Curtin] [Adam_Curtin]
system-monitor 2609 tcp System Monitor [Greg_Robson_Garth] [Greg_Robson_Garth]
system-monitor 2609 udp System Monitor [Greg_Robson_Garth] [Greg_Robson_Garth]
cpdi-pidas-cm 3609 tcp CPDI PIDAS Connection Mon [Tony_Splaver] [Tony_Splaver] 2002-09
cpdi-pidas-cm 3609 udp CPDI PIDAS Connection Mon [Tony_Splaver] [Tony_Splaver] 2002-09
6089-6098 Unassigned
raxa-mgmt 6099 tcp RAXA Management [Sukanta_Ganguly] [Sukanta_Ganguly]
6099 udp Reserved
6603-6609 Unassigned
8609 tcp Reserved
canon-cpp-disc 8609 udp Canon Compact Printer Protocol Discovery [Canon_Inc] [Ryusuke_Okuhara] 2012-06-08 2012-06-15

Contact Information

ID Name Organization Contact URI Last Updated
[Adam_Curtin] Adam Curtin mailto:adam.curtin&isysg.com
[Canon_Inc] Canon Inc. mailto:fujii.ken-ichi149&canon.co.jp 2011-10-10
[Greg_Robson_Garth] Greg Robson-Garth mailto:gregr&alphalink.com.au
[Ryusuke_Okuhara] Ryusuke Okuhara Canon Inc. mailto:okuhara.ryuusuke&canon.co.jp 2012-06-08
[Sukanta_Ganguly] Sukanta Ganguly mailto:sganguly&kineticnetworks.com
[Tony_Splaver] Tony Splaver mailto:tony&cpdi.com 2002-09