Is there a free cookie consent checker with no signup?

Yes. Public scans on this site need no account, no email and no card. They are rate-limited to 3 scans per IP per day and 1 scan per site per hour so the browser pool stays available to everyone.

How long does a scan take?

Usually under a minute. A scan loads the page in a clean browser session, waits for network idle, clicks the consent banner, waits again for tags to fire, and captures both states, so it is slower than a page-speed test and much slower than an HTML fetch.

Does it work on sites behind a login?

No. Scans run from a clean, unauthenticated session with no cookies and no prior consent, so anything behind a login is out of reach. That is also what makes the capture reproducible.

cookie consent checker

Cookie Consent Checker — Test What Fires Before Consent

ConsentProof is a cookie consent checker that scans any website with a real browser and records which cookies and third-party trackers fire before the visitor consents.

No account needed · results usually under a minute · Free public scans, rate-limited per site and per IP

A limited number of free scans run each day; if today's are used, we queue yours for tomorrow and email you.

What a cookie consent checker actually checks

A cookie consent checker answers one question: between the moment a page starts loading and the moment a visitor makes a consent choice, what already happened? That window is where compliance is won or lost, because UK PECR and the GDPR require consent to be given before non-essential cookies are set — not while the banner is on screen.

Checking it properly means loading the page in a clean browser session with no prior consent, recording every cookie and every third-party request during that window, then clicking accept and recording the same things again. The difference between the two captures is the evidence.

It is not a cookie policy generator, and it is not a consent banner. A banner is the control; a checker is the test that the control works. Plenty of sites have a well-configured banner from a good vendor and still leak trackers before consent, usually because a tag was added to Google Tag Manager without going through the consent gate.

Why a header-only checker gives the wrong answer

Several free checkers fetch your HTML and look at Set-Cookie headers. Almost nothing that matters is set that way. Analytics, session replay and advertising pixels are set by JavaScript after the page loads, so a checker that does not execute JavaScript reports a clean page for a site that is firing Hotjar and Meta pixels on load.

ConsentProof drives headless Chrome, so the capture reflects what a real visitor's browser did, including scripts injected by a tag manager and requests fired by third parties that other third parties loaded.

Reading the result

Every result page shows the verdict, the trackers that fired before consent, the cookie and request counts for both phases, the before and after screenshots, the four Google Consent Mode v2 signals, and a SHA-256 of the captured evidence with an absolute UTC timestamp.

The verdict has three states, not two. Fail means something fired before a consent choice. Pass means a banner was found and nothing non-essential fired. Inconclusive means no consent banner could be found, so the blocking behaviour could not be tested at all — which is not the same as passing, and we will not print a green tick for it.

Point-in-time checks go stale. A site that passed last month fails the week after somebody adds a marketing tag, which is the whole reason the paid product re-scans on a schedule and emails you the diff.

Frequently asked

What is a cookie consent checker?: ConsentProof is a cookie consent checker that scans any website with a real browser and records which cookies and third-party trackers fire before the visitor consents. It exists to test whether a consent banner actually blocks anything, rather than whether one is displayed.
Is there a free cookie consent checker with no signup?: Yes. Public scans on this site need no account, no email and no card. They are rate-limited to 3 scans per IP per day and 1 scan per site per hour so the browser pool stays available to everyone.
How long does a scan take?: Usually under a minute. A scan loads the page in a clean browser session, waits for network idle, clicks the consent banner, waits again for tags to fire, and captures both states, so it is slower than a page-speed test and much slower than an HTML fetch.
Does it work on sites behind a login?: No. Scans run from a clean, unauthenticated session with no cookies and no prior consent, so anything behind a login is out of reach. That is also what makes the capture reproducible.

Try ConsentProof

Free public scan, no account needed.

Start free Pricing