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
itm-mcell-s 828 tcp itm-mcell-s [Portnoy_Boxman] [Portnoy_Boxman]
itm-mcell-s 828 udp itm-mcell-s [Portnoy_Boxman] [Portnoy_Boxman]
itm-mcell-u 1828 tcp itm-mcell-u [Portnoy_Boxman] [Portnoy_Boxman]
itm-mcell-u 1828 udp itm-mcell-u [Portnoy_Boxman] [Portnoy_Boxman]
itm-lm 2828 tcp ITM License Manager [Portnoy_Boxman] [Portnoy_Boxman]
itm-lm 2828 udp ITM License Manager [Portnoy_Boxman] [Portnoy_Boxman]
neteh 3828 tcp Netadmin Systems Event Handler
neteh 3828 udp Netadmin Systems Event Handler
4828-4836 Unassigned
synapse-nhttp 8280 tcp Synapse Non Blocking HTTP [Ruwan_Linton] [Ruwan_Linton] 2008-06-05
synapse-nhttp 8280 udp Synapse Non Blocking HTTP [Ruwan_Linton] [Ruwan_Linton] 2008-06-05
8281 Unassigned
libelle 8282 tcp Libelle EnterpriseBus [Libelle_AG] [Hans-Joachim_Krueger] 2016-02-17
libelle-disc 8282 udp Libelle EnterpriseBus discovery [Libelle_AG] [Hans-Joachim_Krueger] 2016-02-17
8282 sctp Reserved
8282 dccp Reserved
8283-8291 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Hans-Joachim_Krueger] Hans Joachim Krueger mailto:hkrueger&libelle.com 2016-02-17
[Libelle_AG] Libelle AG mailto:hkrueger&libelle.com 2016-02-17
[Portnoy_Boxman] Portnoy Boxman mailto:portnoy_boxman&bmc.com 2005-01
[Ruwan_Linton] Ruwan Linton mailto:ruwan&wso2.com 2008-08-20