cookiebanner.free

How we check

One visit, one homepage, no clicks. This page says exactly what that covers, and what it doesn't.

The visit

  1. We open the homepage in a fresh browser with no history, in a container of its own, in a datacenter in the EU. Every result says where.
  2. The browser presents itself as an ordinary desktop Chrome, with a regular user agent and nothing that announces automation. Sites often behave differently for bots, and we want to see what people get.
  3. We follow redirects to wherever the homepage lands. Only that page, nothing deeper.
  4. We wait until the page goes quiet, then a few seconds more. A page that hasn't loaded after 30 seconds counts as timed out.
  5. We click nothing, scroll nothing, accept nothing.
  6. We record every cookie, everything in localStorage, sessionStorage and IndexedDB, every request and where it went, when each of those happened, whether a cookie banner appeared, and a screenshot of the first screen at 1280 by 800.
  7. We also note whether the homepage links to our badge. A site that shows the badge gets checked again every week.
  8. We look up every host the page talks to. A subdomain that points to a tracker counts as that tracker.
  9. We only visit public addresses on the usual web ports, and check every redirect and lookup against that.
  10. The browser only records. Levels and the result are worked out afterwards by a versioned classifier, so a fix to it can be applied to old scans without visiting again.

What we can't see

  • What the server does with its logs
  • Analytics that run on the server
  • Anything after a click, a scroll or a login
  • Pages other than the homepage
  • What the site does for visitors outside the EU

So a pass means: nothing seen in the browser, on first load, from the EU, on that date.

Results are observations from one visit, not a judgement on legal compliance.

Results

Cookie-banner free
No identifiers stored on your device and no trackers contacted on first load. Analytics that stores nothing and builds no profile across sites is allowed, and named on the result. The only result that gets the stamp and a badge with the site's domain.
Asks first
A banner was shown, and nothing that needs consent happened before an answer.
Tracks before asking
Identifiers or cross-site tracking before any answer, with or without a banner.
Couldn't check
Blocked, timed out, unreachable, or pointing somewhere we don't check, like a private address. Never counted as a pass.

Levels

Every finding gets one. The result follows from what was found before any click.

  • S5 Cross-site. Another company can recognise you on other sites.
  • S4 Identifier. This site can recognise you on later visits.
  • S3 Unknown. Something is stored on your device, and we can't tell what for.
  • S2 Contact. A request that stores nothing on your device. Your IP address reaches whoever runs it.
  • S1 Essential. Needed for the site to work.

Only essential, contact and unknown findings, and no banner: cookie-banner free. The same with a banner: asks first. Any identifier or cross-site finding: tracks before asking.

How a finding gets its level

  1. Anything stored on another company's domain is cross-site.
  2. A request to a known tracker is cross-site, even without a cookie. We use the EasyPrivacy list. On the site's own domain it is an identifier: no other company is reached, but the site can still recognise you.
  3. A name on the site's own domain that points to a tracker on another domain counts as that tracker, so it's cross-site.
  4. A cookie we recognise as tracking, like _ga or _fbp, is an identifier, even on the site's own domain.
  5. A cookie we recognise as essential, for a session, form protection or bot protection, is essential. Within limits: a session cookie that lives for months is judged like any other cookie.
  6. A cookie we don't recognise, that lives longer than 30 days and holds an ID-like value, is an identifier. We label it "looks like a persistent identifier". The same goes for an ID-like value in localStorage.
  7. Any other cookie we don't recognise is unknown. We show it, and it doesn't count against the site.
  8. The files that show the cookie banner are never counted as tracking: essential on the site's own domain, contact anywhere else.
  9. Any other request to another company is contact: your IP address went there.
  10. We judge a cookie by what it does: its name, lifetime, scope and value. No framework or platform gets a free pass.

"Cookie" here includes localStorage, sessionStorage and IndexedDB. We never store cookie values. The scanner looks at their length and randomness, then throws them away.

Analytics without cookies

Some analytics count visits without storing anything on your device. A request to a vendor on the list below is contact, not tracking, as long as nothing in that visit was stored by its script or on its domain. If something was, the request counts as a known tracker.

A vendor is listed when it says it uses no cookies or other storage on your device, builds no profile across sites, and sells no data. Each scan checks the first part again.

Fathom Analytics
Fathom states it uses no cookies or similar technology, builds no profile across sites, and does not sell data.
Matched on usefathom.com
Plausible Analytics
Plausible states it sets no cookies and stores nothing on the device, keeps no profile across sites, and does not sell data.
Matched on plausible.io
Simple Analytics
Simple Analytics states it sets no cookies and stores nothing on the device, keeps no profile across sites, and does not sell data.
Matched on simpleanalytics.com and simpleanalyticscdn.com
Pirsch Analytics
Pirsch states it uses no cookies, does not recognise visitors across websites, and does not sell data.
Matched on pirsch.io
Umami
Umami states its tracker uses no cookies, does not track people across websites, and does not sell data. Umami Cloud collects on gateway.umami.is.
Matched on umami.is and api-gateway.umami.dev

We can't see what a vendor does with the data on its own servers.

The same goes for Plausible and Umami installed on the site's own domain, recognised by the EasyPrivacy rules that name their scripts, and for a listed vendor's service on a name of the site that points to that vendor. In each case nothing in that visit may be stored from that address.

To suggest a vendor, write to [email protected]. A place on the list is never paid for.

Classifier changes

Observations never change. How we read them can. When it does, the classifier gets a new version and stored results are read again with it. Every result shows the version it was read with.

  • v1.3 Plausible and Umami installed on a site's own domain count as analytics without cookies, under the same conditions. Shopify's own consent banner counts as a consent tool, and its 2026 cookies _shopify_analytics and _shopify_marketing as tracking.
  • v1.2 GoatCounter is no longer listed as analytics without cookies: it doesn't state that it builds no profile across sites or sells no data. Session cookies of Grav, Craft CMS, Drupal and WordPress are recognised as essential.
  • v1.1 Analytics without cookies and consent records work as described above.
  • v1.0 First version.

Disputes and removal

A finding is wrong
Tell us at [email protected], with the address of the result. If we read something wrong, we fix the classifier and list the change above.
You fixed something
Ask for a rescan on the domain's page, once a day. The new result becomes the latest. Older results stay in the archive.
You own the domain and want out
Add a DNS TXT record cbf-opt-out to it, then check on the opt-out page. Every result leaves the archive and we don't scan it again. Can't change your DNS? Write to [email protected].