Baseline visit v1 schema · facts legacy-derived · descriptive report
https://www.postgresql.org/
Aug 24, 2026, 8:12 AM UTC
complete; derived from status and warnings
Public corrections ledger · SBL-CORR-2026-001
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.
Scan report ready for www.postgresql.org: 21 recorded request rows.
Comparison Reportv1 schema · facts legacy-derived · descriptive report
Context
The scan observed signals a non-expert should not have to decode from raw request tables.
The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.
Context
5 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
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. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.
Nothing observed
With the scanner configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit; application was not verified), this paired visit showed 5 fewer third-party requests and 5 fewer tracking-related service requests.
Services only seen in the unblocked visit: Google. The blocking visit's engine directly blocked 1 request; 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), so treat this as an observed difference, not a measured blocking rate.
Context
Google 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. Functional catalog labels include analytics / tag management. This scan identified an operator for every one of the 2 third-party domains recorded here using catalog, consent-platform, reviewed-ownership, and CNAME evidence.
Context
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.
Nothing observed
Google Analytics was observed, but no DoubleClick remarketing sync appeared in this visit.
Standard analytics collection was observed, without the stats.g.doubleclick.net advertising sync.
Nothing observed
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.
Nothing observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
Brave Shields Comparison
Every signed change is Brave-list blocking minus No blocking. A positive or negative direction is descriptive, not a judgment that the result is better or worse.
Cookie and storage count deltas include every observation. Name-level lists show only reviewed names; unreviewed names are not itemized because they can contain identifiers.
No domain changes observed.
No visible cookie-name changes to show; privacy-filtered names are not itemized.
No storage key changes observed.
No storage key changes observed.
No entity changes observed.
This report
Both visits
Brave-list blocking visit only
Read the findings and measurement limits first, then inspect the evidence for each recorded visit. Comparisons include both visits, even where a difference cannot be interpreted.
Keep this PDF with its evidence package: the source JSON, correction context, export receipt and SHA256SUMS. The package preserves source bytes and the correction context at export time. Hashes check file consistency; they do not establish independent measurement accuracy or a signed attestation.
Correction context SHA-256: 8b4dc650c91f9e1a20f651118d74586978963548cecaa5885e2565e2ccc68c32
Renderer revision: 3c18992e02534f33c825f7c2e51dd534d3ccab0d
2026-08-24T08:12:00.753Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
5 third-party requests: 5 attributed to a single recorded actor, 0 not attributable.
Horizontally scrollable visual map. A text list of every relationship drawn in it follows.
Select a relationship to see its detail and open the rows behind it.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.21 requests were recorded from 52 ms to 1,403 ms. Open the request log for exact timing and request details.
| Domain | Role | Requests | Catalog match | Resource types |
|---|---|---|---|---|
| www.google-analytics.com | service | 3 | Google: analytics / tag management | script, xhr, fetch |
| www.googletagmanager.com | service | 2 | Google: analytics / tag management | script |
| www.postgresql.org | first-party | 16 | No catalog match | document, stylesheet, script, image, font |
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
| Ref | Time | Status | Type | Domain | Provenance | URL |
|---|---|---|---|---|---|---|
B:R0001 | 52ms | 200 | document | www.postgresql.org | Not attributed | https://www.postgresql.org/ |
B:R0002 | 484ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0003 | 485ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0004 | 485ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0005 | 485ms | 200 | script | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0006 | 486ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/…/about/press/… |
B:R0007 | 545ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0008 | 778ms | 200 | script | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0009 | 872ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0010 | 872ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0011 | 977ms | 200 | script | www.googletagmanager.com | initiated by www.postgresql.org | https://www.googletagmanager.com/…?id |
B:R0012 | 1,006ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0013 | 1,007ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0014 | 1,007ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0015 | 1,007ms | 200 | font | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0016 | 1,008ms | 200 | font | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0017 | 1,009ms | 200 | font | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
B:R0018 | 1,145ms | 200 | script | www.google-analytics.com | initiated by www.googletagmanager.com | https://www.google-analytics.com/… |
B:R0019 | 1,213ms | 200 | xhr | www.google-analytics.com | initiated by www.google-analytics.com | https://www.google-analytics.com/…?v&…&t&cid&tid |
B:R0020 | 1,234ms | 200 | script | www.googletagmanager.com | initiated by www.google-analytics.com | https://www.googletagmanager.com/…?id&… |
B:R0021 | 1,403ms | 204 | fetch | www.google-analytics.com | initiated by www.googletagmanager.com | https://www.google-analytics.com/…?v&tid&…&cid |
2026-08-24T08:11:55.444Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
No third-party requests were recorded, so attribution coverage is not applicable.
No retained third-party request has one recorded actor to draw. This is not evidence that no actor was involved: the visit may have reported no actor or several actors for the same request.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.16 requests were recorded from 48 ms to 947 ms. Open the request log for exact timing and request details.
| Domain | Role | Requests | Catalog match | Resource types |
|---|---|---|---|---|
| www.postgresql.org | first-party | 16 | No catalog match | document, stylesheet, script, image, font |
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
| Ref | Time | Status | Type | Domain | Provenance | URL |
|---|---|---|---|---|---|---|
V:R0001 | 48ms | 200 | document | www.postgresql.org | Not attributed | https://www.postgresql.org/ |
V:R0002 | 501ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0003 | 503ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0004 | 503ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0005 | 503ms | 200 | script | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0006 | 504ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/…/about/press/… |
V:R0007 | 564ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0008 | 809ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0009 | 810ms | 200 | stylesheet | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0010 | 811ms | 200 | script | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0011 | 944ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0012 | 945ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0013 | 945ms | 200 | image | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0014 | 946ms | 200 | font | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0015 | 947ms | 200 | font | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
V:R0016 | 947ms | 200 | font | www.postgresql.org | initiated by www.postgresql.org | https://www.postgresql.org/… |
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.
Integrity and provenance
20260824-f70806bec175938f2e174a4cc9fe8136Recorded 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. 16 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 13 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 .