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
[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
vpps-via 676 tcp VPPS Via [Ulysses_G_Smith_Jr] [Ulysses_G_Smith_Jr]
vpps-via 676 udp VPPS Via [Ulysses_G_Smith_Jr] [Ulysses_G_Smith_Jr]
netcomm1 1676 tcp netcomm1
netcomm2 1676 udp netcomm2 [Bulent_Kasman] [Bulent_Kasman]
simslink 2676 tcp SIMSLink [Steve_Ryckman] [Steve_Ryckman]
simslink 2676 udp SIMSLink [Steve_Ryckman] [Steve_Ryckman]
va-pacbase 3676 tcp VisualAge Pacbase server [Dominique_Lelievre] [Dominique_Lelievre] 2003-01
va-pacbase 3676 udp VisualAge Pacbase server [Dominique_Lelievre] [Dominique_Lelievre] 2003-01
dhct-alerts 4676 tcp BIAP Generic Alert [Louis_Slothouber] [Louis_Slothouber] 2005-08
dhct-alerts 4676 udp BIAP Generic Alert [Louis_Slothouber] [Louis_Slothouber] 2005-08
mdns 5353 tcp Multicast DNS [IESG] [IETF_Chair] [RFC6762]
mdns 5353 udp Multicast DNS [IESG] [IETF_Chair] [RFC6762]
raadmin 5676 tcp RA Administration [Sergei_Zjaikin] [Sergei_Zjaikin] 2002-02
raadmin 5676 udp RA Administration [Sergei_Zjaikin] [Sergei_Zjaikin] 2002-02
6717-6766 Unassigned
bmc-perf-agent 6767 tcp BMC PERFORM AGENT [Portnoy_Boxman] [Portnoy_Boxman]
bmc-perf-agent 6767 udp BMC PERFORM AGENT [Portnoy_Boxman] [Portnoy_Boxman]
bmc-perf-mgrd 6768 tcp BMC PERFORM MGRD [Portnoy_Boxman] [Portnoy_Boxman]
bmc-perf-mgrd 6768 udp BMC PERFORM MGRD [Portnoy_Boxman] [Portnoy_Boxman]
adi-gxp-srvprt 6769 tcp ADInstruments GxP Server [Mathew_Pitchforth] [Mathew_Pitchforth] 2005-08
adi-gxp-srvprt 6769 udp ADInstruments GxP Server [Mathew_Pitchforth] [Mathew_Pitchforth] 2005-08
imqbrokerd 7676 tcp iMQ Broker Rendezvous [Joseph_Di_Pol] [Joseph_Di_Pol] 2002-04
imqbrokerd 7676 udp iMQ Broker Rendezvous [Joseph_Di_Pol] [Joseph_Di_Pol] 2002-04
8676-8685 Unassigned
canditv 24676 tcp Canditv Message Service [Gary_Aston] [Gary_Aston] 2009-03-10
canditv 24676 udp Canditv Message Service [Gary_Aston] [Gary_Aston] 2009-03-10
caldav tcp Calendaring Extensions to WebDAV (CalDAV) - non-TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6764] This is an extension of the http service. Defined TXT keys: path=<context path>
caldavs tcp Calendaring Extensions to WebDAV (CalDAV) - over TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6764] This is an extension of the https service. Defined TXT keys: path=<context path>
timezone tcp Time Zone Data Distribution Service - non-TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the http service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
timezones tcp Time Zone Data Distribution Service - over TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the https service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).

Contact Information

ID Name Organization Contact URI Last Updated
[Bulent_Kasman] Bulent Kasman mailto:BKasman&symantec.com
[Dominique_Lelievre] Dominique Lelievre mailto:dominique.lelievre&fr.ibm.com 2003-01
[Gary_Aston] Gary Aston mailto:Gary.Aston&datadrivenlogistics.com 2009-03-10
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Joseph_Di_Pol] Joseph Di Pol mailto:joe.dipol&sun.com 2002-04
[Louis_Slothouber] Louis Slothouber mailto:lpslot&biap.com 2005-08
[Mathew_Pitchforth] Mathew Pitchforth mailto:mathew&adinstruments.co.nz 2005-08
[Portnoy_Boxman] Portnoy Boxman mailto:portnoy_boxman&bmc.com 2005-01
[Sergei_Zjaikin] Sergei Zjaikin mailto:serge&previo.ee 2002-02
[Steve_Ryckman] Steve Ryckman mailto:iana&simsware.com
[Ulysses_G_Smith_Jr] Ulysses G. Smith Jr. mailto:ugsmith&cesi.com