Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-22

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: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

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 basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.

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.

Registration Forms

Available Formats

Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
mecomm 668 tcp MeComm
mecomm 668 udp MeComm
netview-aix-8 1668 tcp netview-aix-8
netview-aix-8 1668 udp netview-aix-8
alarm-clock-c 2668 tcp Alarm Clock Client
alarm-clock-c 2668 udp Alarm Clock Client
dell-rm-port 3668 tcp Dell Remote Management Bradley Bransom Bradley Bransom 2003-01
dell-rm-port 3668 udp Dell Remote Management Bradley Bransom Bradley Bransom 2003-01
mmaeds 4668 tcp MMA EDS Service Robert Shaffer Robert Shaffer 2006-02
mmaeds 4668 udp MMA EDS Service Robert Shaffer Robert Shaffer 2006-02
6680-6686 Unassigned
clever-ctrace 6687 tcp CleverView for cTrace Message Service David Cheng David Cheng 2010-02-01
6687 udp Reserved
clever-tcpip 6688 tcp CleverView for TCP/IP Message Service David Cheng David Cheng 2009-10-13
6688 udp Reserved
tsa 6689 tcp Tofino Security Appliance Scott Howard Scott Howard 2009-10-13
tsa 6689 udp Tofino Security Appliance Scott Howard Scott Howard 2009-10-13
authoritygate 7668 tcp AuthorityGate Secure API communication for Orchestrated task sequencing AuthorityGate Inc Kevin Komlosy 2025-03-28
7668 udp Reserved
spartan 8668 tcp Spartan management Tenebris Technologies Inc. Eric Jacksch 2023-10-26
8668 udp Reserved
tec5-sdctp 9668 tcp tec5 Spectral Device Control Protocol Michael Muth Michael Muth 2009-05-11
tec5-sdctp 9668 udp tec5 Spectral Device Control Protocol Michael Muth Michael Muth 2009-05-11
vdmmesh 18668 tcp Manufacturing Execution Systems Mesh Communication Van Doren MES Edwin van de Burgt 2016-10-31
vdmmesh-disc 18668 udp Manufacturing Execution Systems Mesh Communication Van Doren MES Edwin van de Burgt 2016-10-31

Contact Information

Name Organization Contact URI Last Updated
AuthorityGate Inc support&authoritygate.com 2025-03-28
Bradley Bransom bradley_bransom&dell.com 2003-01
David Cheng davec&aesclever.com 2010-02-01
Edwin van de Burgt edwin.van.de.burgt&vandoren.nl 2016-10-31
Eric Jacksch eric&tenebris.com 2023-10-26
Kevin Komlosy AuthorityGate Inc support&authoritygate.com 2025-03-28
Michael Muth m.muth&tec5.com 2009-05-11
Robert Shaffer bob.shaffer&micmod.com 2006-02
Scott Howard scott&byressecurity.com 2009-10-13
Tenebris Technologies Inc. info&tenebris.com 2023-10-26
Van Doren MES mes&vandoren.nl 2016-10-31