Web & SEO
Cookie & Tracker Scanner (GDPR)
See which cookies a website sets, whether they're Secure/HttpOnly/SameSite, which trackers and ad pixels it loads, and whether a consent banner tool is installed.
How to use
- 1Enter a website.
- 2Review cookies set on first load and third-party trackers found in the page.
- 3Check a consent tool is present if trackers are used.
Frequently asked questions
Why don't I see all cookies?
This scan sees cookies set by the server on the first request and trackers referenced in the HTML. Cookies created later by JavaScript need your browser's DevTools (Application → Cookies).
Do I need consent for these cookies?
Under GDPR/ePrivacy (EU/UK), strictly necessary cookies don't need consent; analytics, advertising and tracking cookies do.
Which consent tools are detected?
OneTrust, Cookiebot, Didomi, Usercentrics, Quantcast, TrustArc, CookieYes, Osano, Termly, iubenda, Complianz and Google Consent Mode.
Why Secure, HttpOnly and SameSite flags matter as much as which cookies exist
Two sites can set the exact same session cookie by name and still differ enormously in risk depending on these three flags: Secure ensures the cookie only transmits over HTTPS rather than leaking over an unencrypted connection, HttpOnly blocks JavaScript from reading the cookie's value (a real defense against cross-site scripting attacks stealing session tokens), and SameSite restricts whether the cookie gets sent on cross-site requests at all (a defense against cross-site request forgery). A cookie audit that only lists cookie names without checking these flags misses most of what actually determines whether a given cookie is a security liability.
Worked example: Cookie & Tracker Scanner
Scanning a typical e-commerce site on first load might reveal a session cookie properly marked Secure and HttpOnly, a cart-tracking cookie, and several third-party tracker references (an analytics pixel, an ad retargeting script) loaded directly in the HTML — plus a check for whether a recognized consent management tool like OneTrust or Cookiebot is present. Finding trackers loading with no consent tool detected at all is a specific, actionable gap: under GDPR/ePrivacy, non-essential cookies like analytics and advertising trackers need consent before they load, not just a cookie policy page describing them after the fact.
Why this scan can't see everything a site actually does
The FAQ is direct about the real limitation here: this captures cookies set by the server on the very first request and trackers referenced directly in the initial HTML — it has no way to see cookies that get created later by JavaScript running after the page loads, which is an increasingly common pattern for how modern analytics and marketing tools actually operate. Confirming the complete cookie picture for a site that sets most of its tracking cookies dynamically after load requires opening the browser's own DevTools (Application → Cookies) and interacting with the page, a manual step this automated scan can't replace.
Why the list of detected consent tools is a fixed, named list
The scanner checks for specific, recognizable fingerprints of a dozen named consent management platforms — OneTrust, Cookiebot, Didomi, Usercentrics, Quantcast, TrustArc, CookieYes, Osano, Termly, iubenda, Complianz and Google Consent Mode — rather than trying to infer generically whether 'some kind of banner' exists. That means a site running a lesser-known or custom-built in-house consent banner will show as having no detected consent tool even if it's fully compliant, since detection here works by matching known scripts and markers from that specific list, not by visually detecting any banner-shaped UI on the page.
A worked example: necessary versus non-necessary cookies in practice
A typical login or shopping-cart session cookie that's required for the site to function at all — keeping someone logged in, remembering what's in their cart — falls under 'strictly necessary' and doesn't legally require consent under GDPR/ePrivacy rules. A cookie set by an advertising retargeting pixel that tracks a visitor across other sites to show them ads later is the opposite case: it provides no function the visitor requested, exists purely for marketing purposes, and does require explicit consent before it's allowed to load. Scanning a site and seeing several of the latter type firing with no consent banner in place is a concrete, specific compliance gap, not a judgment call.
Related tools
- Website Accessibility Checker (WCAG 2.2 Quick Scan)
Scan a web page for common WCAG 2.2 accessibility failures — missing alt text, unlabelled form fields and buttons, empty links, heading order, page language and title, disabled zoom and more — with fixes for each.
- Accessibility Overlay Checker
Check whether a website uses an accessibility overlay widget (accessiBe, UserWay, AudioEye, EqualWeb and others) — and learn why overlays don't make sites accessible.
- Website Carbon Calculator
Estimate the CO₂ emissions of a web page from its size and monthly visits, using the Sustainable Web Design model — and see the impact of making it lighter.
- Domain Age Checker
Find out how old a domain is — its registration date and age in years and months, plus expiry and registrar — from the official registry data.
- Cookie Consent Banner Generator (GDPR-Ready Code)
Generate a lightweight, dependency-free cookie consent banner — Accept all, Reject all and per-category choices — that blocks analytics and marketing scripts until the visitor agrees. Copy-paste HTML, CSS and JavaScript.
- Cookie Policy Generator
Create a cookie policy listing the cookies your site uses — necessary, preferences, analytics and marketing — with how to manage consent, as required by the GDPR, UK PECR and the EU ePrivacy Directive.