Site

pbskids.org

Baseline visit
Requested address
https://pbskids.org/
Report ID
20260814-fd78e4369bb6bcf7727879f3fcde77e7
Evidence SHA-256
3f25079d492614e5b51972640757f5cfcf2050c2222a305572ba4a5d66fb1f50
Scanner
playwright-chromium

pbskids.org contacted catalogued Google domains during the visit labeled GPC off.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

GPC off

pbskids.org itself175 requestsrequests that stayed on the site
Catalogued services6 requests2 names: Google 4, Sentry 2
Hosts the catalog does not name0 requestsno other cross-site host on record

GPC on

pbskids.org itself175 requestsrequests that stayed on the site
Catalogued services6 requests2 names: Google 4, Sentry 2
Hosts the catalog does not name0 requestsno other cross-site host on record
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
  • not measured

1 distinct catalogued tracking-service entity recorded responses across 3 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried.

1tracking-service entity
6cross-site requests

Context

Bottom line: this visit has signals, none ranked worth checking

The scan observed signals a non-expert should not have to decode from raw request tables. Some detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.

Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web. Details

The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from this report's cohort, with each percentile card naming its metric-specific measured-site denominator; otherwise it uses fixed reference thresholds. That cohort is drawn from a curated set of popular, mostly commercial sites, not a random sample of the web. The request log, domain table, and methodology remain below for verification.

181 requests observed in one controlled visit.

What was checked

Page
https://pbskids.org/
When
Aug 14, 2026, 7:06 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 scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
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 both visits: fingerprinting and session-recording signals. Each linked card states what was retained.

Context

6 of 180 requests the engine evaluated matched Brave Shields filter lists

6 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 6 request rows in this visit.Show matched requests

Context

This GPC comparison supports no comparable delta

The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.

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.

Context

Privacy policy read; it made no statement this scan can check

None of the statements this scan knows how to check appear in the policy text. As a result, nothing was compared against this visit's evidence (1 of 1 observed tracking company named in the policy). That is a limit of the automated check, not a finding about the site either way.

Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped. Details

Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields.

Policy at https://pbskids.org/privacy; 0 checkable statements matched; 1 of 1 observed tracking company named in the policy.

Context

Catalogued service domains recorded responses during this visit

Google 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 analytics / tag management. This scan identified an operator for every one of the 3 third-party domains recorded here using catalog, consent-platform, reviewed-ownership, and CNAME evidence. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: Sentry.

6 cross-site requests across 3 third-party hosts.Below the median for third-party domains across the 51 sites measured for this metric. Modest distinct tracking-service entities count.Show third-party requests

Context

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google.

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

4 requests to these platforms.Show catalog-matched requests

Not flagged

Google Analytics present, no remarketing signal

Google Analytics was observed, but no DoubleClick remarketing sync appeared in this visit.

This does not prove advertising or remarketing features are off; it means this visit recorded no DoubleClick remarketing sync. Details

Standard analytics collection was observed, without the stats.g.doubleclick.net advertising sync.

Google Analytics host observed; no stats.g.doubleclick.net request.Show catalog-matched requests

Not flagged

No third-party cookies observed

The automated visit did not observe third-party cookies.

This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.

3 cookies total in this report.No third-party cookies observed.

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.

Scan report ready for pbskids.org: 181 recorded request rows.

Comparison Report

pbskids.org

Recorded final address https://pbskids.org/
ShareDownloads the GPC off visit's request CSV, source report and correction context in a ZIP. Follows the evidence switcher below.PDF + evidence (opens in a new tab)Downloads a ZIP containing the PDF for every recorded visit, exact source JSON, correction context and file hashes. The scanner renders it on request.

GPC Comparison

GPC off and GPC on: two visits, no comparable metric delta

GPC off: started Aug 14, 2026, 7:06 PM UTC · 2,955msGPC on: started Aug 14, 2026, 7:06 PM UTC · 3,230msRan first: GPC on
No metric deltas are comparable across these two visits, so none are shown.
  • Request, cookie, and storage deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Catalog-matched request and entity deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Other detector and causal-path deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The pair did not record the fingerprint-heuristics detector's status for both visits, and an unrecorded condition never counts as matching. The baseline visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals.
  • The Shields-number delta (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Fingerprinting deltas (each visit's own evidence still renders below): The GPC off visit did not complete this measurement, so it has no exact count. The GPC on visit did not complete this measurement, so it has no exact count. The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
  • Ad-pixel deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.

Measurement limits

4 conditions affect how this evidence reads

Both visits

  • Each visit in this report is one automated, headless Chromium visit from a fixed en-US / UTC profile, with no scrolling, clicking, or consent interaction. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Counts are a lower bound: trackers that load only after interaction or consent are not observed; Service Workers are blocked, and Web Worker or WebSocket traffic may be incomplete. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled. Cookie and storage figures are an end-of-visit snapshot, with storage keys read from the top frame only.
  • The in-page fingerprint observer could not read one or more frames, so fingerprint-like API calls and heuristics for this visit are incomplete.
  • Read the site's privacy policy (https://pbskids.org/privacy) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.

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
20260814-fd78e4369bb6bcf7727879f3fcde77e7
Site
pbskids.org
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: fingerprinting evidence was censored before completion: the in-page fingerprint observer did not finish (recorded loss count: 1); recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Variant visit

Started
Run quality
cut short: fingerprinting evidence was censored before completion: the in-page fingerprint observer did not finish (recorded loss count: 1); recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

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 .