Download websites that use Cookiebot

About Cookiebot

A consent banner is a legal instrument that happens to be written in JavaScript. Cookiebot exists because a site owner concluded, or was advised, that the site processes personal data belonging to people protected by European privacy law and that the processing needs a recorded lawful basis. So a detection in the Cookie compliance category is unusual among technology detections. What gets identified is not a capability the site has, it is a belief the site's owner holds about its own regulatory exposure, and beliefs of that kind are expensive to act on.

Somebody scanned the site, categorised its cookies, wired a blocking layer in front of the analytics and advertising tags, and accepted that a share of visitors would decline and vanish from the reporting. Nobody does that for entertainment. The platform is published by Cybot and has been available since 2012, and it competes with a crowded field of consent tools, so each installed banner represents a decision taken against alternatives rather than a default that arrived with the theme.

Detection here is more dependable than in most categories, because a consent layer has to run on every page and has to run early, ahead of the tags it gates. As of September 2026 we record the platform on 306,374 sites. 109,378 of them resolve to United States, which reads oddly for a tool built around European regulation until you remember that the obligation follows the visitor rather than the server. American companies serving European customers carry the same duty as European ones, and the domain mix concentrating in .com says the same thing from a different angle.

Two limits deserve naming. A consent tool tells you nothing about whether a site's compliance is correct, only that an attempt was made and that a particular vendor was paid or trialled to make it, and plenty of banners are configured badly enough to be worse than none. The licence is also recorded as Freemium, so the population mixes small free tier installations with serious enterprise deployments, and the page itself rarely reveals which is which.

For anyone selling privacy tooling the value is obvious, since the list is a competitor's install base and consent platforms get replaced more often than most infrastructure. The less obvious use is as a filter on everything else. A site running any consent platform is a site taking legal exposure seriously enough to spend money on it, which makes the population a workable proxy for organisations with a compliance budget, a legal reviewer somewhere in the chain and an advertising or analytics stack worth gating in the first place. Filters like that only exist for somebody holding the whole population, because the question was never about one domain.