Checklist

Free cookie scanners compared: after Reject All, who still sees the request?

Run the free scan

Four free cookie scanners on one Shopify store: Cookiebot, CookieYes, CookieScript, Termly. None showed which hosts still sent requests after Reject All.

In brief

On Store F, four free cookie scanners finished empty or never left a progress screen. None showed who still received requests after Reject All. The request log, with no HAR, showed the hosts that kept requesting. After Reject All and one reload, GA, GTM, syndication, TVSquared, Attentive, Dynamic Yield, and Elevar still requested. Northbeam, Heap, Contentsquare, and a set of ad hosts stopped. Cookies already set stayed. One US session on October 7, 2026. This page is not legal advice.

This page records one automated browser session on Store F, a bedding brand on Shopify with OneTrust, after Reject All. It is not legal advice and not a ruling on any store. The record is a request log plus the four free-scan screens. Observation is not counsel permission.

Last updated October 28, 2026. The capability table is doc-sourced, not verified by us. Check date: 2026-10-07 (Asia/Shanghai). The 2GDPR wording was checked on 2026-10-11 (Asia/Shanghai). The CookieConsentHQ and ConsentStack wording was checked on 2026-10-28 (Asia/Shanghai).

Short answer

The same Store F URL went through Cookiebot, CookieYes, CookieScript, and Termly on October 7, 2026. Cookiebot stayed on Preparing data for more than three minutes and asked for an email. No email was entered. CookieYes finished empty. CookieScript returned no report, twice. Termly stayed on Scanning your website for more than two minutes. None of those screens listed who still received requests after Reject All.

A separate pass logged request hosts. There is no HAR. Before any click, every host in the table below was already requesting. After Reject All and one homepage reload, google-analytics.com, googletagmanager.com, googlesyndication.com, the TVSquared collector, Attentive, Dynamic Yield, and the Elevar GTM suite were still requesting. northbeam.io, heap-api.com, contentsquare.net, and the stackadapt, tapad, impact, grin, pdscrb, and mgln hosts were not seen again in that window.

Cookies already on the profile stayed, including _ga, _fbp, and cookies for Attentive, Northbeam, Heap, Contentsquare, TVSquared, and Ometria. A free US-baseline visit is not an EU or California legal conclusion. ConsentProbe does not install a CMP.

What the October 7, 2026 session showed

The browser was an automated session. Requests were counted by host for about 10 to 12 seconds after network idle. There was no DevTools Network panel and no HAR export. The shell exit was Ashburn, Virginia, in the United States. The browser was assumed to use that same egress. It was not checked on its own.

The profile already held Store F cookies from earlier visits. OptanonAlertBoxClosed was absent, so the OneTrust banner still appeared. The first layer showed Reject All, Manage Preferences, and Accept Cookies. Fresh was the homepage with no banner click.

Reject All was clicked on that first layer. The session waited about 10 seconds, then reloaded the homepage once. The banner did not return. OptanonAlertBoxClosed was set, and the browser posted to privacyportal.onetrust.com. No product page was opened on this pass.

The table is the host set written down for this compare. Other hosts in the same log, including a fraud vendor and a wishlist relay, sit outside it. A host missing after the reload was not seen in that window. Absence in the window does not prove the tag never fires.

Swipe to see more

Store F request hosts. Fresh, then Reject All plus one homepage reload. One US session. No HAR.
HostFresh, no clickAfter Reject All and reload
google-analytics.comyesyes
googletagmanager.comyesyes
googlesyndication.com (pagead2 and ade)yesyes
us.tvsquared.com collectoryesyes
attn.tv and attentivemobile.comyesyes
dynamicyield.comyesyes
getelevar.com (Elevar GTM suite)yesyes
northbeam.ioyesno
heap-api.comyesno
contentsquare.netyesno
stackadapt, tapad, impact, grin, pdscrb, mglnyesno

Cookies stayed, and parameters were not read

None of those cookies were cleared after Reject All. _ga, a _ga_* cookie, _fbp, and cookies for Attentive, Northbeam, Heap, Contentsquare, TVSquared, and Ometria were still present. This session did not check whether the values were rewritten. OneTrust did not delete the existing cookies on reject in this session.

Query parameters were not read. A google-analytics.com row in this log is not split into a cookieless Consent Mode ping and a hit that still carries a cookie. That split is the cookieless ping check.

What the four free scanners showed

Each of the four is a free online cookie scanner: paste a URL, no account. The same homepage URL was submitted to each free public scanner. No email was entered. Empty and unfinished screens are the result. Nothing in this table is a filled cookie inventory.

Cookiebot's blurred overlay included placeholder lines, including "Low risk" and zero trackers. The scan had not finished, so those lines were not treated as a report. The visible copy talked about prior consent in general. It did not name Reject All, and it did not list hosts that still received requests after a reject.

CookieYes completed. The page said: Sorry! We couldn't find any cookies on this URL. CookieScript was tried with the www URL and again without www. Both times the page said: Oh... Sorry, no report found. Termly was still on Scanning your website after more than two minutes, with a sign-up prompt to be notified. The page says 30 to 60 seconds is normal.

None of the four clicked Reject All. None showed the after-Reject host list from the request log.

Swipe to see more

Store F through four free scanners on October 7, 2026. Empty or unfinished. Not filled inventories.
ScannerWhat the free page showedAfter-Reject hosts shown?
CookiebotStuck on Preparing data for more than 3 minutes. Email form for the report. No email entered. Blurred overlay not counted.No
CookieYesFinished. Sorry! We couldn't find any cookies on this URL.No
CookieScriptTried twice. Oh... Sorry, no report found.No
TermlyStill on Scanning your website after more than 2 minutes. Sign-up prompt to be notified.No

What the vendor pages say they do

The next table is what the vendors' own pages say a free scanner can do. Every cell is doc-sourced, not verified by us. Check date: 2026-10-07 (Asia/Shanghai). The Store F run is the section above, not this table.

Cookiebot's scan-report article describes prior-consent flags, including cookies set before consent. CookieYes says its checker can include some cookies set while someone uses a banner. The CookieScript and Termly scanner pages do not describe a labeled before-Accept pass. Store F produced no finished Cookiebot report, so this session has no prior-consent flag.

Those pages name GDPR, ePrivacy, or US state laws. They do not publish the country of the crawl. This article does not assign a scan location to Cookiebot, CookieYes, CookieScript, or Termly.

Public comparison pages checked the same day mostly set price, page limits, and cookie categories next to each other. ConsentStack published its own scanner study on 2026-09-01. That study is their evidence. Its cookie checker page counted more than 6,800 sites scanned as of 2026-10-28 (Asia/Shanghai).

Swipe to see more

Doc-sourced, not verified by us. Check date: 2026-10-07 (Asia/Shanghai).
ScannerCookie inventory in the docsReject All recheck in the docsRequest-level evidence in the docsFree public limit in the docs
CookiebotYes. The report uses Necessary, Preferences, Statistics, Marketing, and Unclassified. The checker page also names necessary, functional, analytics, performance, and advertising.Not claimed on the free checker page.Claims first- and third-party cookies and third-party requests, with Source, Initiator, and Via. No downloadable HAR is claimed.Free checker with an email report. A separate free CMP subscription is one domain under 50 pages, and automated monthly scanning is off.
CookieYesYes. Necessary, Functional, Analytics, Performance, and Advertisement, with cookie ID, domain, duration, and description.Not claimed on the free checker page.Detects HTTP, JavaScript, and HTML5 local storage cookies. The free checker page does not claim a full third-party request list.Free plan: 5 scans a month, 100 pages a scan, 5,000 pageviews a month. No scheduled scan.
CookieScriptYes. A cookie test organized by category, including pattern cookies for random names.Not claimed on the scanner page.The scanner page talks about cookies and running JavaScript. It does not claim a third-party request list.Public scan without an account: 10 pages.
TermlyYes. Six categories: Essential, Performance and Functionality, Analytics and Customization, Advertising, Social Networking, and Unclassified.Not claimed. The scanner crawls, categorizes, and emails a cookie report.Cookie report. The product page does not claim a HAR or a request waterfall.Free to scan. Free plan: quarterly scans.

2GDPR's free public check

The 2GDPR homepage says: "Free public checks have been discontinued". The next line says: "To use our service or API, please contact us for pricing". Fetched 2026-10-11 (Asia/Shanghai).

This page did not run 2GDPR and makes no claim about its results. For a same-store record, the Store F table above lists hosts before any click and after Reject All plus one reload.

CookieConsentHQ's free check and scanner

Based on CookieConsentHQ's own pages (fetched 2026-10-28, Asia/Shanghai); we did not test it. The free checker at /check loads one page as a first-time visitor with no stored consent. The page says: "One page, one location, one visit. It is a quick diagnostic, not an audit." Its FAQ says the checker "can only press Accept on a CookieConsentHQ banner." On another vendor's banner it reports what loads before a choice and leaves the Accept step to the site owner. None of the four pages we read says the checker presses Reject.

The cookie scanner in the dashboard crawls up to 50 pages a scan on the free plan and up to 150 on paid plans. Its page says it loads pages "before consent and revisits the first few pages after Accept all." The scanner page, the help centre, and the changelog describe no pass after Reject. The changelog dates both tools to 19 October 2026.

This page did not run CookieConsentHQ. For hosts that kept requesting after Reject All on one store, see the Store F table above.

Checklist audits vs request logs after Reject

On October 12, 2026, Cookiebot by Usercentrics released a Retail Consent Audit Guide through DesignRush. The release calls it a five-module self-serve audit that does not need a developer. The modules are the banner and consent experience, GPC and other opt-out signals, checkout, chat and third-party widgets, and social and AI referral traffic. The banner module checks whether the banner loads before tracking, the GPC module tests whether the signal is recognized and honored, and the checkout module checks whether tracking tags are properly gated. This page is not legal advice. Source: Newsfile / DesignRush press release, 2026-10-12, fetched 2026-10-13.

The release does not say to export a request log after Reject and compare hosts. This page adds that step on the same store. After Reject All and one reload, it records which hosts still received requests.

On Store F, none of the four produced a host list after Reject All. Cookiebot and Termly were stuck while scanning. CookieYes finished empty. CookieScript said no report. None of the four tested a Reject flow. Hosts that still sent requests after Reject All and one reload are the rows marked yes under After Reject All and reload in the Store F host table.

The free US-baseline visit records one fresh load. It does not click Reject All. All free checks are listed on one page. Fresh, Reject All, and Accept All run together in the EU audit. Open EU and California pricing.

Configuration health scores vs requests after Reject

Cookiebot's Configuration Health Checker is a beta tool inside Cookiebot Admin, not yet open to every account. Its support article says the checker "analyses your CMP configuration and identifies gaps against best practices for your chosen privacy legislation". It "runs a check against your current CMP configuration" and returns a Risk Assessment score from 11 rules. One rule is "Reject all button must be visible". The article does not describe loading the storefront, clicking Reject All, or logging requests after the click. Source: Cookiebot Support, updated 2026-10-16, fetched 2026-10-20.

The same article says: "It is not a legal compliance audit." It lists "the declarations and tracking behavior deployed on your site" among the other factors a full review may involve. A request log records that behavior. After Reject All and one reload on Store F, the yes rows in the host table above were still requesting. Hosts from the other Shopify captures are in Table 1, Still sending after the click. This page did not run the checker, and Store F uses OneTrust. This page is not legal advice.

How to read a free scan next to a Reject log

A free website cookie scanner returns a list. Read the file it actually returned, then put it next to a labeled Reject host list.

  1. If the free page says it found no cookies, or the scan never finishes, write that sentence down. Do not copy numbers off a blurred preview.
  2. Check whether that product clicked Reject All. These four free pages did not.
  3. On the same URL, log request hosts before any banner click. Label that pass Fresh.
  4. Click the Reject control that is actually on the page, reload, and log which hosts still request. If the first layer has no Reject All, record the control you used and do not rename it.
  5. Put the scanner screen next to that host table. An empty scanner page on Store F sat beside hosts that were still requesting.
  6. Keep the exit labeled. A free US-baseline scan is not an EU or California legal conclusion.

Run a free US-baseline visit

The free Reject All tracking check explains what to look for after Reject. The free US-baseline visit records one fresh load. It does not click Reject All. Fresh, Reject All, and Accept All run together in the EU audit. The cookie audit stores the report. All free checks are listed on one page. The testing hub picks the next pass.

FAQ

Do free cookie scanners show who still gets requests after Reject All?

On this Store F session, no. Cookiebot, CookieYes, CookieScript, and Termly did not show which hosts still received requests after Reject All. The request log did. There is no HAR.

Which is the best free cookie scanner for checking Reject All?

On Store F, none of the four free scanners tested here showed which hosts still sent requests after Reject All. Pick a tool that clicks the banner's own Reject control, reloads, and lists hosts after the click. You can also run the DevTools steps on this page by hand. This is a technical check, not legal advice.

Did these four free scanners return a cookie inventory?

No filled inventory. CookieYes finished and said it couldn't find any cookies on this URL. CookieScript said no report found, twice. Cookiebot stayed on Preparing data and was email-gated. Termly stayed on Scanning. A blurred Cookiebot overlay was not treated as a result.

Do these free checkers click Reject All?

These four did not. Their free pages, as checked on 2026-10-07, do not claim a Reject All recheck. The docs are doc-sourced, not verified by us.

What if the US banner has no Reject All?

Store F showed Reject All on the first layer, and that is the control this capture clicked. If a banner hides Reject All, write down the control that exists. Do not relabel a preference-center confirm as Reject All.

Did Reject All clear cookies on Store F?

No. _ga, _fbp, and cookies for Attentive, Northbeam, Heap, Contentsquare, TVSquared, and Ometria were still there after Reject All. This session did not check whether the values changed.

Is this legal advice?

No. It is not legal advice. Observation is not counsel permission. ConsentProbe does not replace counsel, and it does not install a CMP.

Limits of this page

One US session on Store F, shell exit in Ashburn, Virginia, on October 7, 2026. The browser egress was assumed, not checked on its own. The profile was not empty. These notes do not describe Shopify stores in general or every OneTrust setup. California-specific rules were not tested. There is no HAR. Consent Mode parameters were not read. A host absent after the reload was absent in that window only. The four free scans are empty or unfinished screens. The capability table is doc-sourced, not verified by us. It is not legal advice. Observation is not counsel permission. ConsentProbe does not install a CMP. A free US-baseline scan is not an EU or California legal conclusion.

The testing hub picks the next pass.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

Save a US-baseline technical record

After a DIY check, run a free US-baseline scan: one browser visit outside California, with cookies, requests, and screenshots stored as evidence. That visit does not run EU reject/accept or California GPC. EU, California, and Global 2 audits can be purchased from Billing after sign-in.

Free Cookie Scanners After Reject All, Tested | ConsentProbe