Free VPS Security Scanner: Ports, SSL & Header Checker
See what is exposed. Know what to fix next.
Free · No signupExternal checks · No server login
Only scan hosts you own or are authorized to test. Private and reserved addresses are blocked.
Find what your server exposes.
Start with a domain or IP. Get an external assessment with practical fixes, without installing an agent.
The host is sent to the scan service. Email DNS checks use public resolvers from your browser. Reports stay in this page unless you copy or download them.
Fixed scan scope · 23 TCP ports
3306, 5432, 27017, 6379, 9200, 11211, 5984, 9042 · 2375, 2376, 2379, 6443 · 23, 3389, 5900, 21 · 22 · 10000, 2082, 2083, 15672, 5601, 9000 + HTTPS 443 and HTTP 80
From the outside to the inside
Find the issue here. Fix it in CtrlOps.
Connect to your Linux server, review its configuration and run security audits from one desktop workspace.
What gets checked
A focused scan.
A useful baseline.
The scanner checks a fixed set of common service ports. A port number suggests a conventional service; it does not identify software or test whether authentication is enforced.
| Category | Ports / checks | Why it matters |
|---|---|---|
| Database exposure | 3306, 5432, 27017, 6379, 9200, 11211, 5984, 9042 | Bind databases to loopback or a private interface. Restrict inbound access to trusted application hosts with a firewall; retain authentication and TLS. |
| Container & orchestration APIs | 2375, 2376, 2379, 6443 | Restrict API access to trusted management networks. Require authentication and TLS; do not expose an unauthenticated Docker socket. |
| Remote access | 23, 3389, 5900, 21 | Disable unused services. Prefer SSH/SFTP, or restrict remote desktop access through a VPN and firewall. |
| SSH access | 22 | Use SSH keys, disable password authentication where appropriate, and restrict allowed source addresses. A different port can reduce automated noise but does not replace these controls. |
| Admin panels | 10000, 2082, 2083, 15672, 5601, 9000 | Restrict management ports to a VPN or trusted IP addresses and require strong authentication. |
| TLS & certificate | HTTPS 443 | Certificate dates, hostname coverage, chain trust and TLS handshakes. |
| HTTP & headers | HTTP 80 / HTTPS 443 | Homepage headers, cookie attributes, version disclosure and HTTPS redirects. |
| Email & DNS | SPF, DMARC, DKIM, DNSSEC | Domain policies and common DKIM selectors, queried from your browser. |
Read the result in context
An outside view.
Not the whole picture.
Scan your own domain or public IP
The scan service opens TCP connections to a fixed set of ports and reads the homepage response. It does not install software, log in, submit credentials or change server settings. Only scan a host you own or are authorized to test. Firewalls and server logs can record the probes.
Check the origin when a CDN is in front
When a domain points to a CDN or reverse proxy, the observations belong to that edge. The scanner notes recognized CDNs and excludes their port observations from the exposure score. Scan the origin IP to inspect your VPS; use the domain to check hostname-specific certificates and HTTP configuration.
Unreachable is not the same as closed
A connection can time out because a firewall drops traffic, a route is unavailable, or the scanner is blocked. Those probes remain unassessed. The scan covers one resolved address and the homepage, so authenticated routes, other virtual hosts, IPv4/IPv6 differences and application vulnerabilities need separate review.
Use the score to prioritize, then verify
The grade reflects the findings this scan can observe. Missing checks make it a partial assessment. A high score does not prove that SSH, database authentication, operating-system patches or application logic are secure. Use the server security checklist for checks inside the machine, and the SSH security guide for access hardening.
VPS security FAQ
Server security,
explained.
Enter your server domain or public IP and run the scan. It checks a fixed set of exposed service ports, the SSL certificate and TLS version, HTTP security headers and cookie flags, HTTP-to-HTTPS redirects, information disclosure, and email authentication (SPF, DMARC, DKIM). It provides an external grade and suggested actions for findings. Unavailable checks are marked not assessed; this is a surface check, not a guarantee of security.
The scan is a lightweight external check: TCP-connect probes of common ports, TLS handshakes and a homepage HTTP header read. It does not log in or change server configuration. Only public hosts are scanned; private and reserved addresses, including cloud metadata endpoints, are blocked. The scan can appear in your firewall and web-server logs.
A curated set of the highest-risk ports rather than a full sweep: databases (MySQL, PostgreSQL, MongoDB, Redis, Elasticsearch, Memcached, CouchDB, Cassandra), container and orchestration APIs (Docker, etcd, Kubernetes), remote access (SSH, RDP, VNC, Telnet, FTP), and common admin panels (Webmin, cPanel, RabbitMQ, Kibana, Portainer). Web ports are covered by the TLS and header checks.
You can scan any public host, but you should only scan servers you own or are explicitly authorized to test. Port-scanning systems you do not control may violate acceptable-use policies or local law. Private and reserved IP ranges are blocked outright for safety.
If your domain uses Cloudflare, CloudFront, Fastly, or a similar CDN, the address it resolves to belongs to the CDN, not your server. The scanner detects this and notes that the port results reflect the CDN edge. To audit your actual server, scan its origin IP directly.
No. A high grade means the common external misconfigurations this tool checks are in good shape. It is a surface check, not a penetration test - it does not scan every port, test authentication, or review application logic. Treat a good grade as a solid baseline, not a guarantee.
Not necessarily. SSH reachable on the default port 22 is flagged as a low-priority hardening suggestion, not a failure. Moving SSH to a non-default port reduces automated noise, and the bigger wins are disabling password authentication in favour of keys and limiting access with a firewall.
The tool does not save a scan history or store reports in browser storage. Your host is sent to the scan service, and infrastructure providers may keep standard request logs. Short-lived rate-limit counters are held in memory. Email-authentication checks run in your browser over DNS-over-HTTPS, so the queried names also reach public resolvers. Copying or downloading a report creates a separate copy that you control.
Use TLS 1.2 at a minimum and TLS 1.3 where available. The scanner reports the negotiated version and checks whether TLS 1.0 or 1.1 handshakes succeed. Successful legacy handshakes are flagged. An inconclusive legacy probe does not prove those versions are disabled; confirm your web server or load balancer configuration.
Each warning or failure has a severity from critical to low. The score starts at 100 and subtracts a weighted penalty: a critical failure costs 25 points, high 15, medium 8 and low 4; warnings cost less. A is 85 or above, B is 70+, C is 55+, D is 40+, and F is below 40. Unassessed checks are not counted as passes, and incomplete reports are labeled partial assessments.
Keep hardening
Related tools for your next task.