Cookie / Tracker Scanner

See which cookies and tracking scripts a public page sets.

We request the page once from our server, as a first-time visitor with no consent given. Nothing is stored.

Enter a public page to list the cookies and tracking scripts it sends.

Two places cookies come from

A cookie reaches a browser in one of two ways. The server can send it in a Set-Cookie header with the page, which is how logins, shopping carts, load balancers and bot protection usually work. Or a script on the page can write it after loading, which is how most analytics and advertising tools work.

This scanner sees the first kind directly. For the second kind it looks for the scripts themselves: if a page loads Google Analytics, Meta Pixel or Hotjar, you can expect their cookies once the scripts run.

Reading the cookie attributes

  • Domain and path decide which requests carry the cookie. No Domain means only the exact host that set it receives it.
  • Lifetime comes from Max-Age or Expires. Without either, the cookie is a session cookie and goes when the browser closes. Browsers cap lifetimes at 400 days.
  • Secure keeps the cookie off plain HTTP. HttpOnly hides it from JavaScript, which protects session cookies from injected scripts.
  • SameSite controls whether the cookie is sent on requests from other sites. Strict and Lax limit cross-site use; None allows it and requires Secure.

Limits of a single request

The scan acts like a first visit with no consent given, from a server rather than a browser. Sites that show a different page to bots, to other countries or after consent will look different in a real browser. To see everything, open your browser's developer tools, accept the banner, and check the Application or Storage panel.

If you want traffic numbers without adding to this list, OpenRevenue counts visits without cookies, so it needs no consent banner entry of its own.

Frequently asked questions

What does the scanner check?

It requests the page once, follows up to five redirects, and lists every cookie the server sets in its responses with its domain, path, lifetime and the Secure, HttpOnly and SameSite flags. It then reads the HTML for scripts, pixels and inline snippets from known analytics, advertising, session-recording, testing and consent tools.

Why are cookies like _ga missing from the list?

Many tracking cookies are written by JavaScript after the page has loaded, often only once a visitor accepts a consent banner. A server-side request does not run scripts, so those cookies never appear. The tracker list shows the scripts that would set them instead.

Do you store the cookie values?

No. Values are dropped on our server before the result is sent to you; the table only shows names and attributes. We do not keep the page, the cookies or the address you entered.

Does this tell me whether my site is GDPR compliant?

No tool can do that on its own. Compliance depends on what each cookie is for, whether you ask for consent before non-essential cookies are set, and what your privacy policy says. Use the results as an inventory to check against your consent setup.

Which pages can be scanned?

Public http and https pages on the standard ports that return HTML. Addresses on private networks, localhost and internal hostnames are refused, and only the first 2 MB of HTML are read.

Related tools

All tools