Baseline visit Older format: some facts reconstructed, descriptive only

www.walmart.com

Requested addresshttps://www.walmart.com/

Sep 7, 2026, 4:53 AM UTC

Scan report ready for www.walmart.com: 420 recorded request rows.

Comparison ReportOlder format: some facts reconstructed, descriptive only

Brave-list blocking off/on comparison

Recorded final address https://www.walmart.com/ (opens in a new tab)
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.

What this actually means

walmart.com recorded 7 fewer third-party requests in the visit configured for Brave-list blocking.

The visit with no blocking made 420 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 7 fewer third-party requests. The blocker directly stopped 3 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.

2tracking-service entities
403cross-site requests
2third-party cookie records

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Worth checking

Bottom line: this visit has signals 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.

420 requests observed in one controlled visit.

What was checked

Page
https://www.walmart.com/
When
Sep 7, 2026, 4:53 AM 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
Typed a made-up test value into 1 form field in each visit, never submitting the form. 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.

Context

7 requests matched Brave Shields filter lists

7 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 6 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 7 fewer third-party requests, 1 fewer third-party cookie and 2 fewer tracking-related service requests.

Services only seen in the unblocked visit: Criteo and Google. The blocking visit's engine directly blocked 3 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). 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

Worth checking

1 first-party DNS alias matched tracking checks

Of the resolved targets, 1 matched Brave filter lists; those matches do not identify the operators.

The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. These matches do not establish a request's purpose, profiling, or an intent to conceal tracking. A filter-list match alone is not a verified service identity or proof of tracking.

DNS alias: *.www.walmart.com → *.*.*.com.akadns.net (Brave filter-list match; operator unverified).Open domain evidence

Context

Privacy-policy cross-check not established

The page this scan read as the privacy policy held 1,827 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.

Page recorded as the policy: https://www.walmart.com/… (1,827 characters of text); no policy text compared.

Context

Catalogued service domains recorded responses during this visit

Criteo and 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 advertising. This scan could not identify 2 of the 5 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 assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: HUMAN Security.

403 cross-site requests across 5 third-party hosts.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.

1 request to these platforms.Show catalog-matched requests

Not flagged

No Google Analytics observed

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit.

No google-analytics.com or googletagmanager.com requests.Show catalog-matched requests

Context

Third-party cookies were present

2 third-party cookies showed up during the visit.

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary. 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.

21 cookies total in this report.Modest third-party cookies count.

Context

Input-monitoring signal involving a script from another domain

Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain. This scan did not establish the operator of that 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.

Session-recording listener coverage: 112 interaction-listener registrations with https://*.walmartimages.com/ in the registration call chain. Input-monitoring listener coverage: 29 input-listener registrations with https://*.walmartimages.com/ in the registration call chain.

Not flagged

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.

Brave Shields Comparison

No blocking → Brave-list blocking delta

No blocking: 13,541msBrave-list blocking: 13,516msRan first: Brave-list 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): At least one visit did not complete the fingerprint measurement, so no exact cross-visit delta is shown.
  • Ad-pixel deltas (each visit's own evidence still renders below): At least one visit did not complete the pixel measurement, so no exact cross-visit delta is shown.
Requests-21No blocking: 420 · Brave-list blocking: 399
Third-party requests-7No blocking: 403 · Brave-list blocking: 396
Third-party domains-4No blocking: 5 · Brave-list blocking: 1
Cookies-13No blocking: 21 · Brave-list blocking: 8
Third-party cookies-1No blocking: 2 · Brave-list blocking: 1
Storage keys-11No blocking: 15 · Brave-list blocking: 4
Catalog-matched requests-6No blocking: 6 · Brave-list blocking: 0

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.

Cookie and storage count deltas include every observation. Name-level lists show only reviewed names; unreviewed names are not itemized because they can contain identifiers.

Largest per-domain request-count changes

*.www.walmart.comfirst partyNo blocking: 13 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-13
*.px-cloud.netHUMAN Security · security / anti-abuseNo blocking: 4 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-4
*.wal.counlabeled third partyNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
*.walmartimages.comunlabeled third partyNo blocking: 395 · Brave-list blocking: 396Show No blocking requests · Show Brave-list blocking requests+1
www.walmart.comfirst partyNo blocking: 4 · Brave-list blocking: 3Show No blocking requests · Show Brave-list blocking requests-1
*.criteo.comCriteo · advertisingNo blocking: 1 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-1
*.googlesyndication.comGoogle · advertisingNo blocking: 1 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-1

Domains only with Brave-list blocking

No domain changes observed.

Domains only with No blocking

*.www.walmart.comunlabeled · Show No blocking requests13
*.px-cloud.netHUMAN Security · security / anti-abuse · Show No blocking requests4
*.wal.counlabeled · Show No blocking requests2
*.criteo.comCriteo · advertising · Show No blocking requests1
*.googlesyndication.comGoogle · advertising · Show No blocking requests1

Visible cookie names only with Brave-list blocking

No visible cookie-name changes to show; privacy-filtered names are not itemized.

Visible cookie names only with No blocking

No visible cookie-name changes to show; privacy-filtered names are not itemized.

Visible storage keys only with Brave-list blocking

No visible storage-key changes to show; privacy-filtered keys are not itemized.

Visible storage keys only with No blocking

No visible storage-key changes to show; privacy-filtered keys are not itemized.

Entities only with Brave-list blocking

No entity changes observed.

Entities only with No blocking

HUMAN Security1 domain4
Criteo1 domain1
Google1 domain1

Measurement limits

9 conditions affect how this evidence reads

This report

  • 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 "Brave-list 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 page did not reach network idle before the scan window ended.
  • This scan typed a synthetic test value into 1 form field with native form submission blocked. Focus, input and blur handlers may run and send requests. The value is synthetic and is not stored. Observed requests during typing and the following wait are included in the request log. Teardown-only transmissions are not measured.
  • Read the site's privacy policy (https://www.walmart.com/{seg}) 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.

No blocking visit only

  • Resolved 1 first-party subdomain that is a CNAME alias for a third-party tracker (CNAME cloaking), which request-URL matching alone would miss.

Brave-list blocking visit only

  • Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.

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
20260907-62c6f505e07d66dc48e2a5d3c44e6233
Site
www.walmart.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline 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.

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. 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 .