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
eudora-set 592 tcp Eudora Set [Randall_Gellens] [Randall_Gellens]
eudora-set 592 udp Eudora Set [Randall_Gellens] [Randall_Gellens]
commonspace 1592 tcp commonspace [Rob_Chandhok_2] [Rob_Chandhok_2]
commonspace 1592 udp commonspace [Rob_Chandhok_2] [Rob_Chandhok_2]
netrek 2592 tcp netrek [Al_Guetzlaff] [Al_Guetzlaff]
netrek 2592 udp netrek [Al_Guetzlaff] [Al_Guetzlaff]
gtrack-ne 3592 tcp LOCANIS G-TRACK NE Port [Juergen_Edelhaeuser] [Juergen_Edelhaeuser] 2002-08
gtrack-ne 3592 udp LOCANIS G-TRACK NE Port [Juergen_Edelhaeuser] [Juergen_Edelhaeuser] 2002-08
4592 tcp Reserved
hrpd-ith-at-an 4592 udp HRPD-ITH (AT-AN) [David_Ott] [David_Ott] 2008-06-05
snmpssh 5161 tcp SNMP over SSH Transport Model [RFC5592]
snmpssh-trap 5162 tcp SNMP Notification over SSH Transport Model [RFC5592] Known Unauthorized Use on port 5162
ldgateway 9592 tcp LANDesk Gateway [Alan_Butt] [Alan_Butt] 2006-03
ldgateway 9592 udp LANDesk Gateway [Alan_Butt] [Alan_Butt] 2006-03

Contact Information

ID Name Contact URI Last Updated
[Al_Guetzlaff] Al Guetzlaff mailto:aeg&teamquest.com
[Alan_Butt] Alan Butt mailto:alan.butt&landesk.com 2006-03
[David_Ott] David Ott mailto:dott&qualcomm.com 2010-10-15
[Juergen_Edelhaeuser] Juergen Edelhaeuser mailto:Juergen.Edelhaeuser&locanis.com 2002-08
[Randall_Gellens] Randall Gellens mailto:rg+ietf&coretechnologyconsulting.com 2024-07-29
[Rob_Chandhok_2] Rob Chandhok mailto:chandhok&within.com