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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| connendp | 693 | tcp | almanid Connection Endpoint | [Ronny_Bremer] | [Ronny_Bremer] | ||||||
| connendp | 693 | udp | almanid Connection Endpoint | [Ronny_Bremer] | [Ronny_Bremer] | ||||||
| rrirtr | 1693 | tcp | rrirtr | ||||||||
| rrirtr | 1693 | udp | rrirtr | ||||||||
| 2693 | tcp | Unassigned | (Removed 2004-2-6) | ||||||||
| 2693 | udp | Unassigned | (Removed 2004-2-6) | ||||||||
| easl | 3693 | tcp | Emergency Automatic Structure Lockdown System | [Mele_Associates] | [Greg_Hansen][Randy_Yates] | 2014-11-26 | This port was previously removed on 2007-04-05. | ||||
| 3693 | udp | Reserved | 2014-11-26 | This port was previously removed on 2007-04-05. | |||||||
| 4693-4699 | Unassigned | ||||||||||
| rbsystem | 5693 | tcp | Robert Bosch Data Transfer | [Syntegon_Technology_GmbH] | [Klaus_Warth] | 2011-08-01 | 2020-02-04 | ||||
| 5693 | udp | Reserved | |||||||||
| 6925-6934 | Unassigned | ||||||||||
| ethoscan | 6935 | tcp | EthoScan Service | [Marty_Campbell] | [Marty_Campbell] | 2011-06-10 | |||||
| ethoscan | 6935 | udp | EthoScan Service | [Marty_Campbell] | [Marty_Campbell] | 2011-06-10 | |||||
| xsmsvc | 6936 | tcp | XenSource Management Service | [Roger_Klorese] | [Roger_Klorese] | 2006-06 | |||||
| xsmsvc | 6936 | udp | XenSource Management Service | [Roger_Klorese] | [Roger_Klorese] | 2006-06 | |||||
| 6937-6945 | Unassigned | ||||||||||
| 9669-9693 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Greg_Hansen] | Greg Hansen | Mele Associates | mailto:greg.hansen&meleassociates.com | 2014-11-26 |
| [Klaus_Warth] | Klaus Warth | Syntegon Technology GmbH | mailto:Klaus.Warth&Syntegon.com | 2020-02-04 |
| [Marty_Campbell] | Marty Campbell | mailto:martycðosinfo.com | 2011-06-10 | |
| [Mele_Associates] | Mele Associates | mailto:easl&meleassociates.com | 2014-11-26 | |
| [Randy_Yates] | Randy Yates | Digital Signal Labs | mailto:yates&digitalsignallabs.com | 2014-11-26 |
| [Roger_Klorese] | Roger Klorese | mailto:roger&xensource.com | 2006-06 | |
| [Ronny_Bremer] | Ronny Bremer | mailto:rbremer&almanid.com | ||
| [Syntegon_Technology_GmbH] | Syntegon Technology GmbH | mailto:Klaus.Warth&syntegon.com | 2020-02-04 |