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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| meregister | 669 | tcp | MeRegister | [Armin_Sawusch] | [Armin_Sawusch] | ||||||
| meregister | 669 | udp | MeRegister | [Armin_Sawusch] | [Armin_Sawusch] | ||||||
| netview-aix-9 | 1669 | tcp | netview-aix-9 | ||||||||
| netview-aix-9 | 1669 | udp | netview-aix-9 | ||||||||
| toad | 2669 | tcp | TOAD | [Michael_Marking] | [Michael_Marking] | ||||||
| toad | 2669 | udp | TOAD | [Michael_Marking] | [Michael_Marking] | ||||||
| casanswmgmt | 3669 | tcp | CA SAN Switch Management | [Emre_Tunar] | [Emre_Tunar] | 2003-01 | |||||
| casanswmgmt | 3669 | udp | CA SAN Switch Management | [Emre_Tunar] | [Emre_Tunar] | 2003-01 | |||||
| eportcommdata | 4669 | tcp | E-Port Data Service | [Robert_Shaffer] | [Robert_Shaffer] | 2006-02 | |||||
| eportcommdata | 4669 | udp | E-Port Data Service | [Robert_Shaffer] | [Robert_Shaffer] | 2006-02 | |||||
| 5667-5669 | Unassigned | ||||||||||
| ircu | 6665-6669 | tcp | IRCU | [Brian_Tackett] | [Brian_Tackett] | ||||||
| 6665-6669 | udp | Reserved | |||||||||
| cleverdetect | 6690 | tcp | CLEVERDetect Message Service | [Applied_Expert_Systems_Inc] | [David_Cheng] | 2014-12-03 | |||||
| 6690 | udp | Reserved | |||||||||
| 6691-6695 | Unassigned | ||||||||||
| 6696 | tcp | Reserved | |||||||||
| babel | 6696 | udp | Babel Routing Protocol | 2011-08-15 | [RFC8966] | ||||||
| ircs-u | 6697 | tcp | Internet Relay Chat via TLS/SSL | 2014-02-11 | [RFC7194] | ||||||
| 6697 | udp | Reserved | 2014-02-11 | ||||||||
| 6698 | Unassigned | ||||||||||
| 6699 | tcp | Reserved | |||||||||
| babel-dtls | 6699 | udp | Babel Routing Protocol over DTLS | [IESG] | [IETF_Chair] | 2020-09-04 | [RFC8968] | ||||
| 7669-7671 | Unassigned | ||||||||||
| 8669-8674 | Unassigned | ||||||||||
| 9669-9693 | Unassigned | ||||||||||
| 18669-18768 | Unassigned | ||||||||||
| 20481-20669 | Unassigned | ||||||||||
| 36603-36699 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Applied_Expert_Systems_Inc] | Applied Expert Systems, Inc. | mailto:davec&aesclever.com | 2014-12-03 | |
| [Armin_Sawusch] | Armin Sawusch | mailto:armin&esd1.esd.de | ||
| [Brian_Tackett] | Brian Tackett | mailto:cym&acrux.net | ||
| [David_Cheng] | David Cheng | mailto:davec&aesclever.com | 2010-02-01 | |
| [Emre_Tunar] | Emre Tunar | mailto:emre.tunar&ca.com | 2004-11 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Michael_Marking] | Michael Marking | mailto:marking&tatanka.com | ||
| [Robert_Shaffer] | Robert Shaffer | mailto:bob.shaffer&micmod.com | 2006-02 |