Site Behavior Lab
Site

homedepot.com

Baseline visit
Requested address
https://www.homedepot.com/
Report ID
20260814-0d43cea9be32d1d52650401b4661cce3
Evidence SHA-256
b23869d5eff646b0738b9465aeada787703906a0a2c1f40d0bd4ae48f904b234
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.

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.

GPC off

homedepot.com itself36 requestsrequests that stayed on the site
Catalogued services55 requests7 names: Google 20, Quantum Metric 16, HUMAN Security 13, Adobe 2, Meta 2, and 2 more
Hosts the catalog does not name247 requests21 hosts; the catalog cannot say who operates them

GPC on

homedepot.com itselfat least 36 retained requestsrequests that stayed on the site
Catalogued servicesat least 26 retained requests5 names: Quantum Metric 14, HUMAN Security 6, New Relic 3, Adobe 2, Meta 1
Hosts the catalog does not nameat least 228 retained requests16 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
  • the count is a lower bound; more may exist
  • 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 GPC off, 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
302cross-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.

338 requests observed in one controlled visit.

What was checked

Page
https://www.homedepot.com/
When
Aug 14, 2026, 7:15 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
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, 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: session-recording signals, fingerprinting and the typing test. In the GPC on visit only: Brave Shields matches, the privacy policy check, third-party services, named platforms, advertising pixels, Google Analytics remarketing and the consent banner. Each linked card states what was retained.

Worth checking

115 of 290 requests the engine evaluated matched Brave Shields filter lists

115 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

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 variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals.

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.

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

Google, Quantum Metric 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

Google, Quantum Metric 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 advertising, analytics / tag management and session replay / product analytics. This scan could not identify 20 of the 36 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: HUMAN Security.

302 cross-site requests across 36 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.

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

55 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: 174 interaction-listener registrations with https://*.*.forter.com/, https://assets.thdstatic.com/ and https://cdn.quantummetric.com/, plus 5 others in the registration call chain. Input-monitoring listener coverage: 42 input-listener registrations with https://*.*.forter.com/, https://assets.thdstatic.com/ and https://cdn.quantummetric.com/, plus 4 others 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: 10 measureText calls across up to 10 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

38 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 16.2 sCatalog matchRoleResource types
assets.thdstatic.com80No catalog matchthird-partyfont, stylesheet, script, image, other
images.thdstatic.com44No catalog matchthird-partyimage
*.qualtrics.com37No catalog matchthird-partyscript, xhr, image
*.thdstatic.com23No catalog matchthird-partyimage
*.homedepot.com23No catalog matchfirst-partyscript, fetch, xhr, image, document, ping
*.sprinklr.com20No catalog matchthird-partyscript, xhr, image
*.quantummetric.com15Quantum Metric: session replay / product analyticsservicefetch
*.px-cloud.net13HUMAN Security: security / anti-abuseservicescript, xhr
www.google.com13No catalog matchthird-partyfetch, image
www.homedepot.com13No catalog matchfirst-partydocument, script, xhr, fetch
*.*.doubleclick.net7Google: advertisingserviceping, script, document, fetch
*.forter.com6No catalog matchthird-partyxhr, ping
*.getamigo.io5No catalog matchthird-partyscript, fetch
www.googletagmanager.com4Google: analytics / tag managementservicescript
ad.doubleclick.net3Google: advertisingservicefetch
*.online-metrix.net3No catalog matchthird-partydocument, script, image
*.cdn.forter.com3No catalog matchthird-partyping
*.demdex.net2Adobe: analytics / advertisingservicefetch, xhr
*.doubleclick.net2Google: advertisingservicescript
www.facebook.com2Meta: social / advertising pixelserviceimage
*.go-mpulse.net2No catalog matchthird-partyscript, xhr
*.agkn.com2No catalog matchthird-partyimage, xhr
cdn.quantummetric.com1Quantum Metric: session replay / product analyticsservicescript
*.bing.com1Microsoft: advertising / analyticsserviceimage
*.pinterest.com1Pinterest: social / advertising pixelservicexhr
www.google-analytics.com1Google: analytics / tag managementservicescript
analytics.google.com1Google: analytics / tag managementservicefetch
www.googleadservices.com1Google: advertisingservicefetch
*.google.com1Google: advertisingserviceimage
*.thdws.com1No catalog matchthird-partyscript

+8 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
20260814-0d43cea9be32d1d52650401b4661cce3
Site
homedepot.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: fingerprinting evidence was censored before completion: the in-page fingerprint observer did not finish (recorded loss count: 1); detector output evidence was censored before completion: the synthetic keystroke probe did not complete its test (recorded loss count: 1); recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Variant visit

Started
Run quality
cut short: request evidence was censored before completion: the producer recorded an additional collection loss (recorded loss count: 13); fingerprinting evidence was censored before completion: the in-page fingerprint observer did not finish (recorded loss count: 2); detector output evidence was censored before completion: the synthetic keystroke probe did not complete its test (recorded loss count: 1); recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

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 .