Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-11
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
[RFC 6335]
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 [RFC 6335].

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
[RFC 6335]. According to Section 8.1.2 of [RFC 6335], System Ports are 
assigned by the "IETF Review" or "IESG Approval" procedures described in 
[RFC 8126]. User Ports are assigned by IANA using the "IETF Review" process, 
the "IESG Approval" process, or the "Expert Review" process, as per 
[RFC 6335]. Dynamic Ports are not assigned.

The registration procedures for service names and port numbers are
described in [RFC 6335].

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

TXT
Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
opequus-server 2400 tcp OpEquus Server [Gavin_Hutchinson_2] [Gavin_Hutchinson_2]
opequus-server 2400 udp OpEquus Server [Gavin_Hutchinson_2] [Gavin_Hutchinson_2]
med-ltp 24000 tcp med-ltp [Juergen_Fischbach] [Juergen_Fischbach]
med-ltp 24000 udp med-ltp [Juergen_Fischbach] [Juergen_Fischbach]
med-fsp-rx 24001 tcp med-fsp-rx [Juergen_Fischbach] [Juergen_Fischbach]
med-fsp-rx 24001 udp med-fsp-rx [Juergen_Fischbach] [Juergen_Fischbach]
med-fsp-tx 24002 tcp med-fsp-tx [Juergen_Fischbach] [Juergen_Fischbach]
med-fsp-tx 24002 udp med-fsp-tx [Juergen_Fischbach] [Juergen_Fischbach]
med-supp 24003 tcp med-supp [Juergen_Fischbach] [Juergen_Fischbach]
med-supp 24003 udp med-supp [Juergen_Fischbach] [Juergen_Fischbach]
med-ovw 24004 tcp med-ovw [Juergen_Fischbach] [Juergen_Fischbach]
med-ovw 24004 udp med-ovw [Juergen_Fischbach] [Juergen_Fischbach]
med-ci 24005 tcp med-ci [Juergen_Fischbach] [Juergen_Fischbach]
med-ci 24005 udp med-ci [Juergen_Fischbach] [Juergen_Fischbach]
med-net-svc 24006 tcp med-net-svc [Juergen_Fischbach] [Juergen_Fischbach]
med-net-svc 24006 udp med-net-svc [Juergen_Fischbach] [Juergen_Fischbach]
24007-24241 Unassigned
plex 32400 tcp Plex multimedia [Plex_Inc.] [Sasha_Hilton] 2016-06-02
32400 udp Reserved

Contact Information

ID Name Contact URI Last Updated
[Gavin_Hutchinson_2] Gavin Hutchinson mailto:gavinh&tesl.com
[Juergen_Fischbach] Juergen Fischbach mailto:juergen.fischbach&philips.com
[Plex_Inc.] Plex Inc. mailto:sashahilton00&gmail.com 2016-06-02
[Sasha_Hilton] Sasha Hilton mailto:sashahilton00&gmail.com 2016-06-02