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
disclose 667 tcp campaign contribution disclosures - SDR Technologies [Jim_Dixon] [Jim_Dixon]
disclose 667 udp campaign contribution disclosures - SDR Technologies [Jim_Dixon] [Jim_Dixon]
netview-aix-7 1667 tcp netview-aix-7
netview-aix-7 1667 udp netview-aix-7
alarm-clock-s 2667 tcp Alarm Clock Server
alarm-clock-s 2667 udp Alarm Clock Server
infoexch 3667 tcp IBM Information Exchange [Paul_Ford_Hutchinson] [Paul_Ford_Hutchinson] 2003-01
infoexch 3667 udp IBM Information Exchange [Paul_Ford_Hutchinson] [Paul_Ford_Hutchinson] 2003-01
mmacomm 4667 tcp MMA Comm Services
mmacomm 4667 udp MMA Comm Services
5667-5669 Unassigned
vocaltec-gold 6670 tcp Vocaltec Global Online Directory [Scott_Petrack] [Scott_Petrack]
vocaltec-gold 6670 udp Vocaltec Global Online Directory [Scott_Petrack] [Scott_Petrack]
p4p-portal 6671 tcp P4P Portal Service [Chris_Griffiths] [Chris_Griffiths] 2008-07-28
p4p-portal 6671 udp P4P Portal Service [Chris_Griffiths] [Chris_Griffiths] 2008-07-28
vision-server 6672 tcp vision_server

IANA assigned this well-formed service name as a replacement for "vision_server".
[Chris_Kramer] [Chris_Kramer]
vision_server 6672 tcp vision_server [Chris_Kramer] [Chris_Kramer] This entry is an alias to "vision-server". This entry is now historic, not usable for use with many common service discovery mechanisms.
vision-server 6672 udp vision_server

IANA assigned this well-formed service name as a replacement for "vision_server".
[Chris_Kramer] [Chris_Kramer]
vision_server 6672 udp vision_server [Chris_Kramer] [Chris_Kramer] This entry is an alias to "vision-server". This entry is now historic, not usable for use with many common service discovery mechanisms.
vision-elmd 6673 tcp vision_elmd

IANA assigned this well-formed service name as a replacement for "vision_elmd".
[Chris_Kramer] [Chris_Kramer]
vision_elmd 6673 tcp vision_elmd [Chris_Kramer] [Chris_Kramer] This entry is an alias to "vision-elmd". This entry is now historic, not usable for use with many common service discovery mechanisms.
vision-elmd 6673 udp vision_elmd

IANA assigned this well-formed service name as a replacement for "vision_elmd".
[Chris_Kramer] [Chris_Kramer]
vision_elmd 6673 udp vision_elmd [Chris_Kramer] [Chris_Kramer] This entry is an alias to "vision-elmd". This entry is now historic, not usable for use with many common service discovery mechanisms.
6674-6677 Unassigned
vfbp 6678 tcp Viscount Freedom Bridge Protocol [Chris_MacDonald] [Chris_MacDonald] 2011-03-16
vfbp-disc 6678 udp Viscount Freedom Bridge Discovery [Chris_MacDonald] [Chris_MacDonald] 2011-03-16
osaut 6679 tcp Osorno Automation [Peter_Hombach] [Peter_Hombach] 2011-03-16
osaut 6679 udp Osorno Automation [Peter_Hombach] [Peter_Hombach] 2011-03-16
7664-7667 Unassigned
8667 Unassigned
xmms2 9667 tcp Cross-platform Music Multiplexing System [Juho_Herttua] [Juho_Herttua] 2009-04-14
xmms2 9667 udp Cross-platform Music Multiplexing System [Juho_Herttua] [Juho_Herttua]
16667-16788 Unassigned
18636-18667 Unassigned
24667-24675 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Chris_Griffiths] Chris Griffiths mailto:chris_griffiths&cable.comcast.com 2008-07-28
[Chris_Kramer] Chris Kramer mailto:CKramer&gis.shl.com
[Chris_MacDonald] Chris MacDonald mailto:chris&viscount.com 2011-03-16
[Jim_Dixon] Jim Dixon mailto:jim&lambda.com
[Juho_Herttua] Juho Vähä-Herttua mailto:juhovh&iki.fi 2009-04-14
[Paul_Ford_Hutchinson] Paul Ford-Hutchinson mailto:paulfordh&uk.ibm.com 2003-01
[Peter_Hombach] Peter Hombach mailto:p.hombach&osorno.ca 2011-03-16
[Scott_Petrack] Scott Petrack mailto:Scott_Petrack&vocaltec.com