Cookie and tracker scan

See the cookies, trackers and consent banner a first-time visitor meets, before any choice is made.

This tool needs a free account. Sign in or create one, then run it with your credits.

A page URL or a domain; a domain means its home page.

Costs 5 credits with a free account.

What the cookie scanner tells you

Under the ePrivacy rules and the GDPR, most sites in the EU and UK need consent before setting non-essential cookies or loading tracking services. In practice, many sites load analytics and advertising scripts the moment a page opens, before the visitor has seen a banner, let alone made a choice. That is usually a configuration mistake: a tag added to the template instead of the consent tool, or a consent platform set to "notice only".

The cookie scanner visits the page once in our headless browser, as a first-time visitor from an EU server, and clicks nothing. It reports what happened before consent: the cookies that were set, the storage keys written, the other sites contacted, the known trackers among them, and whether a consent banner was showing. These are technical observations from one visit from an EU server, not legal advice.

What we report

  • Consent banner. Whether a banner was visible on arrival, which consent platform loaded it, and whether the page offers the IAB TCF or GPP interfaces. We recognise twelve common platforms, including OneTrust, Cookiebot, Didomi and Usercentrics, and any fixed panel that mentions cookies or consent and has a button. A screenshot shows the banner as a first-time visitor saw it.
  • Trackers before consent. Analytics, advertising, social and tag-manager services that loaded, matched by domain against our catalog of about 125 vendors written from their own documentation.
  • Cookies. Each cookie's name, the site that set it, whether it's first or third party, how long it lasts, its Secure, HttpOnly and SameSite flags, and the vendor it belongs to when we know.
  • Other sites contacted. Every other site the page loaded something from, with the number of requests, the kinds of resource and its category.
  • Hidden trackers. Names on your own domain that point to a tracking service through a CNAME record, a technique that makes third-party tracking look first party.

How the visit works

Our browser runs in a sealed container with no network of its own. Every request the page makes is checked and fetched by our safe fetcher, so a page can't reach private addresses through it, and our browser identifies itself as DNS Super. It waits for the page to go quiet for two seconds, up to 20 seconds, then records what it saw. A visit is capped at 30 seconds and 400 requests; if a page keeps loading past either limit, the result says so and lists what happened up to then.

Scans run as jobs, at most two at a time across the service, so a busy moment can mean a short wait before your scan starts. The wait doesn't count against the visit.

Reading the result

The result opens with the banner and its screenshot, then the trackers that loaded before consent, which are the most important part. The cookie table follows, with lifetimes in plain words and the vendor where we know it. Other sites contacted, storage keys and any CNAME cloaking come last.

Each finding links to a fix guide. Most fixes happen in your consent platform or tag manager: set each tracker to wait for its consent category, then scan again to confirm.

What the scan doesn't do

It doesn't accept or reject consent, scroll, log in or visit more than one page, and it never reads the values of cookies or storage. It can't tell whether a cookie is strictly necessary for your site, only which vendor it belongs to when our catalog knows. Requests to private or reserved addresses are refused, not followed, and the screenshot is a small image we resize ourselves rather than a link to the site.

Questions

Is this a GDPR compliance check?
No. These are technical observations from one visit from an EU server, not legal advice. We report what loaded and what was set before anyone clicked anything; whether that's allowed for your site depends on facts only you and your legal adviser know.
Do you click accept or reject?
No. Nothing is clicked, so everything we report happened before consent. That's the moment regulators look at first, and it's the one most often configured wrongly.
Do you read cookie values?
No. We record each cookie's name, domain, lifetime and flags, never its value, and only the names of storage keys. Our browser never has a field to hold a value.
Why does the scan miss a tracker I know is there?
Some trackers load only after scrolling, after a delay longer than our visit, or only in some countries. We visit once with an English (Ireland) browser and stop after 30 seconds. Services that aren't in our catalog are still listed under other sites contacted.
How much does a scan cost?
5 credits per scan, reserved when it starts and charged when it finishes. It needs an account and runs as a job. A scan whose page never loads is free.