scholastic.com recorded 3 fewer third-party requests in the visit configured for Brave-list blocking.
The visit with no blocking made 103 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 3 fewer third-party requests. The blocker directly stopped 4 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.
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. Where a measured distribution exists, severity ranks this visit against percentiles from the report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort, with each percentile card naming its metric-specific measured-site denominator (among 98 sites with a successful load across all cohorts; other methodologies, request-capped visits, and post-choice consent visits are excluded from this denominator, while failed or block-page attempts are outside that coverage), a curated set of popular, mostly commercial sites, not a random sample of the web, and otherwise uses fixed reference thresholds. The request log, domain table, and methodology remain below for verification.
103 requests observed in one controlled visit.
Context
4 requests matched Brave Shields filter lists
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.
The hand-curated service catalog separately matched 2 request rows in this visit.Show matched requests
Nothing observed
Lower values observed across comparable metrics in the Brave-list blocking attempt
With 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), this paired visit showed 3 fewer third-party requests and 2 fewer tracking-related service requests.
Services only seen in the unblocked visit: Cloudflare and Mouseflow. The blocking visit's engine directly blocked 4 requests; the remaining difference may include follow-on requests that never started once their sources were blocked. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments), so treat this as an observed difference, not a measured blocking rate.
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Context
Tracking companies the privacy policy does not appear to name
Cloudflare was sent requests during this visit, but the policy text matched none of the names this scan knows that company by.
Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation. Named in the policy: Mouseflow.
Policy at https://www.scholastic.com/{seg}/{seg}/{seg}; 0 checkable statements matched; 1 of 2 observed tracking companies named in the policy.
Context
Catalogued service domains recorded responses during this visit
Cloudflare and Mouseflow 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 web analytics and session replay / behavior analytics. This scan could not identify 1 of the 3 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: Mouseflow; the domain match alone does not prove that a recording occurred.
8 cross-site requests across 3 third-party hosts.Below the median for third-party domains across the 88 sites measured for this metric. Modest distinct tracking-service entities count.Show third-party requests
Nothing observed
No requests to major-platform domains were recorded
No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains were observed in this visit.
Major-platform domains were not observed in this single passive visit; interaction-gated requests could still load for real users.
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.
3 cookies total in this report.No third-party cookies observed.
Worth checking
Session-recording signal matched a known vendor
The page registered broad interaction listeners through call chains that included a third-party script, and contacted a known session-replay service.
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, 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, so the card 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.
10 interaction-listener registrations with https://cdn.mouseflow.com/ and https://static.cloudflareinsights.com/ in the registration call chain and known session-replay vendor(s): Mouseflow
Nothing observed
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.
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.
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
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. 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 .