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.
usa.gov's retained request log includes catalogued Google domains.
Where this page's requests went
Both visits. One mark is one request row in the retained log.
GPC off
usa.gov itselfat least 24 retained requestsrequests that stayed on the site
000000000000000000000000
Catalogued servicesat least 8 retained requests2 names: Google 7, Crazy Egg 1
00000000
Hosts the catalog does not nameat least 8 retained requests5 hosts; the catalog cannot say who operates them
00000000
GPC on
usa.gov itselfat least 24 retained requestsrequests that stayed on the site
000000000000000000000000
Catalogued servicesat least 8 retained requests2 names: Google 7, Crazy Egg 1
00000000
Hosts the catalog does not nameat least 8 retained requests5 hosts; the catalog cannot say who operates them
00000000
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
Retained request rows include 2 distinct catalogued tracking-service entities; 1 of the retained service matches recorded responses across at least 8 retained 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 a catalogued session-replay service appeared or broad interaction listeners were registered. 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.
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 activity evidence was also incomplete: request counts are retained lower bounds.
This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds.Details
The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.
At least 40 retained requests observed in one controlled visit.
What was checked
Page
https://www.usa.gov/
When
Aug 14, 2026, 7:20 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.
At least 13 retained requests out of 40 requests the engine evaluated matched Brave Shields filter lists
At least 13 retained 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 at least 8 retained 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 baseline visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals. 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.
3 disqualifying conditions named by the report's claim policy.
Context
Requests were dispatched to catalogued service domains
Google and Crazy Egg 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 and session replay / behavior analytics. This scan could not identify 5 of the 8 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: Crazy Egg. The domain match alone does not prove that a recording occurred.
At least 16 retained cross-site requests across at least 8 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 Google.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
The automated visit did not observe third-party cookies.
This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.
5 cookies total in this report.
Worth checking
Session-recording signal matched a known vendor
The page registered broad interaction listeners through call chains that included a third-party script, and contacted a known session-replay service.
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: 183 interaction-listener registrations with https://*.digitalgov.gov/, https://siteimproveanalytics.com/ and https://www.googletagmanager.com/ in the registration call chain. Known session-replay vendor(s): Crazy Egg.
Opens this report's request log filtered to Crazy Egg; listener registrations are not request rows, so the log cannot show what was observed.
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.
Domain evidence
9 recorded domains
These are retained domain rows, not a complete inventory.
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 6.1 s
Catalog match
Role
Resource types
www.usa.gov
24
No catalog match
first-party
document, image, stylesheet, script, other, font
www.googletagmanager.com
5
Google: analytics / tag management
service
script
*.*.qualtrics.com
3
No catalog match
third-party
script, xhr
www.google-analytics.com
2
Google: analytics / tag management
service
fetch
*.digitalgov.gov
2
No catalog match
third-party
script
*.crazyegg.com
1
Crazy Egg: session replay / behavior analytics
service
script
siteimproveanalytics.com
1
No catalog match
third-party
script
*.*.siteimproveanalytics.io
1
No catalog match
third-party
image
*.*.*.qualtrics.com
1
No catalog match
third-party
script
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.
cut short: request evidence was censored before completion: the bounded public evidence projection did not finish (recorded loss count: 1); recorded by the scanner
cut short: request evidence was censored before completion: the bounded public evidence projection did not finish (recorded loss count: 1); recorded by the scanner
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 .