Site Behavior Lab
Site

wellsfargo.com

Baseline visit
Requested address
https://www.wellsfargo.com/
Report ID
20260814-b1c40f92b44cac7cc4e89fbf6ae94717
Evidence SHA-256
2cbb077703a12d46239f29af4636925fe36679468a67f20c82a9c3aac1e81e23
Scanner
playwright-chromium

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

wellsfargo.com contacted catalogued Google and Microsoft domains during the visit labeled GPC off.

Where this page's requests went

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

GPC off

wellsfargo.com itself68 requestsrequests that stayed on the site
Catalogued services23 requests6 names: Google 10, Adobe 6, Amazon Ads 3, LiveRamp 2, Microsoft 1, and 1 more
Hosts the catalog does not name69 requests14 hosts; the catalog cannot say who operates them

GPC on

wellsfargo.com itselfat least 68 retained requestsrequests that stayed on the site
Catalogued servicesat least 13 retained requests6 names: Adobe 5, Amazon Ads 3, Google 2, LiveRamp 1, Microsoft 1, and 1 more
Hosts the catalog does not nameat least 52 retained 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
  • the count is a lower bound; more may exist
  • not measured

6 distinct catalogued tracking-service entities had requests dispatched (5 recorded responses; the rest recorded no response) across 23 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. 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 3 browser-fingerprinting heuristics matched. 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.

6tracking-service entities
92cross-site requests
15third-party cookie records
3fingerprint-like patterns

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.

160 requests observed in one controlled visit.

What was checked

Page
https://www.wellsfargo.com/
When
Aug 14, 2026, 6:59 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.
  • 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: the typing test and the privacy policy check. In the GPC on visit only: Brave Shields matches, the consent banner, third-party services, named platforms, Google Analytics remarketing and advertising pixels.

Worth checking

47 of 141 requests the engine evaluated matched Brave Shields filter lists

47 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 23 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

Requests were dispatched to catalogued service domains

Google, Adobe and Amazon Ads, 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 analytics / tag management, advertising and analytics / advertising. This scan could not identify 12 of the 23 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

92 cross-site requests across 23 third-party hosts.At or above the median for third-party domains across the 51 sites measured for this metric. Elevated distinct tracking-service entities count (at or above the 6 reference threshold).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.

11 requests to these platforms.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

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

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

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. 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: 23 interaction-listener registrations with https://*.wfinterface.com/ in the registration call chain. Input-monitoring listener coverage: 7 input-listener registrations with https://*.wfinterface.com/ in the registration call chain.

Look closer

Show requests involving *.wfinterface.com

Opens this report's request log filtered to *.wfinterface.com, a script origin recorded in the listener's call chain.

Worth checking

Behavioral fingerprinting heuristics matched

3 behavioral heuristics matched: Canvas fingerprinting heuristic, Offline audio rendering heuristic and Canvas font probing heuristic.

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.

Canvas fingerprinting heuristic: 3 canvases matched; reads: canvas.toDataURL. Offline audio rendering heuristic: 3 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 1 other. Canvas font probing heuristic: 68 measureText calls across up to 68 fonts; measured text contents are not stored.

Domain evidence

27 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 12.8 sCatalog matchRoleResource types
www.wellsfargo.com40No catalog matchfirst-partydocument, script, stylesheet, fetch, xhr
*.wellsfargomedia.com28No catalog matchthird-partyimage, font
static.wellsfargo.com14No catalog matchfirst-partyscript, xhr, fetch, image
*.secure.wellsfargo.com12No catalog matchfirst-partyscript, xhr
*.secure.wf.com9No catalog matchthird-partyxhr, fetch
*.wf.com8No catalog matchthird-partydocument, xhr, script
*.demdex.net6Adobe: analytics / advertisingservicefetch, image
*.wfinterface.com6No catalog matchthird-partyscript
*.*.doubleclick.net5Google: advertisingserviceping, document, image
*.adobedc.net4No catalog matchthird-partyfetch
www.google.com4No catalog matchthird-partyping, image
*.amazon-adsystem.com3Amazon Ads: advertisingserviceimage
*.analytics.yahoo.com3No catalog matchthird-partyimage
analytics.google.com2Google: analytics / tag managementservicefetch
*.doubleclick.net2Google: advertisingservicedocument
*.rlcdn.com2LiveRamp: identity / advertisingserviceimage
*.wellsfargo.com2No catalog matchfirst-partyother
ad.doubleclick.net1Google: advertisingserviceimage
*.bing.com1Microsoft: advertising / analyticsserviceimage
*.taboola.com1Taboola: advertising / recommendationsserviceimage
*.onetrust.com1No catalog matchthird-partyxhr
*.videoamp.com1No catalog matchthird-partyimage
*.schemaapp.com1No catalog matchthird-partyfetch
cdn.schemaapp.com1No catalog matchthird-partyfetch
*.everesttech.net1No catalog matchthird-partyimage
*.agkn.com1No catalog matchthird-partyimage
*.eum-appdynamics.com1No catalog matchthird-partyxhr

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-b1c40f92b44cac7cc4e89fbf6ae94717
Site
wellsfargo.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: detector output evidence was censored before completion: the synthetic keystroke probe did not complete its test (recorded loss count: 1); the privacy-policy link search did not finish (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: 3); detector output evidence was censored before completion: the synthetic keystroke probe did not complete its test (recorded loss count: 1); the privacy-policy link search did not finish (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. 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 .