Site Behavior Lab
Site

www.nasa.gov

Baseline visit
Requested address
https://www.nasa.gov/
Report ID
20261019-290abb2b9b252ce040e50d88e25aa53d
Evidence SHA-256
7ba21d55dee7fb97b184eda0c7f0262f4e2d41cf988c5986407c52082cc7bf77
Scanner
playwright-chromium

nasa.gov's retained request log includes catalogued Google domains.

Where this page's requests went

The No blocking visit. One mark is one request row in the retained log.

www.nasa.gov itselfat least 88 retained requestsrequests that stayed on the site
Catalogued servicesat least 8 retained requests2 names: Google 5, Parse.ly 3
Hosts the catalog does not nameat least 3 retained requests2 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

Retained request rows include 2 distinct catalogued tracking-service entities; 2 of the retained service matches recorded responses across at least 7 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. 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.

≥2tracking-service entities retained
≥11cross-site requests

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 activity evidence was also incomplete: request counts are retained lower bounds, cookie counts are an incomplete end-state snapshot and storage counts are an incomplete end-state snapshot.

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 99 retained requests observed in one controlled visit.

What was checked

Page
https://www.nasa.gov/
When
Oct 19, 2026, 11:21 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 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: every check. Every card below states only what was retained.

Worth checking

At least 10 retained requests matched Brave Shields filter lists

At least 10 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 Shields comparison is not conclusive

The "No blocking" visit exhausted its aggregate response-byte budget, so its request evidence is incomplete. The "Brave-list blocking" visit exhausted its aggregate response-byte budget, 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

Context

Catalogued service domains recorded responses during this visit

Google and Parse.ly 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 audience analytics. This scan could not identify 1 of the 7 third-party hosts recorded here, so it cannot say who operates it. That is a limit of identity coverage, not evidence about the site.

At least 11 retained cross-site requests across at least 7 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.

At least 5 retained requests to these platforms.Show catalog-matched requests

Context

Incomplete evidence: Google Analytics present, no remarketing signal in retained evidence before collection stopped

Google Analytics was observed, but no DoubleClick remarketing sync appears in the retained evidence.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

Standard analytics collection was observed, without the stats.g.doubleclick.net advertising sync.

Google Analytics host observed; no stats.g.doubleclick.net request.Show catalog-matched requests

Context

Incomplete evidence: No third-party cookies observed in retained evidence before collection stopped

No third-party cookies appear in the retained evidence.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

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's incomplete snapshot.

Context

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: 21 interaction-listener registrations with https://cdn.parsely.com/, https://*.digitalgov.gov/ and https://www.googletagmanager.com/ in the registration call chain. Input-monitoring listener coverage: 4 input-listener registrations with https://cdn.parsely.com/ and https://*.digitalgov.gov/ in the registration call chain.

Look closer

Show requests involving cdn.parsely.com

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

Context

Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped

The retained evidence holds no calls to the instrumented high-entropy browser APIs.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

This is an observation layer, not proof that fingerprinting is impossible.

Retained incomplete evidence includes 0 API event records; no exact API-family total is available.

Domain evidence

10 recorded domains

These are retained domain rows, not a complete inventory.

The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 6 sCatalog matchRoleResource types
www.nasa.gov61No catalog matchfirst-partydocument, stylesheet, font, image, script, media
assets.*.nasa.gov20No catalog matchfirst-partyimage
*.nasa.gov7No catalog matchfirst-partyimage, xhr
www.googletagmanager.com4Google: analytics / tag managementservicescript
*.digitalgov.gov2No catalog matchthird-partyscript
cdn.parsely.com1Parse.ly: audience analyticsservicescript
api.parsely.com1Parse.ly: audience analyticsservicefetch
*.parsely.com1Parse.ly: audience analyticsserviceimage
www.google-analytics.com1Google: analytics / tag managementservicefetch
www.google.com1No catalog matchthird-partyfetch

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
20261019-290abb2b9b252ce040e50d88e25aa53d
Site
www.nasa.gov
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the visit hit the scanner's total response-byte budget, so it stopped loading further content; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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 visit hit the scanner's total response-byte budget, so it stopped loading further content; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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.

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 .