Baseline visit v1 schema · facts legacy-derived · descriptive report

www.homedepot.com

Requested addresshttps://www.homedepot.com/

Jul 21, 2026, 9:26 PM UTC

cut short: the Worker instrumentation could not record every request, so the request evidence is incomplete; derived from status and warnings

Public corrections ledger · SBL-CORR-2026-001

This report has a reviewed clarification

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

Read the public review record

Evidence quality

This report is built on an incomplete visit

Incomplete evidence: evidence was cut short before completion (the Worker instrumentation could not record every request, so the request evidence is incomplete). Counts for the affected evidence are lower bounds; families that completed carry only their ordinary limits. The evidence receipt states the exact per-visit quality.

Scan report ready for www.homedepot.com: 253 recorded request rows.

Comparison Reportv1 schema · facts legacy-derived · descriptive reportrequest evidence incomplete

Brave-list blocking off/on comparison

Recorded final address https://www.homedepot.com/ (opens in a new tab)

The selected visit did not finish collecting request evidence. Request counts are lower bounds; Run quality records the reason.

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

homedepot.com's retained request log includes catalogued Meta domains.

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

≥3tracking-service entities retained
≥210cross-site requests
6third-party cookie records
3fingerprint-like patterns

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Worth checking

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 activity evidence was also incomplete: request counts are retained lower bounds.

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.

at least 253 retained requests observed in one controlled visit.

Worth checking

at least 86 retained requests matched Brave Shields filter lists

at least 86 retained 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 at least 26 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete. and The "Brave-list blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete.

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.

2 disqualifying conditions named by the report's claim policy.Show matched requests

Worth checking

2 first-party DNS aliases matched tracking checks

Recorded DNS aliases resolve to catalogued tracking-related services: Adobe. 1 resolved target 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.

{label}.homedepot.com → {label}.online-metrix.net (Brave filter-list match; operator unverified) and {label}.homedepot.com → {label}.{label}.{label}.{label}.{label}.omtrdc.net (Adobe; catalog match)Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

Quantum Metric, Adobe and Meta were sent requests during this visit, but 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.

Policy at https://www.homedepot.com/privacy/{seg}; 0 checkable statements matched; 0 of 3 observed tracking companies named in the policy.

Worth checking

Catalogued service domains recorded responses during this visit

Quantum Metric, Adobe and Meta 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 session replay / product analytics, analytics / advertising and social / advertising pixel. This scan could not identify 17 of the 21 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: Quantum Metric; the domain match alone does not prove that a recording occurred.

at least 210 retained cross-site requests across at least 21 retained third-party hosts.Show third-party requests

Context

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Meta.

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

at least 1 retained request to these platforms.Show catalog-matched requests

Context

Advertising pixel requests contained event labels

Meta Pixel requests contained event labels during this visit.

Pixel decoding was incomplete for one or more request bodies, so whether other pixel requests carried advanced-matching identifier fields is unknown. Retained labels describe request contents, not verified user actions or successful delivery.

Meta Pixel: PageView (1 request)Show catalog-matched requests

Context

Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

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

Worth checking

Third-party cookies were present

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

45 cookies total in this report.

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

149 interaction-listener registrations with https://*.*.forter.com/, https://assets.thdstatic.com/ and https://cdn.quantummetric.com/, plus 3 others in the registration call chain, 38 input-listener registrations with https://*.*.forter.com/, https://assets.thdstatic.com/ and https://cdn.quantummetric.com/, plus 3 others in the registration call chain and known session-replay vendor(s): Quantum Metric

Worth checking

Behavioral fingerprinting heuristics matched

3 behavioral heuristics matched: Offline audio rendering heuristic, Canvas fingerprinting heuristic and WebRTC peer-connection probing.

These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup. They are review prompts for this visit, not proof of cross-site identity tracking.

2 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 1 other, 1 canvas matched; reads: canvas.toDataURL and 2 peer connections with 2 data channels, 2 offers, and 2 local descriptions

Brave Shields Comparison

No blocking and Brave-list blocking: two visits, no comparable metric delta

No blocking: 15,330msBrave-list blocking: 15,246ms
These two visits do not support a side-by-side comparison, so no deltas are shown.
  • The "No blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete.
  • The "Brave-list blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete.

Each visit's own evidence still stands: use the “Evidence shown” switcher below to inspect either visit's tables, and both visits are in the downloaded JSON.

Measurement limits

10 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 "No 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 2 form fields (never submitting the form) to test whether typed input is captured and sent to third parties. The value is synthetic and is not stored. Requests the page sent during and after this typing, including any unload beacons, are part of the recorded request log and counts.
  • Read the site's privacy policy (https://www.homedepot.com/privacy/{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.
  • The scan blocked or could not verify one or more Web Workers while applying the simulated GPC signal; request evidence may be incomplete.

No blocking visit only

  • Resolved 2 first-party subdomains that are CNAME aliases for third-party trackers (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
20260721-ed4bf497fcb34e415aa0ee058e4f5e64
Site
www.homedepot.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the Worker instrumentation could not record every request, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
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 Worker instrumentation could not record every request, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
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 .