Help
Allow our scanner through
If a scan came back saying your site served us a block page, your firewall or bot protection stopped us before we ever saw a page. Allow this address and run the scan again:
82.192.72.222
Cloudflare
Security → WAF → Tools → IP Access Rules. Enter the IP, set the action to Allow, scope it to this website, add it.
Wordfence (WordPress)
Firewall → All Firewall Options → Allowlisted IP Addresses. Paste the IP, save.
Your host’s firewall
SiteGround, Kinsta, WP Engine, Hostinger and most managed hosts run their own WAF you can’t see. Open a ticket: “please allowlist 82.192.72.222 for my site.”
A password or a coming-soon page
Basic-auth prompts, “maintenance mode” plugins and staging locks all look the same to us as a block. Lift it while the scan runs, or scan a URL that’s publicly reachable.
Why we don’t have a bot name
We fetch your site the way an ordinary browser does, not as a named crawler. A named bot gets rate-limited or served a different page by half the WAFs on the web, and then the audit measures the block instead of your site. The IP is the one thing that identifies us, which is why it’s what you allow.
Only your own site
You can only do this for a site you control. If a scan of someone else’s site comes back blocked, that’s their decision and there’s nothing to change — scan a URL that isn’t protected.