Hosts the catalog does not name16 requests3 hosts; the catalog cannot say who operates them
0000000000000000
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
7 distinct catalogued tracking-service entities recorded responses across 18 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled GPC off, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script.
Bottom line: this visit has signals 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.
146 requests observed in one controlled visit.
What was checked
Page
Requested https://www.scholastic.com/; both visits landed on https://www.scholastic.com/home
When
Aug 14, 2026, 7:06 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 scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
Interactions
No typing was recorded in either visit. 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. 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.
Worth checking
34 of 140 requests the engine evaluated matched Brave Shields filter lists
34 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 31 request rows in this visit.Show matched requests
Context
This GPC comparison supports no comparable delta
The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.
1 disqualifying condition named by the report's claim policy.
Worth checking
1 first-party DNS alias matched tracking checks
Recorded DNS aliases resolve to catalogued tracking-related services: Adobe.
These matches do not establish a request's purpose, profiling, or an intent to conceal tracking.Details
The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. A filter-list match alone is not a verified service identity or proof of tracking.
DNS alias: *.scholastic.com → *.*.*.*.omtrdc.net (Adobe; catalog match).Open domain evidence
Worth checking
Consent tooling and requests to tracking-service entities appeared before any choice
scholastic.com sent a request to OneTrust, a consent management platform (the tooling that shows cookie banners). The request log included 7 distinct catalogued tracking-related services before the scanner made any consent choice; 7 companies answered.
It does not determine whether any request required consent or whether the site's behavior complied with applicable law.Details
A request to the platform's loader proves the page attempted to fetch consent tooling. An observed response supports delivery, but neither fact proves a banner was visibly shown to this scanner. Banner display can vary by region and visit context. The scanner never clicks a banner in this mode, so this report records requests made before the scanner made a consent choice. More tracking-service entities or requests may appear after "Accept" than this report captures, so the counts here are lower bounds for users who consent.
Consent platform detected via a request to cdn.cookielaw.org.
Opens the request log at its catalog-matched rows, which include requests to the tracking-related services counted here; this visit never clicked the banner.
Context
Tracking companies the privacy policy does not appear to name
LinkedIn, Pinterest and Cloudflare were sent requests during this visit. However, the policy text matched none of the names this scan knows those companies by.
Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation.Details
Named in the policy: Adobe, Google and Meta, plus 1 other.
Policy at https://www.scholastic.com/…; 0 checkable statements matched; 4 of 7 observed tracking companies named in the policy.
Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.
Worth checking
Catalogued service domains recorded responses during this visit
Adobe, LinkedIn and Google, plus 4 others 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 / advertising, social / advertising pixel and analytics / tag management. This scan could not identify 2 of the 18 third-party hosts recorded here, so it cannot say who operates them. 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.
Google Analytics present; a remarketing sync cannot be told from this report
Google Analytics was observed, with requests to DoubleClick hosts whose names this report generalizes. The remarketing sync host is one such name, so the sync cannot be told apart from them.
This report neither shows nor rules out the sync.Details
The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.
This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites.Details
The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.
28 cookies total in this report.At or above the median for third-party cookies across the 51 sites measured for this metric.
Worth checking
Input-monitoring signal involving a third-party script
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.Details
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.
Session-recording listener coverage: 31 interaction-listener registrations with https://assets.adobedtm.com/, https://cdn.cookielaw.org/ and https://cdn.mouseflow.com/, plus 4 others in the registration call chain. Input-monitoring listener coverage: 7 input-listener registrations with https://cdn.cookielaw.org/, https://*.pinimg.com/ and https://static.cloudflareinsights.com/, plus 1 other in the registration call chain. Known session-replay vendor(s): Mouseflow.
Opens this report's request log filtered to Mouseflow; listener registrations are not request rows, so the log cannot show what was observed.
Context
Fingerprint-like browser APIs were called
1 high-entropy API call appeared in the instrumentation log.
These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers.Details
Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.
1 API family recorded.
Domain evidence
20 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 5.4 s
Catalog match
Role
Resource types
www.scholastic.com
93
No catalog match
first-party
document, script, stylesheet, image, xhr, fetch
assets.adobedtm.com
10
Adobe: analytics / advertising
service
script
cdn.cookielaw.org
9
No catalog match
third-party
script, xhr, fetch, image
*.typekit.net
6
No catalog match
third-party
stylesheet, font
*.ads.linkedin.com
4
LinkedIn: social / advertising pixel
service
image, fetch
*.scholastic.com
4
No catalog match
first-party
script, xhr, image
*.pinterest.com
3
Pinterest: social / advertising pixel
service
xhr, fetch, document
*.licdn.com
2
LinkedIn: social / advertising pixel
service
script
www.googletagmanager.com
2
Google: analytics / tag management
service
script
*.facebook.net
2
Meta: social / advertising pixel
service
script
*.pinimg.com
2
No catalog match
third-party
script
static.cloudflareinsights.com
1
Cloudflare: web analytics
service
script
cdn.mouseflow.com
1
Mouseflow: session replay / behavior analytics
service
script
*.demdex.net
1
Adobe: analytics / advertising
service
xhr
*.*.omtrdc.net
1
Adobe: analytics / advertising
service
xhr
www.google-analytics.com
1
Google: analytics / tag management
service
script
analytics.google.com
1
Google: analytics / tag management
service
fetch
*.*.doubleclick.net
1
Google: advertising
service
ping
www.linkedin.com
1
LinkedIn: social / advertising pixel
service
image
*.onetrust.com
1
No catalog match
third-party
xhr
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.
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.
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.
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 .