Online Port Scanner

What this tool checks

Every website should serve traffic on ports 80 and 443 — anything else exposed to the public internet is usually a mistake. We probe 14 well-known web ports (dev servers, admin panels, control panels, monitoring dashboards) and flag any that respond so you can lock them down behind a firewall, VPN or authentication.

This is an HTTP-level probe: we detect services that speak HTTP or HTTPS on each port. Non-web protocols (SSH, FTP, databases) require a native TCP scanner — for those, run nmap from a machine you own.

Ports we scan

• 80 — HTTP
• 443 — HTTPS
• 8080 — HTTP-Alt
• 8443 — HTTPS-Alt
• 8000 — HTTP-Dev
• 8888 — HTTP-Alt
• 3000 — Node/Dev
• 5000 — Flask/Dev
• 7001 — WebLogic
• 9000 — SonarQube
• 9090 — Prometheus
• 2082/2083 — cPanel
• 10000 — Webmin

How does an online port scanner work?

We send an HTTP or HTTPS request to each port on the target host with a short timeout. If we get any response, the port is open and speaking HTTP; no response within 4 seconds means the port is closed or filtered by a firewall.

Which ports do you scan?

Can you scan non-web ports like SSH or FTP?

Is it legal to scan someone else's website?

Why is port 8080 dangerous?

Do you store the scan results?

Related guides

More tools