Port 3306 — MySQL

TCPDatabase

MySQL classic protocol defaults to TCP 3306. A local Unix-socket connection may bypass TCP entirely, so a port check alone cannot establish whether MySQL is running.

Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.

Configuration and troubleshooting

Check port, bind_address and the client transport. Update connection strings and container mappings after a change; access-denied errors need account checks, not more open ports.

Important limitations

Do not confuse 3306 with MySQL X Protocol on 33060. Limit permitted source addresses and configure authentication and TLS for the deployment.

Read-only checks: run on the server host

Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.

Linux

sudo ss -ltnp 'sport = :3306'

macOS

sudo lsof -nP -iTCP:3306 -sTCP:LISTEN

Windows PowerShell

Get-NetTCPConnection -LocalPort 3306 -State Listen

Sources and review

Sources checked on:

This review covers the explanations and sources on this page, not your device or every community software entry below.

Software Using This Port (2 software)

Community software entries: links are references, not individual verification.

MySQL

Default port for MySQL database server

Reference link ↗

MariaDB

A relational database compatible with the MySQL protocol; check the instance listener configuration.

Reference link ↗

Usage Suggestions

  • Before using port 3306, please confirm it is not occupied by other services
  • If you encounter port conflicts, consider using other ports or stopping the occupying service

Quick Info

Port
3306
Protocol
TCP
Categories
Database
Usage Status
2 software in use

Related Ports

Port 5432TCP
→
Port 27017TCP
→

Need Help?

If you find incorrect information or need to add more, please submit correction information.

Submit Correction