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
dsfgw 438 tcp dsfgw [Andy_McKeen] [Andy_McKeen]
dsfgw 438 udp dsfgw [Andy_McKeen] [Andy_McKeen]
eicon-server 1438 tcp Eicon Security Agent/Server
eicon-server 1438 udp Eicon Security Agent/Server
msp 2438 tcp MSP [Evan_Caves] [Evan_Caves]
msp 2438 udp MSP [Evan_Caves] [Evan_Caves]
spiral-admin 3438 tcp Spiralcraft Admin [Michael_Toth] [Michael_Toth] 2002-03
spiral-admin 3438 udp Spiralcraft Admin [Michael_Toth] [Michael_Toth] 2002-03
teredo 3544 tcp Teredo Port [RFC4380]
teredo 3544 udp Teredo Port [RFC4380]
4380-4388 Unassigned
xandros-cms 4389 tcp Xandros Community Management Service [Stephen_M_Webb] [Stephen_M_Webb] 2007-05
xandros-cms 4389 udp Xandros Community Management Service [Stephen_M_Webb] [Stephen_M_Webb] 2007-05
5438-5442 Unassigned
7438-7442 Unassigned
10322-10438 Unassigned
24324-24385 Unassigned
intel-rci 24386 tcp Intel RCI

IANA assigned this well-formed service name as a replacement for "intel_rci".
[Mark_Lewis_2] [Mark_Lewis_2]
intel_rci 24386 tcp Intel RCI [Mark_Lewis_2] [Mark_Lewis_2] This entry is an alias to "intel-rci". This entry is now historic, not usable for use with many common service discovery mechanisms.
intel-rci 24386 udp Intel RCI

IANA assigned this well-formed service name as a replacement for "intel_rci".
[Mark_Lewis_2] [Mark_Lewis_2]
intel_rci 24386 udp Intel RCI [Mark_Lewis_2] [Mark_Lewis_2] This entry is an alias to "intel-rci". This entry is now historic, not usable for use with many common service discovery mechanisms.
24387-24464 Unassigned
34380-34566 Unassigned
43438 tcp Reserved
hmip-routing 43438 udp HmIP LAN Routing [eQ-3_Entwicklung_GmbH] [Tido_de_Vries] 2018-02-28
pkixrep Public Key Infrastructure Repository Locator Service [RFC4386]

Contact Information

ID Name Organization Contact URI Last Updated
[Andy_McKeen] Andy McKeen mailto:mckeen&osf.org
[eQ-3_Entwicklung_GmbH] eQ-3 Entwicklung GmbH mailto:ports&entwicklung.eq-3.de 2018-02-28
[Evan_Caves] Evan Caves mailto:evan&acc.com
[Mark_Lewis_2] Mark Lewis mailto:mark.h.lewis&intel.com
[Michael_Toth] Michael Toth mailto:iana&spiralcraft.com 2002-03
[Stephen_M_Webb] Stephen M. Webb mailto:stephenw&xandros.com 2007-05
[Tido_de_Vries] Tido de Vries eQ-3 Entwicklung GmbH mailto:tido.devries&entwicklung.eq-3.de 2018-02-28