Scanning
Normal vs deep scan
The eleven steps a hacker takes, what each scan does at each step, and who can run it.
Every scan takes the steps a hacker takes against a website, with the same kind of tools, and stops before doing any harm. The report is laid out the same way: for each step, what a hacker tries, what we did, what we found and what to do.
There are two kinds of scan. A normal scan uses only what anyone on the internet can see: public records and a normal visit to your site. Anyone can run it on any public site. A deep scan also knocks on your server directly, so it only runs on domains you have proved you own. Both are free.
At a glance
| Normal scan | Deep scan |
| Who can run it | Anyone, on any public site | Only on verified domains |
| What it looks at | What a normal visit sees: the page, its headers, TLS, cookies, scripts and public DNS records | Everything in a normal scan, plus requests for known sensitive paths and tests for known vulnerabilities |
| Requests to your site | Up to 100 | Up to 600, one connection to each of 22 server ports, plus nuclei templates at up to 15 requests a second |
| Typical time | About 1 minute | 3 to 5 minutes |
| Price | Free, no sign-up | Free with an account; weekly and automatic with Protect |
The hacker's steps, and what each scan does
1. Find every part of your websiteNormal scan. Hackers use subfinder, amass and crt.sh. We read the public certificate logs (crt.sh and Cert Spotter) for every name under your domain, look each one up in DNS, flag names that point to a deleted service someone else could claim (subdomain takeover, the same fingerprints as can-i-take-over-xyz), and list test, staging and admin sites that are still online.
2. Find open doors on your serverDeep scan. Hackers use nmap and masscan. We connect once to each of 22 ports, such as MySQL, PostgreSQL, Redis, MongoDB, Elasticsearch, Docker, Remote Desktop and FTP, and report the ones that answer. We send nothing else.
3. Find old software with known holesNormal scan. Hackers use Wappalyzer, WPScan and public bug lists. We read the software and versions your site shows and look them up live in OSV.dev, CISA's list of bugs used in attacks now and endoflife.date. On WordPress sites we read each plugin's version from its readme.txt and compare it with wordpress.org, including plugins wordpress.org removed.
4. Look for passwords and keys in your public codeNormal scan. Hackers use trufflehog and gitleaks. We search the page and up to 12 of its scripts for 27 kinds of keys (Stripe, AWS, OpenAI, Anthropic, GitHub, GitLab, npm, Shopify, Twilio, SendGrid, Supabase admin keys and more), Supabase and Firebase settings, and public source maps. Keys are shown shortened.
5. Look for files that should never be publicNormal scan reads robots.txt. Deep scan, like ffuf and gobuster, asks for 116 paths: .env files, .git and .svn folders, backups and database dumps, private keys and cloud credentials, config files, error logs, debug tools (Spring Actuator, Symfony profiler, Laravel Telescope and others), phpinfo pages, folder listings and API descriptions.
6. Try known attacksDeep scan. We run nuclei, the tool hackers use, with its community templates for known bugs, exposures, setup mistakes and takeovers (medium risk and above), and test for open redirects and GraphQL introspection.
7. Listen in on your visitorsNormal scan. Hackers use sslscan, testssl.sh and Wi-Fi sniffers. We check HTTPS and the redirect to it, the certificate, the TLS version, old TLS 1.0 and 1.1, HSTS and insecure content on the page.
8. Trick your visitors' browsersNormal scan. Hackers use Burp Suite and OWASP ZAP. We check the safety headers browsers obey, cookie flags and whether another website can read your pages (CORS).
9. Pretend to be youNormal scan. We read SPF, DMARC, CAA and MX records, so others cannot easily send email as your domain or get certificates for it.
10. Guess passwords on your login pagesHackers use Hydra and WPScan. The normal scan checks whether WordPress shows its usernames to anyone (shown shortened unless the domain is verified) and whether xmlrpc.php is open. The deep scan also looks for public admin and database tools. We never try a password.
11. Report a hole to youNormal scan. A security.txt file that tells friendly researchers how to reach you.
Before probing paths, a deep scan learns how your site answers a page that does not exist, so sites that return 200 for everything do not produce false alarms.
Why deep scans need verification
Asking a site for its .env file, or knocking on its database port, is exactly what an attacker does first. Doing that to someone else's site without permission can be illegal and gets scan servers blocked. Verification proves the site is yours and takes about a minute. See Verify your domain.
Which one to use
- Normal scan for a quick health check, for sites you cannot add DNS records or files to, and for every rescan after small header or DNS fixes.
- Deep scan before a launch, after a big deploy or hosting change, and at least once for every site you run. It is the only scan that finds open server ports, leaked files and known vulnerabilities.
Neither scan covers everything
Both look from the outside as an anonymous visitor. We do not sign in, guess passwords or test how your app works inside (payments, permissions, what one customer can see of another). The report lists what was not tried.