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
alpes 463 tcp alpes [Alain_Durand] [Alain_Durand]
alpes 463 udp alpes [Alain_Durand] [Alain_Durand]
nucleus 1463 tcp Nucleus [Venky_Nagar] [Venky_Nagar]
nucleus 1463 udp Nucleus [Venky_Nagar] [Venky_Nagar]
lsi-raid-mgmt 2463 tcp LSI RAID Management [NetApp] [MSW_architecture_team] 2014-07-18
lsi-raid-mgmt 2463 udp LSI RAID Management [NetApp] [MSW_architecture_team] 2014-07-18
edm-adm-notify 3463 tcp EDM ADM Notify
edm-adm-notify 3463 udp EDM ADM Notify
ttlpriceproxy 5463 tcp TTL Price Proxy [Peter_Jacobs] [Peter_Jacobs]
ttlpriceproxy 5463 udp TTL Price Proxy [Peter_Jacobs] [Peter_Jacobs]
6457-6463 Unassigned
ac-cluster 18463 tcp AC Cluster [Lisa_Zhong] [Lisa_Zhong]
ac-cluster 18463 udp AC Cluster [Lisa_Zhong] [Lisa_Zhong]
36463-36523 Unassigned
38463-38471 Unassigned
45967-46335 Unassigned
inedo 46336 tcp Listen port used for Inedo agent communication [Inedo] [Steve_Dennis] 2016-01-12
46336 udp Reserved
46337-46997 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Alain_Durand] Alain Durand mailto:Alain.Durand&imag.fr
[Inedo] Inedo mailto:support&inedo.com 2016-01-12
[Lisa_Zhong] Lisa Zhong mailto:lzhong&cup.hp.com
[MSW_architecture_team] MSW architecture team NetApp mailto:mswarch&netapp.com 2014-07-18
[NetApp] NetApp, Inc. mailto:mswarch&netapp.com 2014-07-18
[Peter_Jacobs] Peter Jacobs mailto:pjacobs&tullib.com
[Steve_Dennis] Steve Dennis mailto:sdennis&inedo.com 2016-01-12
[Venky_Nagar] Venky Nagar mailto:venky&fafner.stanford.edu