Some hosts put a challenge in front of automated traffic. When that happens, a scanner sees the challenge page, not your app.
Why this matters
A low finding count on a blocked scan is not evidence of safety. It is evidence that the scanner could not reach the app. The honest output is "inconclusive", not "grade A".
What to do
- If you own the app, add the supported access header for your host.
- Or point the check at a staging URL without the challenge.
- Do not disable bot protection just to satisfy a scanner.
CobaltProof detects a blocked response, stops the request-heavy part of the check, and marks the report inconclusive. It never turns a blocker into a clean result.