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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| periscope | 1230 | tcp | Periscope | [Kevin_Madden] | [Kevin_Madden] | ||||||
| periscope | 1230 | udp | Periscope | [Kevin_Madden] | [Kevin_Madden] | ||||||
| linogridengine | 12300 | tcp | LinoGrid Engine | [Frans_Lundberg] | [Frans_Lundberg] | 2004-11 | |||||
| linogridengine | 12300 | udp | LinoGrid Engine | [Frans_Lundberg] | [Frans_Lundberg] | 2004-11 | |||||
| 12301 | Unassigned | ||||||||||
| rads | 12302 | tcp | Remote Administration Daemon (RAD) is a system service that offers secure, remote, programmatic access to Solaris system configuration and run-time state | [Oracle] | [Devjani_Ray] | 2012-04-20 | |||||
| 12302 | udp | Reserved | |||||||||
| 12303-12320 | Unassigned | ||||||||||
| z-wave-s | 41230 | tcp | Z-Wave Protocol over SSL/TLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 | |||||
| z-wave-s | 41230 | udp | Z-Wave Protocol over DTLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Anders_Brandt_4] | Anders Brandt | Sigma Designs | mailto:anders_brandt&sigmadesigns.com | 2015-06-26 |
| [Devjani_Ray] | Devjani Ray | Oracle Corporation | mailto:Devjani.Ray&oracle.com | 2012-04-20 |
| [Frans_Lundberg] | Frans Lundberg | mailto:frans&linova.com | 2004-11 | |
| [Kevin_Madden] | Kevin Madden | mailto:Kevin&emailxtras.com | ||
| [Oracle] | Oracle Corporation | mailto:Devjani.Ray&oracle.com | 2012-04-20 | |
| [Sigma_Designs_3] | Sigma Designs | mailto:anders_brandt&sigmadesigns.com | 2015-06-26 |