Scan Results & Cookie Inventory
Review findings without treating an empty scan as a clean-site guarantee.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
What the scan provides
The cookie scanner uses a browser to observe the requested site and identify cookies/scripts present in the scan context. Known cookies can be classified automatically; unknown or purpose-dependent entries require review.
Check completion and scope
Inspect the tested URL, completion state, timestamp, page/challenge evidence and cookie inventory. A successful scan is an operational result, not a legal verdict. A running/failed scan cannot establish absence of tracking.
What can be missed
Login-only behaviour, delayed tags, interactions, region-dependent content, checkout, frames and post-consent providers can differ. Inventory records can also outlive the current scan and should be reviewed rather than silently treated as newly observed.
Manual verification
Use a clean browser context and inspect storage/network on representative routes before interaction and in separate reject/accept/custom contexts. Record actual names, domains, duration, purposes and when each was observed. Classify purpose, not just provider name.
Empty findings
Zero cookies can be genuine or reflect a challenge, incomplete page, different context or timing. Diagnose the evidence first. It does not by itself prove firewall blocking or legal compliance.
Do not broadly bypass security controls to improve a scan result.