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
cal 588 tcp CAL [Myron_Hattig] [Myron_Hattig]
cal 588 udp CAL [Myron_Hattig] [Myron_Hattig]
triquest-lm 1588 tcp triquest-lm [Nand_Kumar] [Nand_Kumar]
triquest-lm 1588 udp triquest-lm [Nand_Kumar] [Nand_Kumar]
privilege 2588 tcp Privilege [Gil_Hecht] [Gil_Hecht]
privilege 2588 udp Privilege [Gil_Hecht] [Gil_Hecht]
sentinel 3588 tcp Sentinel Server [Ian_Gordon] [Ian_Gordon] 2002-08
sentinel 3588 udp Sentinel Server [Ian_Gordon] [Ian_Gordon] 2002-08
bfd-control 3784 tcp BFD Control Protocol [RFC5881]
bfd-control 3784 udp BFD Control Protocol [RFC5881]
bfd-echo 3785 tcp BFD Echo Protocol [RFC5881]
bfd-echo 3785 udp BFD Echo Protocol [RFC5881]
diameter 3868 sctp DIAMETER [RFC3588]
5869-5882 Unassigned
jute 5883 tcp Javascript Unit Test Environment [Mark_Ethan_Trostler] [Mark_Ethan_Trostler] 2011-11-23
5884-5899 Unassigned
6588 Unassigned Unofficial use of port 6588 by AnalogX and Microsoft
sun-lm 7588 tcp Sun License Manager [Sophie_Deng] [Sophie_Deng]
sun-lm 7588 udp Sun License Manager [Sophie_Deng] [Sophie_Deng]
28241-28588 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Gil_Hecht] Gil Hecht mailto:GilH&aks.com
[Ian_Gordon] Ian Gordon mailto:ian.s.gordon&btopenworld.com 2002-08
[Mark_Ethan_Trostler] Mark Ethan Trostler mailto:mark&zzo.com 2011-11-23
[Myron_Hattig] Myron Hattig mailto:Myron_Hattig&ccm.jf.intel.com
[Nand_Kumar] Nand Kumar mailto:nkumar&triquest-da.com
[Sophie_Deng] Sophie Deng mailto:Sophie.Deng&eng.sun.com