The log of the stanford.edu visit labeled No blocking, which included a typing test, lists 2 cross-site hosts that the service catalog did not classify as tracking.
Where this page's requests went
Both visits. One mark is one request row in the retained log.
No blocking
*.stanford.edu itself17 requestsrequests that stayed on the site
00000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name3 requests2 hosts; the catalog cannot say who operates them
000
Brave-list blocking
*.stanford.edu itself17 requestsrequests that stayed on the site
00000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name3 requests2 hosts; the catalog cannot say who operates them
000
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
one request on record, same site
one request on record, cross-site
not measured
3 cross-site requests appeared in the log. This report does not record which requests came during the typing test. The identity map named 2 of 2 hosts; an unmatched host is a catalog limit, not evidence that it is harmless.
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.
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.
20 requests observed in one controlled visit.
What was checked
Page
https://*.stanford.edu/
When
Nov 18, 2026, 5:39 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
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.
What these visits could not see
Other pages on this site. Only the requested page's 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.
Not flagged
No requests matched Brave Shields filter lists
No requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser.
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 0 request rows in this visit.Show matched requests
Low signal
No change observed in the Brave-list blocking attempt
The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed no change in the comparable metrics (third-party requests, third-party cookies and tracking-related service requests).
Treat this as no observed difference for this pair of visits, not evidence that blocking removes nothing.Details
The blocking visit's engine directly blocked 0 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).
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Context
Other third-party operators were identified outside the tracking-service catalog
Google was named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as a tracking service.
Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking.Details
This scan identified an operator for every one of the 2 third-party domains recorded here using catalog, consent-platform, reviewed-ownership, and CNAME evidence.
3 cross-site requests across 2 third-party hosts. This report does not record which requests came during the typing test.Below the median for third-party domains across the 74 sites measured for this metric.Show third-party requests
Context
Requests were dispatched to major-platform domains the catalog does not carry
This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.
Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload.Details
These domains are not counted as catalog-matched requests.
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.
0 cookies total in this report.No third-party cookies observed.
Not flagged
No fingerprint-like API calls observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
0 API families recorded.
Scan report ready for *.stanford.edu: 20 recorded request rows.
Comparison ReportOlder format: some facts reconstructed, descriptive only
Brave-list blocking off/on comparison
Recorded final addresshttps://*.stanford.edu/
ShareDownloads the No blocking 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.
Brave Shields Comparison
No blocking → Brave-list blocking delta
No blocking: started Nov 18, 2026, 5:39 PM UTC · 3,609msBrave-list blocking: started Nov 18, 2026, 5:39 PM UTC · 3,647msRan first: No blocking
Some deltas are not comparable across these two visits and are not shown.
Other detector and causal-path deltas (each visit's own evidence still renders below): v1 never recorded detector versions, so fingerprinting and pixel deltas cannot be proven to come from matching instrumentation.
The Shields-number delta (each visit's own evidence still renders below): The two visits measured different Shields quantities (filter-list matches vs engine-blocked requests), which must never share a delta.
Fingerprinting deltas (each visit's own evidence still renders below): v1 never recorded detector versions, so fingerprinting and pixel deltas cannot be proven to come from matching instrumentation.
Ad-pixel deltas (each visit's own evidence still renders below): The record of the No blocking visit does not hold this measurement. The record of the Brave-list blocking visit does not hold this measurement.
Every signed change is Brave-list blocking minus No blocking. A positive or negative direction is descriptive, not a judgment that the result is better or worse.
Largest per-domain request-count changes
No per-domain request counts changed between these visits.
Domains only with Brave-list blocking
No domain changes observed.
Domains only with No blocking
No domain changes observed.
Cookies only with Brave-list blocking
No cookie changes observed.
Cookies only with No blocking
No cookie changes observed.
Storage keys only with Brave-list blocking
No storage key changes observed.
Storage keys only with No blocking
No storage key changes observed.
Entities only with Brave-list blocking
No entity changes observed.
Entities only with No blocking
No entity changes observed.
Measurement limits
6 conditions affect how this evidence reads
This report
Brave-list blocking comparison runs should be collected under matched crawl conditions, and the blocking run is a simulation with Brave's engine and default lists in this scanner's browser, not a live Brave visit. Differences can still reflect timing, experiments, cache state, consent state, or bot detection.
The two visits ran in randomized order; the "No blocking" visit ran first.
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.
This scan typed a synthetic test value into 1 form field with native form submission blocked. Focus, input and blur handlers may run and send requests. The value is synthetic and is not stored. Observed requests during typing and the following wait are included in the request log. Teardown-only transmissions are not measured.
Brave-list blocking visit only
Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.
How to use this report
Read the findings and measurement limits first, then inspect the evidence for each recorded visit. Comparisons include both visits, even where a difference cannot be interpreted.
Keep this PDF with its evidence package: the source JSON, correction context, export receipt and SHA256SUMS. The package preserves source bytes and the correction context at export time. Hashes check file consistency; they do not establish independent measurement accuracy or a signed attestation.
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
*.gstatic.com
third-party
2
No catalog match
font
fonts.googleapis.com
third-party
1
No catalog match
stylesheet
*.stanford.edu
first-party
17
No catalog match
document, stylesheet, script, image, font
Request log
20 recorded requests
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Status
Type
Domain
Provenance
URL
B:R0001
62ms
200
document
*.stanford.edu
Not attributed
https://*.stanford.edu/
B:R0002
181ms
200
stylesheet
fonts.googleapis.com
initiated by *.stanford.edu
https://fonts.googleapis.com/…?…
B:R0003
182ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0004
182ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0005
182ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0006
183ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0007
183ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0008
183ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0009
185ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0010
185ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0011
186ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0012
186ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0013
318ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0014
360ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0015
361ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0016
361ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0017
362ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0018
362ms
200
font
*.gstatic.com
initiated by fonts.googleapis.com
https://*.gstatic.com/…
B:R0019
363ms
200
font
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
B:R0020
363ms
200
font
*.gstatic.com
initiated by fonts.googleapis.com
https://*.gstatic.com/…
Request attribution map
Which actor each third-party request is attributed to, from the initiator the browser reported. Attribution, not causation: an initiator may itself have been told what to fetch, a script that wraps fetch or XHR is credited with the requests it relays, and a script can choose the name it is credited under. Requests made by dedicated workers are recorded and counted, but the browser reports no initiator for them, so they are not attributed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
3
Not attributable
0
Third-party requests
3
3 third-party requests: 3 attributed to a single recorded actor, 0 not attributable.
Horizontally scrollable visual map. A text list of every relationship drawn in it follows.
Select a relationship to see its detail and open the rows behind it.
Relationships shown in the request attribution map
2 requests to *.gstatic.com, recorded as initiated by fonts.googleapis.com.
1 request to fonts.googleapis.com, recorded as initiated by *.stanford.edu.
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 98 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.
Automated Chromium scan using Playwright 1.65.1 from github-actions-ubuntu with browser 159.0.8154.6, timezone UTC, locale en-US, the listed viewport, and Brave Shields classification only. Brave-list matching uses each route-evaluated request's initiating document (the parent document for a subframe navigation), under methodology shields-request-context-v2-adblock-rust-0.13.5-request-method-v1-playwright-1.65.1+subject-validity-v4+detector-coverage-v2+fingerprint-surface-v2; main-frame navigations are not blocked or counted as matches, and redirect follow-up URLs that Playwright does not re-route are not independently evaluated. Treat results as reproducible evidence for this scan configuration, not a universal claim about all visitors.
Brave-list blocking: evidence
2026-11-18T17:39:51.096Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests203 third-party
Blocked by Brave lists0engine blocks reported by this visit; no engine readback recorded
Third-party domains20 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
*.gstatic.com
third-party
2
No catalog match
font
fonts.googleapis.com
third-party
1
No catalog match
stylesheet
*.stanford.edu
first-party
17
No catalog match
document, stylesheet, script, image, font
Request log
20 recorded requests
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Status
Type
Domain
Provenance
URL
V:R0001
73ms
200
document
*.stanford.edu
Not attributed
https://*.stanford.edu/
V:R0002
228ms
200
stylesheet
fonts.googleapis.com
initiated by *.stanford.edu
https://fonts.googleapis.com/…?…
V:R0003
229ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0004
229ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0005
230ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0006
231ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0007
232ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0008
232ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0009
232ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0010
233ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0011
233ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0012
233ms
200
script
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0013
367ms
200
stylesheet
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0014
409ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0015
410ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0016
410ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0017
411ms
200
image
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0018
411ms
200
font
*.gstatic.com
initiated by fonts.googleapis.com
https://*.gstatic.com/…
V:R0019
411ms
200
font
*.stanford.edu
initiated by *.stanford.edu
https://*.stanford.edu/…
V:R0020
413ms
200
font
*.gstatic.com
initiated by fonts.googleapis.com
https://*.gstatic.com/…
Request attribution map
Which actor each third-party request is attributed to, from the initiator the browser reported. Attribution, not causation: an initiator may itself have been told what to fetch, a script that wraps fetch or XHR is credited with the requests it relays, and a script can choose the name it is credited under. Requests made by dedicated workers are recorded and counted, but the browser reports no initiator for them, so they are not attributed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
3
Not attributable
0
Third-party requests
3
3 third-party requests: 3 attributed to a single recorded actor, 0 not attributable.
Horizontally scrollable visual map. A text list of every relationship drawn in it follows.
Select a relationship to see its detail and open the rows behind it.
Relationships shown in the request attribution map
2 requests to *.gstatic.com, recorded as initiated by fonts.googleapis.com.
1 request to fonts.googleapis.com, recorded as initiated by *.stanford.edu.
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 98 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.
Automated Chromium scan using Playwright 1.65.1 from github-actions-ubuntu with browser 159.0.8154.6, timezone UTC, locale en-US, the listed viewport, and Brave Shields block simulation. Brave-list matching uses each route-evaluated request's initiating document (the parent document for a subframe navigation), under methodology shields-request-context-v2-adblock-rust-0.13.5-request-method-v1-playwright-1.65.1+subject-validity-v4+detector-coverage-v2+fingerprint-surface-v2; main-frame navigations are not blocked or counted as matches, and redirect follow-up URLs that Playwright does not re-route are not independently evaluated. Treat results as reproducible evidence for this scan configuration, not a universal claim about all visitors.
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.
Exact build and instrument digests were not recorded by this legacy schema.
Variant visit
Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
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 .
Reports record one automated visit per condition; visits may be incomplete. On restart-safe deployments, an interrupted visit may be retried; attempts are never merged. Results describe these visits, not everything a site can do.