mit.edu recorded 2 fewer third-party requests in the visit configured for Brave-list blocking.
Where this page's requests went
Both visits. One mark is one request row in the retained log.
No blocking
www.mit.edu itself18 requestsrequests that stayed on the site
000000000000000000
Catalogued services1 request1 name: Google 1
0
Hosts the catalog does not name7 requests1 host; the catalog cannot say who operates it
0000000
Brave-list blocking
www.mit.edu itself18 requestsrequests that stayed on the site
000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name6 requests1 host; the catalog cannot say who operates it
000000
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
The visit with no blocking made 26 requests; the visit 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) recorded 2 fewer third-party requests. The blocker directly stopped 2 requests, as many as the net difference: a blocked request can be retried or replaced by another, and counts vary from run to run.
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.
26 requests observed in one controlled visit.
What was checked
Page
https://www.mit.edu/
When
Sep 28, 2026, 3:42 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
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: the typing test.
Context
2 requests matched Brave Shields filter lists
2 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 1 request row in this visit.Show matched requests
Not flagged
Lower values observed across comparable metrics 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 2 fewer third-party requests and 1 fewer tracking-related service request.
Treat this as an observed difference, not a measured blocking rate.Details
Services only seen in the unblocked visit: Google. The blocking visit's engine directly blocked 2 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
Not flagged
Privacy policy read; no checked statement contradicted
The policy's checkable statements did not contradict this visit's evidence (1 of 1 observed tracking company named in the policy).
Only a few kinds of statement are checked automatically, so this is not a reading of the whole policy.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. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped.
Policy at https://www.mit.edu/privacy; 1 checkable statement 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 could not identify 1 of the 2 third-party hosts recorded here, so it cannot say who operates it. That is a limit of identity coverage, not evidence about the site.
8 cross-site requests across 2 third-party hosts.Below the median for third-party domains across the 85 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.
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 Sep 28, 2026, 3:42 PM UTC · 2,859msBrave-list blocking: started Sep 28, 2026, 3:42 PM UTC · 2,436msRan 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.
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.
The synthetic form-input probe did not complete its test, so input-capture conclusions for this visit are incomplete.
Read the site's privacy policy (https://www.mit.edu/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.
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.
2026-09-28T15:42:32.679Z · cut short: the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; 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.
Requests268 third-party
Matched Shields lists2classification reported by this visit; no engine readback recorded
Third-party domains21 distinct catalogued service entity
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
www.googletagmanager.com
service
1
Google: analytics / tag management
script
*.typekit.net
third-party
7
No catalog match
stylesheet, font
www.mit.edu
first-party
18
No catalog match
document, stylesheet, image, script, xhr
Request log
26 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
50ms
200
document
www.mit.edu
Not attributed
https://www.mit.edu/
B:R0002
167ms
200
stylesheet
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0003
168ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0004
168ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0005
216ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0006
248ms
200
stylesheet
*.typekit.net
initiated by www.mit.edu
https://*.typekit.net/…
B:R0007
332ms
200
stylesheet
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…
B:R0008
428ms
200
script
www.googletagmanager.com
initiated by www.mit.edu
https://www.googletagmanager.com/…?id
B:R0009
457ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
B:R0010
458ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
B:R0011
458ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
B:R0012
459ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
B:R0013
460ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
B:R0014
463ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0015
463ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0016
463ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0017
464ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0018
465ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0019
466ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0020
538ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0021
539ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0022
540ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0023
540ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0024
569ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0025
576ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
B:R0026
581ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
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 not observed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
8
Not attributable
0
Third-party requests
8
8 third-party requests: 8 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
6 requests to *.typekit.net, recorded as initiated by *.typekit.net.
1 request to *.typekit.net, recorded as initiated by www.mit.edu.
1 request to Google, a catalogued service, recorded as initiated by www.mit.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 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.
Automated Chromium scan using Playwright 1.63.0 from github-actions-ubuntu with browser 153.0.8010.12, 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.3-request-method-v1-playwright-1.63.0+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-09-28T15:42:35.546Z · cut short: the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; 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.
Requests246 third-party
Blocked by Brave lists2engine blocks reported by this visit; no engine readback recorded
Third-party domains10 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
*.typekit.net
third-party
6
No catalog match
stylesheet, font
www.mit.edu
first-party
18
No catalog match
document, stylesheet, image, script, xhr
Request log
24 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
57ms
200
document
www.mit.edu
Not attributed
https://www.mit.edu/
V:R0002
123ms
200
stylesheet
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0003
124ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0004
125ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0005
166ms
200
stylesheet
*.typekit.net
initiated by www.mit.edu
https://*.typekit.net/…
V:R0006
179ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0007
259ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
V:R0008
260ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
V:R0009
260ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
V:R0010
260ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
V:R0011
261ms
200
font
*.typekit.net
initiated by *.typekit.net
https://*.typekit.net/…?…&v
V:R0012
264ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0013
265ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0014
266ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0015
267ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0016
267ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0017
268ms
200
image
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0018
342ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0019
344ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0020
344ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0021
345ms
200
script
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0022
372ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0023
374ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
V:R0024
388ms
200
xhr
www.mit.edu
initiated by www.mit.edu
https://www.mit.edu/…
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 not observed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
6
Not attributable
0
Third-party requests
6
6 third-party requests: 6 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
5 requests to *.typekit.net, recorded as initiated by *.typekit.net.
1 request to *.typekit.net, recorded as initiated by www.mit.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 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.
Automated Chromium scan using Playwright 1.63.0 from github-actions-ubuntu with browser 153.0.8010.12, 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.3-request-method-v1-playwright-1.63.0+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.
cut short: the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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 synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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.