MySQL Open Port Scanner

Test if your MySQL database is open to the public
Shadowserver foundation recently published scanning results for MySQL server instances on port 3306/TCP. Over 3.6 million MySQL servers were accessible worldwide. For almost all of these databases, there is no use case for the general public to access or even know these servers exist.

We're pretty certain that none of the 3.6 million had intentionally left their databases accessible, so here is a quick scan you can do, to check if your MySQL databases have their ports open.
Scan for MySQL open ports:

Instructions: Enter a single IP or hostname to scan. The MySQL Open Port Scanner will check the default MySQL port 3306 over TCP. Only IPv4 addresses are supported with this scanner. There are two possible results:
If your MySQL server is exposed, the common mitigations are:
These two mitigation solutions do not meet the Zero Trust Network Architecture philosophy as users are granted excess privileges. Learn about the pros and cons of mitigation options at Dev.to
If your MySQL database ports are closed, your instance is safe from external scans. You can still overlay Remote.It connectivity to:
Remote.It accounts are free, get started here.
Learn how to deploy Remote.It in the following environments

Move away from legacy networks - enjoy the freedom of connectivity as code

By deploying a single line of code within their corporate cloud infrastructure, companies are able to eliminate the need to use discoverable Public IP addresses for access that in turn eliminates the attack surface.

“Cloud resources can be in different regions or even within different cloud providers and Remote.It makes them all available simultaneously. No connecting, unconnecting, and reconnecting as is required with legacy VPN type solutions. And because our solution operates at layer 4, our connections are peer to peer, so unlike CASB (CloudAccess Security Broker)” type solutions – sensitive corporate data businesses’ traffic isn’t routing through us”, said Ryo Koyama, CEO of Remote.It.

Cloud native developers need to be freed from the limitations of legacy networks. In addition to providing cloud access to resources with no public IP address, development environments are becoming too large and too dispersed to easily and predictably replicate on local machines. Deploying Remote.It means that those resources, when they are in production, staging, or development, are directly available as if they were running directly on the developers local machine. This way of working is not only faster, it’s easier and safer to manage.

Create an account and get started with Remote.It for free

Enjoy free personal plans or upgrade to paid commercial plans starting at just $10/month (annually)
Create free account