Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| agentx | 705 | tcp | AgentX | [Bob_Natale] | [Bob_Natale] | ||||||
| agentx | 705 | udp | AgentX | [Bob_Natale] | [Bob_Natale] | ||||||
| slingshot | 1705 | tcp | slingshot | [Paul_Groarke] | [Paul_Groarke] | ||||||
| slingshot | 1705 | udp | slingshot | [Paul_Groarke] | [Paul_Groarke] | ||||||
| sds-admin | 2705 | tcp | SDS Admin | [Don_Traub] | [Don_Traub] | ||||||
| sds-admin | 2705 | udp | SDS Admin | [Don_Traub] | [Don_Traub] | ||||||
| adobeserver-5 | 3705 | tcp | Adobe Server 5 | [Bernd_Paradies] | [Bernd_Paradies] | 2008-01-14 | |||||
| adobeserver-5 | 3705 | udp | Adobe Server 5 | [Bernd_Paradies] | [Bernd_Paradies] | 2008-01-14 | |||||
| 4705-4710 | Unassigned | ||||||||||
| storageos | 5705 | tcp | StorageOS REST API | [StorageOS] | [Simon_Croome] | 2017-03-03 | |||||
| 5705 | udp | Reserved | |||||||||
| 6705 | udp | Reserved | |||||||||
| 6705 | tcp | Reserved | |||||||||
| frc-mp | 6705 | sctp | ForCES MP (Medium Priority) channel | [RFC5811] |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Bernd_Paradies] | Bernd Paradies | mailto:bparadie&adobe.com | 2008-01-14 | |
| [Bob_Natale] | Bob Natale | mailto:bob.natale&appliedsnmp.com | ||
| [Don_Traub] | Don Traub | mailto:don.traub&sun.com | ||
| [Paul_Groarke] | Paul Groarke | mailto:paulg&quay.ie | ||
| [Simon_Croome] | Simon Croome | mailto:simon.croome&storageos.com | 2017-03-03 | |
| [StorageOS] | StorageOS | mailto:simon.croome&storageos.com | 2017-03-03 |