Scan a site’s cookies
A real browser visits the site, trying five journeys, and notes the cookies and services called at each step.
Part of the EU compliance pack.
On this page
Run a scan#
- On the site’s Compliance page, open Cookie scan.
- Click Scan now.
The scan takes one to five minutes, sometimes more if there’s a queue: scans run one at a time. It’s possible before turning on the banner, to take stock. It runs again by itself every month when the banner is active, and you receive an email if a new cookie appears without consent.
You can run 3 manual scans per site per day.
What the browser does#
It tries five journeys: no choice, all refused, preferences, statistics, all accepted. That’s how it knows what gets set before consent.
Read the result#
| Part | What to do |
|---|---|
| Set or loaded without consent | The problem to handle. Add their address to Blocking rules, or describe them as functional if they’re truly essential. If the rule already exists, the item is loaded by a script the banner does not recognise: contact support and mention the page, shown next to each cookie. |
| Cookies to describe | The scan doesn’t recognise them. Without a description, the policy shows a “purpose to check” mention. Your answer is kept for future scans. |
| Inventory | All cookies, with their Service, Category, Purpose and Duration. |
| External services called | Even without a cookie, each call sends the visitor’s IP address. A Google font loaded before consent deserves to be hosted on the site. |
Results are kept for 400 days and included in client reports, with no personal data.
Still have a question? Write to us.