Start with the access report
A restricted scan shows the address requested, the time, the response code and, when the server supplies one, a request ID. These details help your host find the exact request in its firewall or CDN logs.
- 403: access refused. Ask your host which rule rejected the request. The code alone does not tell us whether it was a firewall rule, location restriction or the origin server.
- 401: sign-in required. Use a public page. Scavo does not log into your site, and you should not put passwords or access tokens into a scan URL.
- 429: request limit reached. Follow the server's retry window before scanning again. Scavo does not repeatedly retry the blocked scan.
- Browser verification. A challenge page is not your website content, even when it returns HTTP 200. Scavo does not solve CAPTCHAs or pretend that the page passed.
Make a narrow exception
- Ask the person who manages your hosting or CDN to match the report's URL, UTC time and request ID to their logs.
- If you want Scavo to scan your public pages, allow its verified outbound IP through the specific rule that blocked it. Keep the exception limited to the relevant hostname and public read requests.
- Keep protection on private pages, logins and forms. Do not disable the whole firewall or trust a User-Agent string on its own: anyone can send that text.
- Run a fresh scan after the change. If it is still restricted, send the new access report to [email protected].
Scanner identity
Current User-Agent:
ScavoBot/1.0 (+https://scavo.ai/legal/privacy#automated-scanning-identity; mailto:[email protected])Verified outbound addresses for this Scavo installation:
167.99.88.81
The IP addresses in an older report describe that run. Check this page before adding a new exception.
What a partial report can tell you
Scavo can still report the access response and any independent certificate or domain-expiry checks that finished. Those results are separate from the page checks that could not run. There is no overall health score, and the report does not replace your last completed baseline.
A blocked Scavo request does not prove your site is down or that ChatGPT, Google or other AI services cannot reach it. A robots.txt permission also does not override a firewall. Keep any intentional AI training restrictions in place.