Understanding Website Scanning

Two engines

1. HTTP crawl — records cookies and related signals visible without full page execution.
2. Browser crawl — uses a remote browser session to observe execution, storage, network requests, and consent scenarios.

If the browser provider is not configured, the browser half can fail while the HTTP crawl may still complete (partial completion).

Reuse

A completed scan may be reused when website, depth, scanner version, and domain-rule context match and the prior scan finished within the reuse window (30 minutes unless the deployment changes it). Quick results are never reused as Standard or Deep. Choose Force new scan to ignore the window.

Concurrency and caps

A second start while a scan is queued or running joins that job. Each website also has a daily scan cap (12 unless configured otherwise).