Site Behavior Lab
Site

www.theguardian.com

Baseline visit
Requested address
https://www.theguardian.com/
Report ID
20260928-e4a1b41f9502c00b71043b0c104e5518
Evidence SHA-256
0936d015444832e4d0980bb16e8f1ea05a9e9b3215245e320c994c16a127b0c5
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-005

This report has a reviewed clarification

SBL-CORR-2026-005: In these reports the privacy-policy cross-check read a privacy hub, a page that links to the site's policy without containing it, as the policy itself. Company names were matched only against that page, so the card listing tracking companies the policy does not appear to name is not evidence that the policy omits them, and the policy may name them. Requests and other observations are unaffected. Consult all clarification events for this report.

Read the public review record

theguardian.com's retained request log includes catalogued Google and LinkedIn domains.

Where this page's requests went

The No blocking visit. One mark is one request row in the retained log.

www.theguardian.com itselfat least 30 retained requestsrequests that stayed on the site
Catalogued servicesat least 257 retained requests21 names: Google 45, PubMatic 42, Magnite 31, Amazon Ads 24, The Trade Desk 20, and 16 more
Hosts the catalog does not nameat least 383 retained requests90 hosts; the catalog cannot say who operates them
Not measuredabsence here is not evidence of absence
  • Other pages on this site
  • Signed-in visitors, other browsers and other regions
  • Anything that loads only after interaction or consent
  • Services the catalog does not name
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • the count is a lower bound; more may exist
  • not measured

Retained request rows include 21 distinct catalogued tracking-service entities; 21 of the retained service matches recorded responses across at least 121 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled No blocking, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script. SBL-CORR-2026-005: In these reports the privacy-policy cross-check read a privacy hub, a page that links to the site's policy without containing it, as the policy itself. Company names were matched only against that page, so the card listing tracking companies the policy does not appear to name is not evidence that the policy omits them, and the policy may name them. Requests and other observations are unaffected. Consult all clarification events for this report.

≥21tracking-service entities retained
≥640cross-site requests
143third-party cookie records

Review-worthy

Bottom line: this visit has review-worthy signals

The scan observed signals a non-expert should not have to decode from raw request tables. Some activity evidence was also incomplete: request counts are retained lower bounds.

This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. Details

The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.

At least 670 retained requests observed in one controlled visit.

What was checked

Page
Requested https://www.theguardian.com/; both visits landed on https://www.theguardian.com/us
When
Sep 28, 2026, 12:00 PM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence was cut short.

What these visits could not see

  • Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its activity was recorded.
  • Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Anything that loads only after interaction or consent. Trackers that load that late are not observed, so counts are a lower bound.
  • Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
  • Checks with incomplete evidence. In the No blocking visit: every check except third-party cookies and storage. In the Brave-list blocking visit: the privacy policy check, session-recording signals, fingerprinting, the typing test, CNAME cloaking, advertising pixels and the consent banner. The cards for the incomplete checks state only what was retained.

Worth checking

At least 335 retained requests matched Brave Shields filter lists

At least 335 retained requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block. Details

Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ.

The hand-curated service catalog separately matched at least 257 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete.

The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.

1 disqualifying condition named by the report's claim policy.Show matched requests

Context

Tracking companies the privacy policy does not appear to name

PubMatic, The Trade Desk and Index Exchange, plus 6 others were sent requests during this visit. However, the policy text matched none of the names this scan knows those companies by.

Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation. Details

Named in the policy: Google and LinkedIn.

Policy at https://www.theguardian.com/…/privacy; 0 checkable statements matched; 2 of 11 observed tracking companies named in the policy. Policy mentions of Magnite, Amazon Ads and Equativ are unknown because the historical alias matcher was incomplete.

Look closer

Show catalog-matched requests

Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.

Review-worthy

Catalogued service domains recorded responses during this visit

Google, PubMatic and Magnite, plus 18 others appeared in the request log.

A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened. Details

Functional catalog labels include advertising, advertising / supply-side platform and advertising / demand-side platform. This scan could not identify 88 of the 121 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

At least 640 retained cross-site requests across at least 121 retained third-party hosts.Show third-party requests

Context

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google and LinkedIn.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

At least 49 retained requests to these platforms.Show catalog-matched requests

Context

Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped

No Google Analytics request appears in the retained evidence.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

Google Analytics was not observed in this visit.

No google-analytics.com, analytics.google.com or googletagmanager.com requests.Show catalog-matched requests

Review-worthy

Third-party cookies were present

143 third-party cookies showed up during the visit.

This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites. Details

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

165 cookies total in this report.

Context

Input-monitoring signal involving a third-party script

Listener coverage that could observe typing-related input events was registered through call chains that included a third-party script.

This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted. Details

Stack attribution records the script origins present in the bounded registration call chain. A cross-site origin in that chain does not by itself establish that the cross-site script registered the listener. That is because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain. The card therefore says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected). Treat this card as a review prompt rather than proof.

Session-recording listener coverage: 53 interaction-listener registrations with https://assets.guim.co.uk/, https://cdn.brandmetrics.com/ and https://cdn.permutive.com/, plus 2 others in the registration call chain. Input-monitoring listener coverage: 14 input-listener registrations with https://assets.guim.co.uk/, https://cdn.brandmetrics.com/ and https://*.*.doubleclick.net/ in the registration call chain.

Look closer

Show requests involving assets.guim.co.uk

Opens this report's request log filtered to assets.guim.co.uk, a script origin recorded in the listener's call chain.

Context

Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped

The retained evidence holds no calls to the instrumented high-entropy browser APIs.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

This is an observation layer, not proof that fingerprinting is impossible.

Retained incomplete evidence includes 0 API event records; no exact API-family total is available.

Domain evidence

123 recorded domains

These are retained domain rows, not a complete inventory.

The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 10.7 sCatalog matchRoleResource types
assets.guim.co.uk68No catalog matchthird-partyother, font, script, stylesheet, document
*.pubmatic.com33PubMatic: advertising / supply-side platformservicefetch, image, xhr, script, document
*.*.doubleclick.net31Google: advertisingservicescript, document, other, image, fetch
*.guim.co.uk27No catalog matchthird-partyimage
*.gumgum.com27No catalog matchthird-partydocument, image
*.theguardian.com25No catalog matchfirst-partyfetch, script, xhr, document, stylesheet
*.amazon-adsystem.com22Amazon Ads: advertisingservicescript, xhr, document, image
*.adsrvr.org20The Trade Desk: advertising / demand-side platformservicefetch, image, document
*.casalemedia.com19Index Exchange: advertising / exchangeservicefetch, document, image
*.rubiconproject.com16Magnite: advertising / supply-side platformservicefetch, document, script, xhr, image
pixel.rubiconproject.com15Magnite: advertising / supply-side platformserviceimage
*.analytics.yahoo.com14No catalog matchthird-partyscript, xhr, document, image
*.openx.net13OpenX: advertising / exchangeservicefetch, document, image
*.3lift.com13TripleLift: advertising / supply-side platformservicefetch, document, image
*.adsafeprotected.com13No catalog matchthird-partyscript, image
api.permutive.com12No catalog matchthird-partyxhr, image
*.the-ozone-project.com12No catalog matchthird-partyfetch, document, xhr, image
*.presage.io12No catalog matchthird-partydocument, image
*.googlesyndication.com11Google: advertisingservicefetch, script, image
*.dotomi.com10No catalog matchthird-partyimage, document
ads.pubmatic.com9PubMatic: advertising / supply-side platformservicescript, document, image
*.smartadserver.com8Equativ: advertising / supply-side platformservicedocument, image
*.bidswitch.net8No catalog matchthird-partyimage, document
*.*.bidr.io7No catalog matchthird-partyimage, document
*.*.stackadapt.com6StackAdapt: advertising / demand-side platformserviceimage, document
*.rlcdn.com6LiveRamp: identity / advertisingserviceimage
*.everesttech.net6No catalog matchthird-partydocument
id5-sync.com5No catalog matchthird-partyfetch, xhr, image
*.adnxs.com5No catalog matchthird-partyxhr, document, image
*.permutive.app5No catalog matchthird-partyxhr

+93 more in the evidence explorer below.

Raw evidence

Open the interactive evidence explorer

The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.

This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.

Report ID
20260928-e4a1b41f9502c00b71043b0c104e5518
Site
www.theguardian.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
cut short: the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.

This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.

Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. How detector accuracy is measured.

Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .