Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-04-19
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
tftp 69 tcp Trivial File Transfer [David_Clark] [David_Clark]
tftp 69 udp Trivial File Transfer [David_Clark] [David_Clark]
subntbcst-tftp 247 tcp SUBNTBCST_TFTP

IANA assigned this well-formed service name as a replacement for "subntbcst_tftp".
[John_Fake] [John_Fake]
subntbcst_tftp 247 tcp SUBNTBCST_TFTP [John_Fake] [John_Fake] This entry is an alias to "subntbcst-tftp". This entry is now historic, not usable for use with many common service discovery mechanisms.
subntbcst-tftp 247 udp SUBNTBCST_TFTP

IANA assigned this well-formed service name as a replacement for "subntbcst_tftp".
[John_Fake] [John_Fake]
subntbcst_tftp 247 udp SUBNTBCST_TFTP [John_Fake] [John_Fake] This entry is an alias to "subntbcst-tftp". This entry is now historic, not usable for use with many common service discovery mechanisms.
tftp-mcast 1758 tcp tftp-mcast [Tom_Emberson] [Tom_Emberson]
tftp-mcast 1758 udp tftp-mcast [Tom_Emberson] [Tom_Emberson]
etftp 1818 tcp Enhanced Trivial File Transfer Protocol [William_Polites] [William_Polites]
etftp 1818 udp Enhanced Trivial File Transfer Protocol [William_Polites] [William_Polites]
tftps 3713 tcp TFTP over TLS [Mark_mayernick] [Mark_mayernick] 2003-03
tftps 3713 udp TFTP over TLS [Mark_mayernick] [Mark_mayernick] 2003-03

Contact Information

ID Name Contact URI Last Updated
[David_Clark] David Clark mailto:ddc&lcs.mit.edu
[John_Fake] John Fake mailto:fake&us.ibm.com
[Mark_mayernick] Mark mayernick mailto:Mark.Mayernick&thomson.net 2003-03
[Tom_Emberson] Tom Emberson mailto:tom&lanworks.com
[William_Polites] William Polites mailto:wpolites&mitre.org