Free Tool

Cookie / Tracker Scanner

Inspect a public page's first response for cookies and recognizable tracking code, with honest scope and readable evidence.

We fetch up to 1 MB of the public HTML response. Private networks and non-standard ports are blocked.

What a cookie and tracker scan can tell you

A first-response scan gives you a fast inventory of signals present in the HTML a server returns. It can reveal cookies set in HTTP headers and recognizable scripts for analytics, advertising, tag management, and session replay. That makes it a useful starting point when reviewing a new site, a vendor integration, or an unexpected change in your own stack.

The result is intentionally evidence-based: each tracker match names the signature it found, while cookies are shown with their declared scope and security attributes. A match indicates code is present, not that every visitor is necessarily tracked.

How to interpret response cookies

Secure restricts a cookie to HTTPS connections, while HttpOnly prevents client-side JavaScript from reading it. SameSitecontrols when a cookie can accompany cross-site requests. These attributes improve security, but they do not explain the cookie's purpose or determine whether consent is required.

Session cookies expire when the browser session ends. Persistent cookies use an Expires or Max-Age attribute. Review long-lived, broadly scoped cookies carefully, especially when a third party controls the receiving domain.

Why this is not a full browser audit

Modern pages often add trackers after hydration, a consent choice, a route change, or a user interaction. This scanner does not run JavaScript or click a consent banner, so those later requests are outside its view. Browser developer tools, consent-management logs, and a legal review remain important for a complete audit.

Use the report to form specific follow-up questions: who owns this script, which data does it send, how long is that data retained, and can the same product decision be supported with less visitor-level tracking?

Frequently Asked Questions

It fetches the public page's first HTML response, reads its Set-Cookie headers, and checks the returned markup for recognizable tracker signatures. It does not execute the page's JavaScript or crawl other pages.

No. A browser can load scripts, pixels, and cookies after JavaScript runs, after a user interacts, or after consent is granted. Treat this report as a transparent first-response check, not an exhaustive compliance audit.

No. Cookies can preserve a login, security state, language, cart, or other essential preference. Review each cookie's purpose, duration, and scope before deciding whether it is necessary or requires consent.

Some sites block automated requests, require authentication, or return a challenge page instead of their normal markup. In those cases, scan a public page and confirm the result with your browser's developer tools.

Start by removing tools you do not use and documenting the purpose of every remaining cookie. A cookieless analytics platform such as BuddyStat can provide site insights without persistent visitor identifiers.

Related tools

Keep working with a nearby calculator or utility.

View all tools

Understand traffic without tracking people

BuddyStat gives you clear website analytics with a lightweight, cookieless script and privacy-friendly defaults. Get started for free with up to 3,000 pageviews per month.

Start tracking for free