Site Behavior Lab
Site

www.stanford.edu

Baseline visit
Requested address
https://www.stanford.edu/
Report ID
20260811-7fe47e54eadf2739245744f641182185
Evidence SHA-256
5f6ace4d50b14659baeab4b959a3e77699f64fe49dd66aeb784f823bfbef88ec
Scanner
playwright-chromium

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

stanford.edu contacted catalogued Google domains during the visit labeled No blocking.

Where this page's requests went

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

www.stanford.edu itself36 requestsrequests that stayed on the site
Catalogued services8 requests2 names: Google 6, Contentsquare 2
Hosts the catalog does not name83 requests6 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
  • not measured

2 distinct catalogued tracking-service entities recorded responses across 11 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 a catalogued session-replay service appeared or broad interaction listeners were registered. 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.

2tracking-service entities
91cross-site requests
5third-party cookie records

Worth checking

Bottom line: this visit has signals worth checking

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

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.

127 requests observed in one controlled visit.

What was checked

Page
https://www.stanford.edu/
When
Aug 11, 2026, 4:17 AM 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
Typed a made-up test value into 1 form field in each visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the Brave-list blocking visit 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 Brave-list blocking visit only: Brave Shields matches, the privacy policy check, third-party services, named platforms, Google Analytics remarketing, advertising pixels and the consent banner.

Context

8 requests matched Brave Shields filter lists

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

Context

This Shields comparison is not conclusive

The "Brave-list 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

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 (2 of 2 observed tracking companies 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://www.stanford.edu/privacy; 0 checkable statements matched; 2 of 2 observed tracking companies named in the policy.

Context

Catalogued service domains recorded responses during this visit

Google and Contentsquare 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, advertising and session replay / behavior analytics. This scan could not identify 1 of the 11 third-party hosts recorded here, so it cannot say who operates it. That is a limit of identity coverage, not evidence about the site. Catalog labels include session-replay or behavior-analytics services: Contentsquare. The domain match alone does not prove that a recording occurred.

91 cross-site requests across 11 third-party hosts.At or above the median for third-party domains across the 86 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.

6 requests to these platforms.Show catalog-matched requests

Context

Google Analytics present; a remarketing sync cannot be told from this report

Google Analytics was observed, with requests to DoubleClick hosts whose names this report generalizes. The remarketing sync host is one such name, so the sync cannot be told apart from them.

This report neither shows nor rules out the sync. Details

The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

Google Analytics host observed; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Worth checking

Third-party cookies were present

5 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.

10 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 86 sites measured for this metric.

Context

Session-replay vendor observed

Contentsquare appeared in the request log.

The domain match alone does not prove that a recording occurred. Details

Catalog labels include session-replay or behavior-analytics services: Contentsquare. Treat this card as a review prompt rather than proof.

Known session-replay vendor(s): Contentsquare.

Look closer

Show requests to Contentsquare

Opens this report's request log filtered to Contentsquare; listener registrations are not request rows, so the log cannot show what was observed.

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. Details

Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.

1 API family recorded.

Domain evidence

12 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 13.3 sCatalog matchRoleResource types
*.storyblok.com69No catalog matchthird-partyimage, media
www.stanford.edu36No catalog matchfirst-partydocument, stylesheet, script, font, fetch
www.youtube.com10No catalog matchthird-partydocument, stylesheet, script, image, xhr
*.contentsquare.net2Contentsquare: session replay / behavior analyticsservicescript, xhr
www.google-analytics.com2Google: analytics / tag managementservicefetch
*.*.doubleclick.net2Google: advertisingservicexhr
www.googletagmanager.com1Google: analytics / tag managementservicescript
static.doubleclick.net1Google: advertisingservicescript
*.gstatic.com1No catalog matchthird-partyfont
*.ytimg.com1No catalog matchthird-partyimage
www.google.com1No catalog matchthird-partyscript
jnn-pa.googleapis.com1No catalog matchthird-partyxhr

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
20260811-7fe47e54eadf2739245744f641182185
Site
www.stanford.edu
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
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 scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
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.

Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 99 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.

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 .