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
eyelink 589 tcp EyeLink [Dave_Stampe] [Dave_Stampe]
eyelink 589 udp EyeLink [Dave_Stampe] [Dave_Stampe]
vqp 1589 tcp VQP [Keith_McCloghrie] [Keith_McCloghrie]
vqp 1589 udp VQP [Keith_McCloghrie] [Keith_McCloghrie]
quartus-tcl 2589 tcp quartus tcl [Subroto_Datta] [Subroto_Datta]
quartus-tcl 2589 udp quartus tcl [Subroto_Datta] [Subroto_Datta]
isomair 3589 tcp isomair [Richard_Fleming] [Richard_Fleming] 2002-08
isomair 3589 udp isomair [Richard_Fleming] [Richard_Fleming] 2002-08
4574-4589 Unassigned
5884-5899 Unassigned
netconf-tls 6513 tcp NETCONF over TLS [IESG] [IETF_Chair] 2024-01-24 [RFC7589][RFC9918]
6589-6599 Unassigned
7589-7605 Unassigned
21555-21589 Unassigned
25794-25899 Unassigned
bosswave 28589 tcp Building operating system services wide area verified exchange [University_of_California_Berkeley] [Michael_Andersen] 2016-06-13
28589 udp Reserved

Contact Information

ID Name Organization Contact URI Last Updated
[Dave_Stampe] Dave Stampe mailto:dstampe&psych.toronto.edu
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Keith_McCloghrie] Keith McCloghrie mailto:kzm&cisco.com
[Michael_Andersen] Michael Andersen mailto:michael&steelcode.com 2016-06-13
[Richard_Fleming] Richard Fleming mailto:richard&apoapsis.com 2002-08
[Subroto_Datta] Subroto Datta mailto:subrotod&altera.com
[University_of_California_Berkeley] University of California, Berkeley mailto:m.andersen&cs.berkeley.edu 2016-06-13