Baseline visit v1 schema · facts legacy-derived · descriptive report

www.youtube.com

https://www.youtube.com/

Jul 27, 2026, 10:03 AM UTC

complete; derived from status and warnings

View site history Scan this exact route again

Public corrections ledger · SBL-CORR-2026-001

This report has a reviewed clarification

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

Read the public review record

What this actually means

youtube.com contacted catalogued services on separate Google domains.

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

8cross-site domains

104cross-site requests

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary

playwright-chromium

Context

Bottom line: this visit has review-worthy signals

The scan observed signals a non-expert should not have to decode from raw request tables.

The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from the report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort, with each percentile card naming its metric-specific measured-site denominator (among 98 sites with a successful load across all cohorts; other methodologies, request-capped visits, and post-choice consent visits are excluded from this denominator, while failed or block-page attempts are outside that coverage), a curated set of popular, mostly commercial sites, not a random sample of the web, and otherwise uses fixed reference thresholds. The request log, domain table, and methodology remain below for verification.

158 requests observed in one controlled visit.

Context

4 requests matched Brave Shields filter lists

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

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. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.

The hand-curated service catalog separately matched 3 request rows in this visit.Show matched requests

Context

Mixed changes observed in the Brave-list blocking attempt

With the scanner configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit; application was not verified), this paired visit showed 2 more third-party requests and 3 fewer tracking-related service requests.

The blocking visit's engine directly blocked 4 requests; ad rotation, experiments, or caching between the two visits can offset or outweigh what blocking removed, which is how totals can hold steady or rise despite direct blocks. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments), so treat this as an observed difference, not a measured blocking rate.

Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests

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. Functional catalog labels include advertising. This scan identified an operator for every one of the 8 third-party domains recorded here using catalog, consent-platform, reviewed-ownership, and CNAME evidence. 2 catalogued cross-site domains belong to the same reviewed Google domain family as the site, so that traffic is not evidence of disclosure to an outside company.

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

Context

Major-platform domains matched within the site's reviewed organization

Google domains appeared across a registrable-domain boundary, but the reviewed ownership map groups them with the site rather than an outside company.

Cross-registrable-domain traffic remains counted in the report, but this reviewed ownership relationship does not support an outside-recipient disclosure claim. Naming the operator also does not prove request purpose.

104 cross-site requests mapped to a reviewed same-organization domain family.Show catalog-matched requests

Nothing observed

No Google Analytics observed

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit.

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

Nothing observed

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.

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

Context

Input-monitoring signal involving a script from another domain

Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain, whose operator this scan did not establish.

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. 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, 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, so the card 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.

18 interaction-listener registrations with https://www.google.com/ in the registration call chain and 6 input-listener registrations with https://www.google.com/ in the registration call chain

Context

Fingerprint-like browser APIs were called

1 high-entropy API call appeared in the instrumentation log.

These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers. Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.

1 API family recorded.

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.

Integrity and provenance

Evidence receipt

Open report JSON Download corrections with this JSON Open provenance sidecar Printable version Download PDF + evidence Open PDF

Report ID: 20260727-edd2056041c853e7610b1ba3d9f52cb2
Site: www.youtube.com
Latest visit: Jul 27, 2026, 10:03 AM UTC
Schema: v1 schema · facts legacy-derived · descriptive report

Verify recorded provenance

Baseline visit

Started: Jul 27, 2026, 10:03 AM UTC
Run quality: complete; derived from status and warnings
Scanner: playwright-chromium
Browser: 149.0.7827.55
Redaction: not recorded by this schema
Provenance: Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started: Jul 27, 2026, 10:03 AM UTC
Run quality: complete; derived from status and warnings
Scanner: playwright-chromium
Browser: 149.0.7827.55
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. 16 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 13 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 2026-08-02.