Online Port Scanner

An open port is a door. Every service listening on a public IP is something an attacker can reach, fingerprint, and probe for weak credentials or known CVEs. The classic breach isn't an exotic zero-day — it's a Redis instance bound to 0.0.0.0 with no password, a Postgres database left open to the internet during a migration, or a MongoDB that shipped with default auth disabled. Our online port scanner checks your domain for exactly these exposures in seconds.

We run a fast TCP-connect probe across the ~25 ports that matter most for security: remote-admin interfaces (SSH, Telnet, RDP, VNC), databases (MySQL, PostgreSQL, MSSQL, MongoDB), caches and search engines (Redis, Memcached, Elasticsearch, Kibana), infrastructure control planes (Docker API, RabbitMQ management), and mail/web ports. We grade each open port by risk: an exposed database or a plaintext Telnet port is critical; standard web ports (80/443) are expected and never flagged as noise.

Why services end up exposed: a Docker container published a port with `-p 6379:6379` instead of `-p 127.0.0.1:6379:6379`, a cloud security group has an inbound rule of `0.0.0.0/0` that was meant to be temporary, or a managed database was created with 'public access' enabled for convenience and never locked down. The fix is almost always the same — bind internal services to localhost or a private subnet, and put a firewall or security group in front of anything that genuinely needs to stay open.

This free check is a fast triage of the most common exposures. A full SteelSuit scan goes deeper — a complete top-1000 nmap port scan with service-version and script detection, plus correlation against the rest of your attack surface (TLS config on each open port, known CVEs for the detected service versions, and subdomain enumeration so you catch the staging box that's wide open while production is locked down).