Consent controls
Looks for visible accept, reject and category actions on the public page.
FREE THREE-STATE COOKIE SCAN
See what loads before visitors choose.
Enter a public website. CookiLow tests the browser before consent, after acceptance and after rejection — then shows the technical result here.
✓ No account required✓ No CMS access✓ Three browser states✓ Result shown on this page
DEMO CONSENT SCANcookilow.com
Before choiceAcceptReject
Meta Pixelconnect.facebook.net
TOO EARLYGoogle Analyticsgoogle-analytics.com
CHECKEssential sessionfirst-party
ALLOWED01
service loads before consentFix path and verification included
WHAT THE FREE SCAN CHECKS
Not just which cookies exist — when services are allowed to start.
CookiLow records public browser behaviour and turns technical signals into a result a website owner, marketer or developer can understand.
External requests
Records third-party hosts contacted in each consent state.
Browser storage
Observes cookies and other storage created during the tested flow.
Known services
Classifies familiar analytics, advertising and embedded-content tools when detected.
INSIDE YOUR RESULT
From a browser signal to a fix your team can verify.
The scan keeps the affected state, service and technical signal together, so the finding is useful beyond a generic cookie list.
Consent stateBefore choice
Observed serviceMeta Pixel
Technical signalRequest to connect.facebook.net
FindingOptional service started too early
VerificationFix the trigger, then repeat the same scan
THE THREE-STATE TEST
The same page, observed after three different visitor decisions.
Before choice
Optional services should wait while the visitor has not decided.
After accept
Permitted services may start after an affirmative choice.
After reject
Optional services should remain blocked after rejection.
MORE THAN AN INVENTORY
A cookie list tells you what exists. A behaviour scan shows what the choice changed.
Use an inventory to document technologies. Use CookiLow when you need to test whether the website followed the visitor's decision.
Lists detected cookies and servicesCompares requests, storage and services in three consent states
Describes what is presentShows what started before a visitor chose
Often requires a dashboard or emailed reportReturns the first public result directly on this page
Useful for policy maintenanceUseful for developers, marketing and repeatable fix verification
READ THE RESULT CORRECTLY
A technical snapshot, with a clear boundary.
A public scan is evidence of observed browser behaviour at one point in time. It is designed to find signals worth fixing — not to replace legal review.
FREE SCAN QUESTIONS
Know what the result can — and cannot — prove.
Clear expectations make the report more useful.
Do I need to install anything before the scan?
No. Enter a public domain and CookiLow will open the website in an isolated browser.
Why are three consent states necessary?
A list of cookies cannot show whether rejection actually blocks optional services. Comparing before choice, accept and reject makes that behaviour visible.
Will the scanner find every cookie on every page?
No public scanner can guarantee that. Results depend on the pages reached, dynamic behaviour, geolocation, bot protection and the consent controls available during the scan.
Does a clear result prove legal compliance?
No. It confirms only the technical signals observed during this scan. Legal texts, lawful bases and vendor decisions require separate review.
What should I do after fixing a finding?
Run the same scan again and compare the result. Paid monitoring is designed to preserve that history and catch later changes.