Console and network evidence

Before reviewing browser evidence

Use this page after a report is generated from a completed scan. Console and network counts are browser-observed evidence from the rendered page, so they should be read with the matching screenshot, HTML snapshot, issue evidence and accepted scan scope. Do not treat every console or network count as a security finding. The count is a signal that the reviewer should interpret in context: what page was rendered, what request failed, whether the resource was first-party or third-party and whether the issue is reproducible inside the accepted scope.

Review console and network counts

Follow the path `Reports → Technical appendix → Page row → Console → Network → Related issue evidence`.

1. Open /reports/{report} after the scan is completed and the report is generated. Result: the report page shows the Technical appendix for the same scan run.
2. Scroll to Technical appendix and find the affected page row. Result: Console, Network, Screenshot and HTML values are shown together for that URL.
3. Compare Console count with issue evidence. Result: runtime errors are interpreted as browser-observed symptoms, not automatically as exploitable security findings.
4. Compare Network count with the failed or blocked request context. Result: external resource failures, blocked scripts and status problems stay separate from page-level issue severity.
5. Open the related issue or screenshot and HTML artifact when more context is needed. Result: the console or network count is tied to captured evidence before remediation.
6. If evidence is missing or sensitive, continue to Privacy redaction or Failure and skipped-page meanings. Result: reports explain why evidence is incomplete instead of inventing unseen requests.

What console evidence means

Console evidence records JavaScript runtime symptoms observed by the browser worker.

• Console counts can point to broken scripts, consent logic failures, checkout validation problems or browser-only rendering issues.
• A console count is not enough by itself to prove business impact; read the issue evidence and affected URL before prioritizing.
• Console evidence should not include secrets, tokens, credentials or private form values.
• If a console error changes after a retry, compare it with the same scan run and page URL before updating a report.

What network evidence means

Network evidence records failed or blocked requests observed during rendering.

• Failed first-party requests may explain missing content, broken checkout states or incomplete evidence.
• Third-party blocked resources may be informational when the page still works and the finding does not depend on that provider.
• Private, unsafe, login-only or out-of-scope requests should remain excluded instead of being forced into the scan.
• Network evidence should be interpreted with screenshot and HTML snapshot availability so the report does not overstate what was observed.

Continue to report evidence

When console and network counts are understood, continue to [Understand report evidence](/docs/reports/report-evidence). That page explains how findings, severity, confidence, screenshots and appendix data appear in the customer report.