Separating a blocked scanner from a broken public page
A blocked auditing tool and a broken public page are different findings. Record the response actually delivered to the scanner and compare it with a controlled public request.
Identify what was blocked
Look for the exact status, challenge page, denial message or tool error. Distinguish a website response from a browser-control permission error produced before navigation. Record the requested hostname and path. A screenshot of a normal browser page does not tell you what the scanner received, and a scanner denial does not establish that all visitors are blocked.
Avoid changing unrelated controls
If a site security rule is implicated, have its operator inspect the matching event before changing it. If the restriction belongs to the auditing application, changing website content will not address it. Preserve legitimate protection while resolving a verified access issue for the intended audience. Repeat the specific failed request and retain the result.
Source guidance
Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.Frequently Asked Questions
Should security be disabled just to improve a score?
No. First establish the cause and intended access. A narrowly verified correction is more meaningful than removing protection to make a tool report look cleaner.