Check a cloud server's external exposure in one command
Run curl -4 https://qsa.sh on the server to scan its public IPv4 from outside, then compare the open ports, versions and nuclei findings with your security group or firewall rules.
Engine updates, coverage changes and product news. What changed, and what it means for your scans.
Run curl -4 https://qsa.sh on the server to scan its public IPv4 from outside, then compare the open ports, versions and nuclei findings with your security group or firewall rules.
Docker publishes ports through its own iptables rules, so traffic to them never reaches the chain UFW filters. How to see it on the host, confirm it from outside, and fix it, safest option first.
curl <url> | bash is arbitrary local code execution with no checkpoint. curl qsa.sh is not that pattern: it streams a report, runs nothing on your machine, and scans only your own public IP from the outside.
A small bash script that runs a qsa.sh scan on a schedule, remembers the last result, and notifies you only when your externally visible exposure actually changes. Works with free and paid tokens.
nmap 7.99 and nuclei 3.11.1 are now live for every scan, scan time budgets have been rebuilt so long scans finish instead of being cut off, and every scan now opens with origin intelligence from worldip.io.
qsa.sh runs a real external security and port scan of your own server, from outside your network, in about thirty seconds with nothing to install — and it only ever scans the IP you connect from.