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
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
netconf-beep NETCONF over BEEP [RFC4744][RFC9900]
netconfsoapbeep NETCONF for SOAP over BEEP [RFC4743][RFC9900]
netconfsoaphttp NETCONF for SOAP over HTTPS [RFC4743][RFC9900]

Contact Information

ID Name Organization Contact URI Last Updated
[Andrew_Andrews] Andrew Andrews mailto:Andrew.Andrews&Nuance.com 2017-04-26
[Didier_Lahay] Didier Lahay mailto:dlahay&sierrawireless.com 2013-02-22
[Eclipse_Foundation] Eclipse Foundation mailto:license&eclipse.org 2013-02-22
[Matahari_Project] Matahari Project mailto:matahari&lists.fedorahosted.org 2011-08-31
[Nuance_Communications_Inc3] Nuance Communications, Inc. mailto:Andrew.Andrews&Nuance.com 2017-04-20
[Zane_Bitter] Zane Bitter mailto:zbitter&redhat.com 2011-08-31