Site Behavior Lab
Site

www.homedepot.com

Baseline visit
Requested address
https://www.homedepot.com/
Report ID
20260727-4006618d80dc779268592042b119010e
Evidence SHA-256
fe3b18d1778bb8e62ee0e106737af22ca9dfbc4a4fe04e901d369b352d179c2c
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-005

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.

SBL-CORR-2026-005: In these reports the privacy-policy cross-check read a privacy hub, a page that links to the site's policy without containing it, as the policy itself. Company names were matched only against that page, so the card listing tracking companies the policy does not appear to name is not evidence that the policy omits them, and the policy may name them. Requests and other observations are unaffected. Consult all clarification events for this report.

SBL-CORR-2026-004: Two Brave-list blocking comparisons published two hosting tenant names each under a shared provider suffix, and the names encoded the scanner's egress address, a visit timestamp and per-visit tokens. Redaction now generalizes such names. Redacted copies are published under new report IDs and the originals are removed. Each copy merges the generalized hosts into one domain row, so its unblocked run counts one fewer third-party domain. Every earlier event about an original applies to its copy.

This report is the redacted replacement for 20260727-f378d41658184b8e1b014ae2e41b8541, which was removed for privacy and has no page. Correction events recorded against that report apply to this one.

Read the public review record

homedepot.com's observed Meta Pixel requests contained populated identifier fields.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

No blocking

www.homedepot.com itself42 requestsrequests that stayed on the site
Catalogued services58 requests7 names: Quantum Metric 25, Google 22, New Relic 5, Adobe 2, Meta 2, and 2 more
Hosts the catalog does not name249 requests27 hosts; the catalog cannot say who operates them

Brave-list blocking

www.homedepot.com itself21 requestsrequests that stayed on the site
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name146 requests9 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

An advertising pixel on homedepot.com attached populated fields that the platform designates for personal identifiers (external ID) to observed requests. The scanner records only that they were filled, never their values, so their contents, hashing, successful delivery, and eventual use are not verified. In the visit labeled No blocking, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script and 4 browser-fingerprinting heuristics matched. SBL-CORR-2026-005: In these reports the privacy-policy cross-check read a privacy hub, a page that links to the site's policy without containing it, as the policy itself. Company names were matched only against that page, so the card listing tracking companies the policy does not appear to name is not evidence that the policy omits them, and the policy may name them. Requests and other observations are unaffected. Consult all clarification events for this report.

6tracking-service entities
307cross-site requests
14third-party cookie records
≥4fingerprint-like patterns retained

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

349 requests observed in one controlled visit.

What was checked

Page
https://www.homedepot.com/
When
Jul 27, 2026, 9:58 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 2 form fields in each visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the No blocking visit 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 the No blocking visit only: CNAME cloaking, the privacy policy check, advertising pixels, session-recording signals, fingerprinting, the typing test and the consent banner. Each linked card states what was retained.

Worth checking

142 requests matched Brave Shields filter lists

142 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 58 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 161 fewer third-party requests, 14 fewer third-party cookies and 53 fewer tracking-related service requests.

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

Services only seen in the unblocked visit: Quantum Metric, Google and Adobe, plus 3 others. The blocking visit's engine directly blocked 37 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

2 first-party DNS aliases matched tracking checks

Recorded DNS aliases resolve to catalogued tracking-related services: Adobe. Of the resolved targets, 1 matched Brave filter lists; those matches do not identify the operators.

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: *.homedepot.com → *.online-metrix.net (Brave filter-list match; operator unverified). DNS alias: *.homedepot.com → *.*.*.*.*.omtrdc.net (Adobe; catalog match).Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

Quantum Metric, Google and Adobe, plus 3 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.

Policy at https://www.homedepot.com/privacy/…; 0 checkable statements matched; 0 of 6 observed tracking companies named in the policy.

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.

Worth checking

Catalogued service domains recorded responses during this visit

Quantum Metric, Google and Adobe, plus 3 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 session replay / product analytics, advertising and analytics / tag management. This scan could not identify 26 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. Catalog labels include session-replay or behavior-analytics services: Quantum Metric. The domain match alone does not prove that a recording occurred. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: New Relic.

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

Worth checking

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google, Meta and Microsoft, plus 1 other.

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

26 requests to these platforms.Show catalog-matched requests

Worth checking

Advertising pixels carried populated identifier fields

Meta Pixel attached populated personal-identifier fields (external ID) to requests observed in this visit.

The scanner records their categories, never their values, so their contents, hashing, successful delivery, and eventual use are not verified. Details

Recognized identifier fields held non-empty values. Event labels do not establish that the corresponding user action occurred.

Meta Pixel: custom event and PageView; identifiers external ID (2 requests).Show catalog-matched requests

Context

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.

Google Analytics host observed; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Worth checking

Third-party cookies were present

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

59 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 51 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.

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: 22 interaction-listener registrations with https://assets.thdstatic.com/, https://cdn.quantummetric.com/ and https://*.newrelic.com/, plus 3 others in the registration call chain. Input-monitoring listener coverage: 4 input-listener registrations with https://assets.thdstatic.com/, https://*.newrelic.com/ and https://*.go-mpulse.net/, plus 1 other in the registration call chain. Known session-replay vendor(s): Quantum Metric.

Look closer

Show requests to Quantum Metric

Opens this report's request log filtered to Quantum Metric; listener registrations are not request rows, so the log cannot show what was observed.

Worth checking

Behavioral fingerprinting heuristics matched

At least 4 behavioral heuristics matched in retained evidence: Offline audio rendering heuristic, Canvas fingerprinting heuristic, Canvas font probing heuristic and WebRTC peer-connection probing.

They are review prompts for this visit, not proof of cross-site identity tracking. Details

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.

Offline audio rendering heuristic: 2 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 2 others. Canvas fingerprinting heuristic: 1 canvas matched; reads: canvas.toDataURL. Canvas font probing heuristic: 12 measureText calls across up to 12 fonts; measured text contents are not stored. WebRTC peer-connection probing: 2 peer connections with 2 data channels, 2 offers, and 2 local descriptions.

Domain evidence

46 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 16.4 sCatalog matchRoleResource types
assets.thdstatic.com79No catalog matchthird-partyfont, stylesheet, script, image, other
images.thdstatic.com39No catalog matchthird-partyimage
*.quantummetric.com24Quantum Metric: session replay / product analyticsservicefetch, ping
*.homedepot.com23No catalog matchfirst-partyscript, fetch, xhr, image, ping, document
*.sprinklr.com22No catalog matchthird-partyscript, xhr, image
*.thdstatic.com19No catalog matchthird-partyimage
*.qualtrics.com19No catalog matchthird-partyscript, xhr
*.px-cloud.net17No catalog matchthird-partyscript, xhr, ping
www.homedepot.com17No catalog matchfirst-partydocument, script, xhr, fetch
www.google.com15No catalog matchthird-partyfetch, image
*.*.doubleclick.net7Google: advertisingserviceping, script, document, fetch
*.getamigo.io6No catalog matchthird-partyscript, fetch
*.forter.com6No catalog matchthird-partyxhr, ping
*.nr-data.net4New Relic: performance monitoringservicexhr, ping
www.googletagmanager.com4Google: analytics / tag managementservicescript
ad.doubleclick.net4Google: advertisingservicefetch, image
*.online-metrix.net3No catalog matchthird-partydocument, script, image
*.cdn.forter.com3No catalog matchthird-partyping
*.akstat.io3No catalog matchthird-partyping
*.demdex.net2Adobe: analytics / advertisingservicefetch, xhr
*.doubleclick.net2Google: advertisingservicescript
www.facebook.com2Meta: social / advertising pixelserviceimage
analytics.google.com2Google: analytics / tag managementservicefetch
*.go-mpulse.net2No catalog matchthird-partyscript, xhr
*.agkn.com2No catalog matchthird-partyimage, xhr
*.akamaihd.net2No catalog matchthird-partyxhr
*.*.*.homedepot.com2No catalog matchfirst-partyfetch, xhr
cdn.quantummetric.com1Quantum Metric: session replay / product analyticsservicescript
*.newrelic.com1New Relic: performance monitoringservicescript
*.bing.com1Microsoft: advertising / analyticsserviceimage

+16 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
20260727-4006618d80dc779268592042b119010e
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 in-page fingerprint observer could not read every frame, so the fingerprinting 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
complete; 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. 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 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 .