About this tool
List the cookies a site sets before consent, with domain, lifetime, Secure, HttpOnly and SameSite flags and a likely purpose.
Set-Cookie headers are collected from every response in the redirect chain. Each cookie’s attributes are parsed, its lifetime is calculated, first- or third-party is decided from the domain, and the purpose is estimated from well-known names (for example _ga for analytics).
Example: check Page URL = https://github.com/.
Cookies created later by JavaScript or after a consent choice are not visible to this check. It is not a legal compliance assessment.
Quick steps
- Enter the address of a public page or domain.
- Press Check. The 1CLIK server visits it, which can take a few seconds.
- Read each line — Good, Improve, Problem or Info — with a hint on what to fix.
1CLIK’s server fetches only the public address you enter. Private and internal addresses are refused, and results are cached for a few minutes, not saved to your account.
FAQ
How does the Cookie Scanner work?
Set-Cookie headers are collected from every response in the redirect chain. Each cookie’s attributes are parsed, its lifetime is calculated, first- or third-party is decided from the domain, and the purpose is estimated from well-known names (for example _ga for analytics).
What should I keep in mind?
Cookies created later by JavaScript or after a consent choice are not visible to this check. It is not a legal compliance assessment.
Why can the result differ from what I see in my browser?
The check sees what the server sends to 1CLIK, before any JavaScript runs. Sites can also answer automated requests differently, block them, or vary by country.