Klaro Compliance Checker Verify Your Setup Is Working
Klaro is a popular open-source, self-hosted consent management platform loved by developers for its flexibility. But self-hosted means self-maintained - scripts not declared in your klaroConfig, inline scripts, and dynamically loaded resources can fire outside Klaro's blocking scope, silently, with no dashboard to flag the issue.
We work alongside Klaro - not against it
Klaro manages your consent configuration through its open-source framework. We independently verify that configuration produces the right outcome in a real browser - catching configuration gaps and undeclared scripts that Klaro cannot see from inside the page.
What we verify that Klaro alone cannot confirm
Klaro controls what it controls. These six checks require independent observation from outside the page.
| Check | Why Klaro alone cannot confirm it |
|---|---|
| Pre-consent cookies | Klaro blocks scripts it manages through its configuration file - but scripts not declared in klaroConfig, inline scripts, and dynamically loaded resources can fire outside its blocking scope. |
| Google Consent Mode v2 signals | Klaro can be extended to generate Consent Mode signals, but signal timing and the presence of all 4 v2 signals (ad_user_data, ad_personalization) must be verified from outside the page. |
| Reject All enforcement | A site update, new script tag, or configuration drift can add scripts that fire regardless of the consent state Klaro tracks - and self-hosted setups have no central dashboard to flag the issue. |
| GPC signal handling | Global Privacy Control requires a browser-level test. Klaro can be configured to honor GPC signals - but the klaroConfig setting does not confirm it works in a real browser session. |
| Dark pattern checks | Klaro provides the consent modal framework and CSS styling hooks. The choices made during implementation - button prominence, default states, modal behavior - are entirely in the developer's hands. |
| Multi-region behavior (up to 15 regions) | Klaro supports conditional configuration, but geo-targeting logic is custom-implemented. We test from actual EU, California, UK, and other jurisdiction IPs to verify region-specific rules work as intended. |
How we detect Klaro on your site
Four independent fingerprint signals confirm Klaro is present and active.
JavaScript globals
klaro, klaroConfig
DOM elements
.klaro .cookie-modal, .klaro .cookie-notice
Consent cookies
klaro
Script domains
cdn.kiprotect.com/klaro (often self-hosted)
See the full list of 40+ detected CMPs: Supported CMPs
Verify your Klaro configuration works end-to-end
Cookie Compliance Checker is launching soon. Join the waitlist for early access and be among the first to scan your site.