Service Name and Transport Protocol Port Number Registry

Last Updated
2026-03-27
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, 
Jana Iyengar, 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
commplex-main 5000 tcp
commplex-main 5000 udp
hydap 15000 tcp Hypack Data Aquisition [HYPACK_Inc] [Mircea_Neacsu] 2011-10-27
hydap 15000 udp Hypack Data Aquisition [HYPACK_Inc] [Mircea_Neacsu] 2011-10-27
icl-twobase1 25000 tcp icl-twobase1 [J_A_Sever] [J_A_Sever]
icl-twobase1 25000 udp icl-twobase1 [J_A_Sever] [J_A_Sever]
heathview 35000 tcp HeathView [Heathwest_Systems_Limited] [Andrew_Porrer] 2013-03-21
35000 udp Reserved
asmp 45000 tcp Nuance AutoStore Status Monitoring Protocol (data transfer) [Nuance_Communications_Inc4] [Andrew_Andrews] 2011-09-01 2017-04-26
asmp-mon 45000 udp Nuance AutoStore Status Monitoring Protocol (device monitoring) [Nuance_Communications_Inc4] [Andrew_Andrews] 2011-09-01 2017-04-26

Contact Information

ID Name Organization Contact URI Last Updated
[Andrew_Andrews] Andrew Andrews mailto:Andrew.Andrews&Nuance.com 2017-04-26
[Andrew_Porrer] Andrew Porrer Heathwest Systems Limited mailto:Andrew.Porrer&heathwest.com 2013-03-21
[Heathwest_Systems_Limited] Heathwest Systems Limited mailto:info&heathwest.com 2013-03-21
[HYPACK_Inc] HYPACK Inc. mailto:mircea&hypack.com 2011-10-27
[J_A_Sever] J. A. (Tony) Sever mailto:J.A.Sever&bra0119.wins.icl.co.uk
[Mircea_Neacsu] Mircea Neacsu mailto:mircea&hypack.com 2011-10-27
[Nuance_Communications_Inc4] Nuance Communications, Inc. mailto:dev&nsius.com 2017-04-26