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.