Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-07
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 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
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [AuthorityGate_Inc] | AuthorityGate Inc | mailto:support&authoritygate.com | 2025-03-28 | |
| [Bradley_Bransom] | Bradley Bransom | mailto:bradley_bransom&dell.com | 2003-01 | |
| [David_Cheng] | David Cheng | mailto:davec&aesclever.com | 2010-02-01 | |
| [Edwin_van_de_Burgt] | Edwin van de Burgt | mailto:edwin.van.de.burgt&vandoren.nl | 2016-10-31 | |
| [Eric_Jacksch] | Eric Jacksch | mailto:eric&tenebris.com | 2023-10-26 | |
| [Kevin_Komlosy] | Kevin Komlosy | AuthorityGate Inc | mailto:support&authoritygate.com | 2025-03-28 |
| [Michael_Muth] | Michael Muth | mailto:m.muth&tec5.com | 2009-05-11 | |
| [Robert_Shaffer] | Robert Shaffer | mailto:bob.shaffer&micmod.com | 2006-02 | |
| [Scott_Howard] | Scott Howard | mailto:scott&byressecurity.com | 2009-10-13 | |
| [Tenebris_Technologies_Inc] | Tenebris Technologies Inc. | mailto:info&tenebris.com | 2023-10-26 | |
| [Van_Doren_MES] | Van Doren MES | mailto:mes&vandoren.nl | 2016-10-31 |