Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-03-18
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
echo 7 tcp Echo [Jon_Postel] [Jon_Postel]
echo 7 udp Echo [Jon_Postel] [Jon_Postel]
at-echo 204 tcp AppleTalk Echo
at-echo 204 udp AppleTalk Echo
lsp-ping 3503 tcp MPLS LSP-echo Port [RFC8029]
lsp-ping 3503 udp MPLS LSP-echo Port [RFC8029]
echonet 3610 tcp ECHONET [Takeshi_Saito] [Takeshi_Saito] 2002-09
echonet 3610 udp ECHONET [Takeshi_Saito] [Takeshi_Saito] 2002-09
bfd-echo 3785 tcp BFD Echo Protocol [RFC5881]
bfd-echo 3785 udp BFD Echo Protocol [RFC5881]
sma-spw 9522 udp SMA Speedwire [SMA_Solar_Techology] [SMA_Solar_Techology] 2011-03-08
BioSonics tcp BioSonics Echosounders [BioSonics_Inc.] [Asa_Packer] 2023-12-05 Defined TXT keys: None
BioSonics udp BioSonics Echosounders [BioSonics_Inc.] [Asa_Packer] 2023-12-05 Defined TXT keys: None

Contact Information

ID Name Organization Contact URI Last Updated
[Asa_Packer] Asa Packer mailto:apacker&biosonicsinc.com 2023-12-05
[BioSonics_Inc.] BioSonics, Inc. mailto:engineering&biosonicsinc.com 2023-12-05
[Jon_Postel] Jon Postel mailto:postel&isi.edu
[SMA_Solar_Techology] SMA Solar Techology AG mailto:thomas.weber&sma.de 2011-03-08
[Takeshi_Saito] Takeshi Saito mailto:takeshi.saito&toshiba.co.jp 2002-09