Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-05-02
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
mysql-cluster | 1186 | tcp | MySQL Cluster Manager | [Arjen_Lentz] | [Arjen_Lentz] | 2004-11 | |||||
mysql-cluster | 1186 | udp | MySQL Cluster Manager | [Arjen_Lentz] | [Arjen_Lentz] | 2004-11 | |||||
mysql-cm-agent | 1862 | tcp | MySQL Cluster Manager Agent | [Andrew_Morgan] | [Andrew_Morgan] | 2009-12-08 | |||||
mysql-cm-agent | 1862 | udp | MySQL Cluster Manager Agent | [Andrew_Morgan] | [Andrew_Morgan] | 2009-12-08 | |||||
mysql-im | 2273 | tcp | MySQL Instance Manager | [Petr_Chardin] | [Petr_Chardin] | 2004-12 | |||||
mysql-im | 2273 | udp | MySQL Instance Manager | [Petr_Chardin] | [Petr_Chardin] | 2004-12 | |||||
mysql | 3306 | tcp | MySQL | [Monty] | [Monty] | ||||||
mysql | 3306 | udp | MySQL | [Monty] | [Monty] | ||||||
mysql-proxy | 6446 | tcp | MySQL Proxy | [Kay_Roepke] | [Kay_Roepke] | 2009-04-22 | |||||
mysql-proxy | 6446 | udp | MySQL Proxy | [Kay_Roepke] | [Kay_Roepke] | 2009-04-22 | |||||
sphinxql | 9306 | tcp | Sphinx search server (MySQL listener) | [Andrew_Aksyonoff] | [Andrew_Aksyonoff] | 2009-10-20 | |||||
mysqlx | 33060 | tcp | MySQL Database Extended Interface | [Oracle_8] | [Omer_BarNir] | 2015-08-06 |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Andrew_Aksyonoff] | Andrew Aksyonoff | mailto:shodan&sphinxsearch.com | 2009-10-20 | |
[Andrew_Morgan] | Andrew Morgan | mailto:andrew.morgan&sun.com | 2009-12-08 | |
[Arjen_Lentz] | Arjen Lentz | mailto:arjen&mysql.com | 2004-11 | |
[Kay_Roepke] | Kay Roepke | mailto:Kay.Roepke&sun.com | 2009-04-22 | |
[Monty] | Monty | mailto:monty&analytikerna.se | ||
[Omer_BarNir] | Omer BarNir | mailto:omer.barnir&oracle.com | ||
[Oracle_8] | Oracle Corp | mailto:omer.barnir&oracle.com | 2015-08-06 | |
[Petr_Chardin] | Petr Chardin | mailto:petr&mysql.com | 2004-12 |