Site Behavior Lab
Site

www.foxnews.com

Baseline visit
Requested address
https://www.foxnews.com/
Report ID
20261118-4729d25fd3c58559fe233f52fce94355
Evidence SHA-256
0bc1e9d8ef8b38daf1e2bc05c13e2aae09d59aea86f3493b07fd49261a64ec9c
Scanner
playwright-chromium

foxnews.com recorded 75 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.foxnews.com itself140 requestsrequests that stayed on the site
Catalogued services55 requests11 names: Taboola 15, Chartbeat 9, Nielsen 8, Amazon Ads 5, Criteo 5, and 6 more
Hosts the catalog does not name58 requests25 hosts; the catalog cannot say who operates them

Brave-list blocking

www.foxnews.com itself138 requestsrequests that stayed on the site
Catalogued services2 requests2 names: Amazon Ads 1, Twilio Segment 1
Hosts the catalog does not name36 requests11 hosts; the catalog cannot say who operates them
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 253 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 75 fewer third-party requests. The blocker directly stopped 38 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.

10tracking-service entities
113cross-site requests
12third-party cookie records

Review-worthy

Bottom line: this visit has review-worthy signals

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.

253 requests observed in one controlled visit.

What was checked

Page
https://www.foxnews.com/
When
Nov 18, 2026, 6:11 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: CNAME cloaking, the privacy policy check, fingerprinting, session-recording signals, the typing test, advertising pixels and the consent banner. Each linked card states what was retained.

Worth checking

74 requests matched Brave Shields filter lists

74 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 55 request rows 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 75 fewer third-party requests, 11 fewer third-party cookies and 52 fewer tracking-related service requests.

Treat this as an observed difference, not a measured blocking rate. Details

Services only seen in the unblocked visit: Taboola, Chartbeat and Nielsen, plus 5 others. The blocking visit's engine directly blocked 38 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).

Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests

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: *.foxnews.com → *.*.*.*.*.omtrdc.net (Adobe; catalog match).Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

Taboola, Chartbeat and Criteo, plus 2 others 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: Nielsen, Microsoft and Google.

Policy at https://www.foxnews.com/privacy-policy; 0 checkable statements matched; 3 of 8 observed tracking companies named in the policy. Policy mentions of Amazon Ads and Twilio Segment are unknown because the historical alias matcher was incomplete.

Look closer

Show catalog-matched requests

Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.

Review-worthy

Catalogued service domains recorded responses during this visit

Taboola, Chartbeat and Nielsen, plus 7 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 advertising / recommendations, audience analytics and audience measurement. This scan could not identify 21 of the 43 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. The role taxonomy leaves at least one catalog category unclassified for these identified services and assigns none a tracking-related role, so they are not counted as tracking-related. Unclassified service: Braze.

113 cross-site requests across 43 third-party hosts.Show third-party requests

Context

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google and Microsoft.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

5 requests to these platforms.Show catalog-matched requests

Not flagged

Google Tag Manager loaded, no Analytics request recorded

This visit contacted Google Tag Manager, but recorded no request to a Google Analytics collection host and no DoubleClick remarketing sync.

Tag Manager can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here. Details

Tag Manager is a loader.

googletagmanager.com observed; no google-analytics.com, analytics.google.com or stats.g.doubleclick.net request.Show catalog-matched requests

Review-worthy

Third-party cookies were present

12 third-party cookies showed up during the visit.

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.

45 cookies total in this report.At or above the 90th-percentile mark for third-party cookies across the 74 sites measured for this metric.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Context

Fingerprint-like browser APIs were called

At least 782 retained high-entropy API calls appeared in the incomplete 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: canvas.measureText.

Retained incomplete evidence includes 1 API event record; no exact API-family total is available.

Domain evidence

47 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 5.9 sCatalog matchRoleResource types
static.foxnews.com106No catalog matchfirst-partyscript, stylesheet, image, document, xhr
*.foxnews.com30No catalog matchfirst-partyimage, xhr, document, script, fetch
*.imrworldwide.com7Nielsen: audience measurementservicescript, image, document
images.taboola.com7Taboola: advertising / recommendationsserviceimage
*.chartbeat.net6Chartbeat: audience analyticsserviceimage
*.h-cdn.com6No catalog matchthird-partyscript, xhr, stylesheet
*.ketchcdn.com6No catalog matchthird-partyscript, fetch, ping
www.gstatic.com6No catalog matchthird-partyscript, stylesheet, other
www.google.com5No catalog matchthird-partyscript, document
cdn.taboola.com4Taboola: advertising / recommendationsservicescript, image
*.criteo.com4Criteo: advertisingservicescript, document
*.taboola.com4Taboola: advertising / recommendationsservicefetch, ping
*.*.atp.fox4No catalog matchthird-partyfetch, script, xhr
static.trueanthem.com4No catalog matchthird-partyscript
*.amazon-adsystem.com3Amazon Ads: advertisingservicescript, xhr, fetch
*.demdex.net3Adobe: analytics / advertisingservicexhr
*.bing.com3Microsoft: advertising / analyticsservicescript, image
*.scorecardresearch.com3Comscore: audience measurementservicescript, image
commswap.com3No catalog matchthird-partyscript, fetch
*.gstatic.com3No catalog matchthird-partyfont
www.foxnews.com3No catalog matchfirst-partydocument, xhr, script
*.*.amazon-adsystem.com2Amazon Ads: advertisingservicescript
static.chartbeat.com2Chartbeat: audience analyticsservicescript
www.googletagmanager.com2Google: analytics / tag managementservicescript
*.kts.fox2No catalog matchthird-partyscript
cdn.confiant-integrations.net2No catalog matchthird-partyscript
pix.pub2No catalog matchthird-partyimage
*.fontawesome.com2No catalog matchthird-partystylesheet
static.criteo.net1Criteo: advertisingservicescript
cdn.segment.com1Twilio Segment: customer data platformservicescript

+17 more in the evidence explorer below.

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.

Report ID
20261118-4729d25fd3c58559fe233f52fce94355
Site
www.foxnews.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
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 in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
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. A study has been recorded for pixel-events and does not support a published rate under the current build. 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 98 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 .