Baseline visit
Requested addresshttps://www.khanacademy.org/
Jul 14, 2026, 3:26 AM UTC
complete; recorded by the scanner
Worth checking
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.
Context
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.
Worth checking
In the visit that clicked Reject all, Google answered requests.
The report verified that the site registered Reject all after the click and again after one page reload. The recorded requests span before and after the click, so some can be pre-choice traffic, from vendors the site treats as strictly necessary, or processing claimed under legitimate interest. It is a documented observation to review against the banner's promises, not a violation ruling.
Context
The page this scan read as the privacy policy held 974 characters of text, short enough to be the page before its policy loaded. As a result, no policy text was compared against this visit's evidence. That is a limit of the automated check, not a finding about the site either way.
The scanner that recorded this visit read a policy page a fixed second after it began loading. Some pages render their policy later, and some had requests refused by the scan's own traffic budget. A short read can therefore be the page around a policy that never arrived. Company mentions and policy statements recorded from it are not used; later scanner versions wait for the page to settle and withhold such a read.
Context
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 analytics / tag management. This scan could not identify 3 of the 6 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
Context
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.
Not flagged
Google Analytics was observed, but no DoubleClick remarketing sync appeared in this visit.
Standard analytics collection was observed, without the stats.g.doubleclick.net advertising sync.
Not flagged
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.
Context
Listener coverage that could observe typing-related input events was registered through call chains that included a third-party script.
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. That is 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. The card therefore 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.
Not flagged
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
Raw evidence
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
20260714-ad6a59f306b5ef20da4a0adcfa4eac63shields-request-context-v2-adblock-rust-0.13.0-request-method-v1+phase-kernel-v1+boundary-state-v1+consent-r2-v1+resource-budget-v11961b4197b649b6eb8028f95a9f2f6b28973b7427178b23e661017da7ed0c7c4b7d4991063310a81b56342ca7ad949723e785704326179e1658335d7af2f88cf17d246aca749766d24266f98061bb05f9d88182529285a3472e57045663261a9redaction-v3+allowlists-v2:042fbfccf7b914479b7100002c5f709b54314606840c4dde50fb2368e23c30e8+public-string-policy-v2:74f1170bbf38a2f85629fa612c01f5da3c0ab1d8f0042f4082eef21815db868c+tldts@7.4.3+node-evidence-policy-v1+v3-to-v4-ip-port-title@1shields-request-context-v2-adblock-rust-0.13.0-request-method-v1+phase-kernel-v1+boundary-state-v1+consent-r2-v1+resource-budget-v11961b4197b649b6eb8028f95a9f2f6b28973b7427178b23e661017da7ed0c7c4b7d4991063310a81b56342ca7ad949723e785704326179e1658335d7af2f88cf17d246aca749766d24266f98061bb05f9d88182529285a3472e57045663261a9redaction-v3+allowlists-v2:042fbfccf7b914479b7100002c5f709b54314606840c4dde50fb2368e23c30e8+public-string-policy-v2:74f1170bbf38a2f85629fa612c01f5da3c0ab1d8f0042f4082eef21815db868c+tldts@7.4.3+node-evidence-policy-v1+v3-to-v4-ip-port-title@1Recorded 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. A study has been recorded for pixel-events and does not support a published rate under the current build. 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 .