Cookie Analyzer
About the Cookie Analyzer
The Cookie Analyzer inspects the cookies a website sets when you load it, listing each cookie's name and the security attributes attached to it. Cookies are small pieces of data the server stores in your browser to maintain sessions, remember preferences, and track behavior across requests, and they are delivered through the Set-Cookie response header. This tool decodes those headers so you can see exactly what a site is storing and how carefully it is protecting that data.
The key attributes it reports are the ones that govern security and scope. The Secure flag ensures a cookie is only sent over HTTPS, HttpOnly prevents JavaScript from reading it which blocks a major cross-site scripting theft vector, and SameSite (Strict, Lax, or None) controls whether the cookie travels on cross-site requests, which is the core defense against cross-site request forgery. The tool also surfaces expiration and domain or path scope, distinguishing short-lived session cookies from long-lived persistent ones.
Common use cases include privacy and GDPR or ePrivacy compliance reviews, auditing third-party tracking cookies, verifying that authentication cookies are properly hardened after a framework change, and debugging session issues where a login does not persist. It pairs naturally with the Security Headers Checker for a complete picture of a site's response-level protections and with an SSL check when confirming that Secure cookies are actually delivered over encrypted connections.
A practical tip: any cookie carrying a session or auth token should have Secure, HttpOnly, and SameSite set, and SameSite=None must always be combined with Secure or modern browsers will reject it. Watch for an excessive number of third-party cookies, which often signals heavy ad or analytics tracking that may need consent banners, and prefer scoping cookies tightly with explicit domain and path values rather than leaving them broad.
Frequently asked questions
- What do the Secure and HttpOnly cookie flags do?
- Secure ensures the cookie is only transmitted over HTTPS, and HttpOnly stops client-side JavaScript from reading it, which blocks a common cross-site scripting theft path. Both should be set on any sensitive session cookie.
- What is the SameSite attribute for?
- SameSite controls whether a cookie is sent on cross-site requests. Strict and Lax help prevent cross-site request forgery, while SameSite=None allows cross-site use but must be paired with the Secure flag.
- What is the difference between session and persistent cookies?
- Session cookies have no expiration and are deleted when the browser closes, while persistent cookies set an Expires or Max-Age date and survive across sessions. Persistent cookies are typically used for preferences and long-term tracking.
- Why does the analyzer matter for privacy compliance?
- Regulations like GDPR and ePrivacy require disclosure and often consent for non-essential cookies, especially third-party trackers. Listing every cookie and its scope helps you confirm your consent banner and privacy policy match what the site actually sets.
Analyze HTTP response headers
Check security headers configuration
Check SSL certificate validity and expiration
Test HTTP compression support
Measure website load time
Follow redirect chains