Baseline visit v1 schema · facts legacy-derived · descriptive report
https://*.stanford.edu/
Sep 7, 2026, 5:18 AM UTC
complete; derived from status and warnings
Scan report ready for *.stanford.edu: 20 recorded request rows.
Comparison Reportv1 schema · facts legacy-derived · descriptive report
Context
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; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.
Nothing observed
No requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser.
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.
Low signal
The blocking visit (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)) showed no change in the comparable metrics (third-party requests, third-party cookies and tracking-related service requests).
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), so treat this as no observed difference for this pair of visits, not evidence that blocking removes nothing.
Context
Google were named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as tracking services.
Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking. 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.
Context
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. These domains are not counted as catalog-matched requests.
Nothing observed
This visit did not contact Google Analytics.
Neither Google Analytics nor its remarketing sync was observed in this visit.
Nothing 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.
Nothing observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
Brave Shields Comparison
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.
No per-domain request counts changed between these visits.
No domain changes observed.
No domain changes observed.
No cookie changes observed.
No cookie changes observed.
No storage key changes observed.
No storage key changes observed.
No entity changes observed.
No entity changes observed.
This report
Both visits
Brave-list blocking visit only
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.
Correction context SHA-256: 1a6acc2ad1147c0255b04d14d2748f411159a9516f818959dd3054be53ed216c
Renderer revision: 3c18992e02534f33c825f7c2e51dd534d3ccab0d
2026-09-07T05:18:22.664Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
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.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.20 requests were recorded from 43 ms to 903 ms. Open the request log for exact timing and request details.
| 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 |
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.
| Ref | Time | Status | Type | Domain | Provenance | URL |
|---|---|---|---|---|---|---|
B:R0001 | 43ms | 200 | document | *.stanford.edu | Not attributed | https://*.stanford.edu/ |
B:R0002 | 382ms | 200 | stylesheet | fonts.googleapis.com | initiated by *.stanford.edu | https://fonts.googleapis.com/…?… |
B:R0003 | 382ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0004 | 382ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0005 | 384ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0006 | 384ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0007 | 384ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0008 | 384ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0009 | 385ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0010 | 385ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0011 | 385ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0012 | 385ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0013 | 838ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0014 | 899ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0015 | 900ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0016 | 900ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0017 | 901ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0018 | 901ms | 200 | font | *.gstatic.com | initiated by fonts.googleapis.com | https://*.gstatic.com/… |
B:R0019 | 903ms | 200 | font | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
B:R0020 | 903ms | 200 | font | *.gstatic.com | initiated by fonts.googleapis.com | https://*.gstatic.com/… |
2026-09-07T05:18:26.928Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
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.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.20 requests were recorded from 44 ms to 906 ms. Open the request log for exact timing and request details.
| 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 |
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.
| Ref | Time | Status | Type | Domain | Provenance | URL |
|---|---|---|---|---|---|---|
V:R0001 | 44ms | 200 | document | *.stanford.edu | Not attributed | https://*.stanford.edu/ |
V:R0002 | 379ms | 200 | stylesheet | fonts.googleapis.com | initiated by *.stanford.edu | https://fonts.googleapis.com/…?… |
V:R0003 | 381ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0004 | 381ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0005 | 381ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0006 | 382ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0007 | 382ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0008 | 382ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0009 | 383ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0010 | 384ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0011 | 384ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0012 | 385ms | 200 | script | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0013 | 799ms | 200 | stylesheet | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0014 | 904ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0015 | 904ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0016 | 905ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0017 | 905ms | 200 | image | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0018 | 905ms | 200 | font | *.gstatic.com | initiated by fonts.googleapis.com | https://*.gstatic.com/… |
V:R0019 | 906ms | 200 | font | *.stanford.edu | initiated by *.stanford.edu | https://*.stanford.edu/… |
V:R0020 | 906ms | 200 | font | *.gstatic.com | initiated by fonts.googleapis.com | https://*.gstatic.com/… |
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
20260907-9260e3c1118f4901acc733b336b9dbf5Recorded 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 .