Skip to content
TagSentry
Blog

Guide · Consent

How to check website cookies, and what the list misses

Check a site's cookies in your browser in two minutes, then the two places a cookie list leaves out. Tested on 188 random websites before any click.

Shaun Brown · November 16, 2026 · 6 min read

The short answer

To check a website's cookies, open it in a private window, click nothing, and look in your browser's developer tools under Application › Cookies (Chrome and Edge) or Storage › Cookies (Firefox). Then check two places a cookie list doesn't show: the Network tab, for who received data, and Local storage, where many ad tags keep their IDs. Press Reject, reload and look again. When we loaded 188 random websites from a US connection, 99 sent data to trackers before any click.

How to see a website's cookies in your browser

Every desktop browser shows you the cookies a page has set. You don't need an online tool for this, and it takes about two minutes.

  1. Open a private or incognito window, so no old cookies or earlier choices get in the way.
  2. Open developer tools (F12, or Cmd+Option+I on a Mac) before you load the site, then load it.
  3. Don't touch the cookie banner. The first look is what a new visitor gets before they choose.
  4. In Chrome or Edge, go to Application › Storage › Cookies and click the site's address. In Firefox, it's Storage › Cookies.

The table lists each cookie's Name, Value, Domain and Expires / Max-Age. The domain tells you who can read it: the site's own (a first-party cookie) or another company's, such as doubleclick.net (a third-party cookie). Across the 188 sites in our test, about 70% of all cookies set (3,065 of 4,402) were on another company's domain.

Which cookies are trackers

The name usually gives a tracker away. These are the ones we saw most often, and what each company's own documentation says they're for.

CookieSet byWhat it's for
_ga, _ga_<ID>Google AnalyticsTells one visitor from another, and keeps the session
_gcl_auGoogle AdsAd measurement
IDEGoogle's ad network, on doubleclick.netAdvertising
_fbpMeta PixelAn ID for the browser, set on the site's own domain
_clck, _clskMicrosoft ClarityA visitor ID, and linking pages into one recording
MUIDMicrosoftIdentifies a browser across Microsoft's services, used for ads
__hstc, hubspotutkHubSpotTracking visitors and matching them to form fills
bcookie, li_sugrLinkedInA browser ID, and matching a visitor to an identity

Cookies with names like PHPSESSID, cf_clearance or a cart ID usually keep the site working. UK and EU rules let cookies that are strictly necessary for what the visitor asked for run without a yes.

A cookie list shows what the page stored. What the page sent, and to whom, is somewhere else.

The Network tab. This is the list of every request the page made. Type a tracker's address into the filter box, such as facebook.com/tr, google-analytics.com, analytics.google.com or bat.bing.com. Any hit there means data went to that company, whether or not a cookie came back.

Google's cookieless pings. Consent Mode is Google's way of telling its tags what the visitor agreed to. In its Advanced setup, Google's tags keep sending requests while consent is denied. Google says these go "without cookies" and carry the consent state, the time, the browser and the referrer.

So you can see a clean cookie list and a Google request in the Network tab on the same page. The gcs value in the request says which kind it is: G100 means both storage signals were denied. Our Consent Mode check decodes the other values.

Local storage. Under Application › Local storage, a site can keep IDs that never appear as cookies. On 56 sites in our test we found a tracker's key there, most often Google Ads' _gcl_ls (33 sites).

The UK's ICO lists tracking pixels, local storage, scripts and fingerprinting next to cookies, as technologies its cookie rules cover. A check that counts only cookies looks at one item on that list.

What we found on 188 random websites

On 16 November 2026 we drew 240 websites at random from the Tranco top-sites list, between rank 10,000 and 300,000, and loaded each homepage once in a fresh browser. We clicked nothing, waited eight seconds, and recorded every cookie, the keys in local storage, and every request to Google and 20 other known trackers. 188 loaded.

Before any clickSites
Set no cookies at all35
Set a tracking cookie101
Sent data to a tracker (anything but Google's cookieless ping)99
Sent data to a tracker but set no tracking cookie2
Set a tracking cookie, with no request to a tracker we know4
Kept a tracker's ID in local storage56

Meta was the commonest destination after Google (32 sites), then LinkedIn (24) and Microsoft (22).

On most sites the two checks agreed: where trackers sent data, they also set cookies. The exceptions went both ways. Two sites sent Google Analytics requests without setting a Google cookie, and three of the 32 sites that sent data to Meta had no _fbp cookie. A cookie list would have shown those sites as clean for that tracker.

Two other sites set a Google Analytics cookie and made no request to Google at all. That usually means their analytics goes through the site's own server first. On those, the Network tab shows nothing going to Google, and the cookie is the only clue.

We loaded every site from the US, where most sites don't ask first. So these numbers describe what a US visitor gets. They aren't a verdict on what a European visitor sees.

Check again after Reject, and from the right country

The first look shows what happens before anyone chooses. To see whether the banner does its job, repeat it after a Reject.

  1. Press Reject (or "only necessary").
  2. Delete the tracking cookies in the Application panel, leaving the banner's own consent cookie.
  3. Reload, and check the cookie list, the Network tab and local storage again.

After a Reject, no new tracking cookies should appear, and the only Google requests should carry gcs=G100. When we ran this on 45 European banners last month, 10 kept sending data to trackers after Reject. The GDPR cookie banner guide has that test and what the rules ask for.

Location matters too. Many banners only show to visitors from places whose law asks first. If you're in the US and your customers are in Germany, a VPN set to Germany shows you what they get. For the US side, see do you need a cookie banner in the US?

They save time if you know what they did. Many load your page once, from one country, and list what they found, which is the first look above done for you.

Before you trust a result, find out whether it clicked anything first, which country it loaded from, and whether it reports requests as well as cookies. A result that lists only cookies tells you the least.

Where TagSentry fits

Our free scan at app.tagsentry.ai/scan does the first look for you, with no account. It loads your site once from the US and clicks nothing. It names the trackers that ran before any choice and lists Google's cookieless pings separately. If a banner loads late, it says how many trackers ran before it.

It also reads the Consent Mode setting Google sees first and whether Tag Manager is on the page. For a US-facing site, it checks whether visitors have a way to opt out. It's one page load, and it isn't legal advice.

If you want a banner that sets Google's consent signals to denied before any tag runs, with the rules each place's law asks for, see how TagSentry's consent works.

Sources

  1. Chrome for Developers: View, edit, and delete cookies
  2. Chrome for Developers: Network features reference
  3. Firefox Source Docs: Storage Inspector
  4. Google Analytics Help: Google Analytics cookie usage on websites
  5. Google Business Safety: Cookies used by Google's advertising products
  6. Meta for Developers: fbp and fbc parameters
  7. Microsoft Learn: Clarity cookies
  8. HubSpot: Cookies set in a visitor's browser by HubSpot
  9. Google for Developers: Consent mode overview
  10. ICO: What are storage and access technologies?
  11. LinkedIn: Cookie table
  12. ICO: What are the exceptions?
  13. Tranco: a research-oriented top sites ranking