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
micom-pfs 490 tcp micom-pfs [David_Misunas] [David_Misunas]
micom-pfs 490 udp micom-pfs [David_Misunas] [David_Misunas]
insitu-conf 1490 tcp insitu-conf [Paul_Blacknell] [Paul_Blacknell]
insitu-conf 1490 udp insitu-conf [Paul_Blacknell] [Paul_Blacknell]
qip-qdhcp 2490 tcp qip_qdhcp [Mike_Morgan] [Mike_Morgan]
qip-qdhcp 2490 udp qip_qdhcp [Mike_Morgan] [Mike_Morgan]
colubris 3490 tcp Colubris Management Port [Gilbert_Moineau] [Gilbert_Moineau] 2002-05
colubris 3490 udp Colubris Management Port [Gilbert_Moineau] [Gilbert_Moineau] 2002-05
4489-4499 Unassigned Known UNAUTHORIZED USE: Ports 4490 and 4491
hfcs 4900 tcp HFSQL Client/Server Database Engine [PC_SOFT] [Jerome_AERTS_2] 2006-03-02 2014-02-02
hfcs 4900 udp HFSQL Client/Server Database Engine [PC_SOFT] [Jerome_AERTS_2] 2006-03-02 2014-02-02
flr-agent 4901 tcp FileLocator Remote Search Agent

IANA assigned this well-formed service name as a replacement for "flr_agent".
[David_Vest] [David_Vest] 2008-11-19
flr_agent 4901 tcp FileLocator Remote Search Agent [David_Vest] [David_Vest] 2008-11-19 This entry is an alias to "flr-agent". This entry is now historic, not usable for use with many common service discovery mechanisms.
4901 udp Reserved
magiccontrol 4902 tcp magicCONROL RF and Data Interface [Andreas_Spalenski] [Andreas_Spalenski] 2008-11-24
4902 udp Reserved
4903-4911 Unassigned
6490-6499 Unassigned
7479-7490 Unassigned
11490-11599 Unassigned
26490-26999 Unassigned
m3da 44900 tcp M3DA is used for efficient machine-to-machine communications [Eclipse_Foundation] [Didier_Lahay] 2013-02-22
m3da-disc 44900 udp M3DA Discovery is used for efficient machine-to-machine communications [Eclipse_Foundation] [Didier_Lahay] 2013-02-22
44901-44999 Unassigned
matahari 49000 tcp Matahari Broker [Matahari_Project] [Zane_Bitter] 2011-08-31
49000 udp Reserved
nusrp 49001 tcp Nuance Unity Service Request Protocol [Nuance_Communications_Inc3] [Andrew_Andrews] 2017-04-20
nusdp-disc 49001 udp Nuance Unity Service Discovery Protocol [Nuance_Communications_Inc3] [Andrew_Andrews] 2017-04-20
49002-49149 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Andreas_Spalenski] Andreas Spalenski mailto:andreas.spalenski&trsystems.de 2008-11-24
[Andrew_Andrews] Andrew Andrews mailto:Andrew.Andrews&Nuance.com 2017-04-26
[David_Misunas] David Misunas mailto:DMisunas&micom.com
[David_Vest] David Vest mailto:dave&mythicsoft.com 2008-11-19
[Didier_Lahay] Didier Lahay mailto:dlahay&sierrawireless.com 2013-02-22
[Eclipse_Foundation] Eclipse Foundation mailto:license&eclipse.org 2013-02-22
[Gilbert_Moineau] Gilbert Moineau mailto:gilbert.moineau&colubris.com 2002-05
[Jerome_AERTS_2] Jerome AERTS PC SOFT mailto:jae&pcsoft.fr 2014-02-02
[Matahari_Project] Matahari Project mailto:matahari&lists.fedorahosted.org 2011-08-31
[Mike_Morgan] Mike Morgan mailto:mmorgan&lucent.com
[Nuance_Communications_Inc3] Nuance Communications, Inc. mailto:Andrew.Andrews&Nuance.com 2017-04-20
[Paul_Blacknell] Paul Blacknell mailto:paul&insitu.com
[PC_SOFT] PC SOFT mailto:jae&pcsoft.fr 2014-02-02
[Zane_Bitter] Zane Bitter mailto:zbitter&redhat.com 2011-08-31