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
as-servermap 449 tcp AS Server Mapper [Barbara_Foss] [Barbara_Foss]
as-servermap 449 udp AS Server Mapper [Barbara_Foss] [Barbara_Foss]
peport 1449 tcp PEport [Qentin_Neill] [Qentin_Neill]
peport 1449 udp PEport [Qentin_Neill] [Qentin_Neill]
ratl 2449 tcp RATL [Paul_Greenfield] [Paul_Greenfield]
ratl 2449 udp RATL [Paul_Greenfield] [Paul_Greenfield]
hotu-chat 3449 tcp HotU Chat [Tim_Burgess] [Tim_Burgess] 2002-04
hotu-chat 3449 udp HotU Chat [Tim_Burgess] [Tim_Burgess] 2002-04
privatewire 4449 tcp PrivateWire [Uri_Resnitzky] [Uri_Resnitzky]
privatewire 4449 udp PrivateWire [Uri_Resnitzky] [Uri_Resnitzky]
4489-4499 Unassigned Known UNAUTHORIZED USE: Ports 4490 and 4491
5446-5449 Unassigned
8449 Unassigned
9446-9449 Unassigned
14415-14499 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

Contact Information

ID Name Organization Contact URI Last Updated
[Barbara_Foss] Barbara Foss mailto:BGFOSS&rchvmv.vnet.ibm.com
[Didier_Lahay] Didier Lahay mailto:dlahay&sierrawireless.com 2013-02-22
[Eclipse_Foundation] Eclipse Foundation mailto:license&eclipse.org 2013-02-22
[Paul_Greenfield] Paul Greenfield mailto:paul.greenfield&unisys.com
[Qentin_Neill] Qentin Neill mailto:quentin&columbiasc.ncr.com
[Tim_Burgess] Tim Burgess mailto:tim&hotu.com 2002-04
[Uri_Resnitzky] Uri Resnitzky mailto:info&arx.com