Independent verification · No account required

Verify evidence packages — online or offline.

Verify a public proof by ID/link, or validate an exported evidence ZIP offline. Evidence packages are tamper-evident : any modification changes SHA-256 hashes and fails verification.

What’s inside the ZIP

Proof URL or Proof ID

We extract the UUID automatically from the link.

—

Proof ID

—

Captured at (UTC)

—

Source URL

—

— — —

View proof page Download evidence ZIP

Tip: For the strongest integrity check, download the evidence ZIP and verify it (manifest + SHA-256).

What the evidence ZIP contains

A self-contained forensic package — around 30 files, typically 5–150 MB depending on which optional artifacts (video, full HAR) are included. Captured artifacts + network identity + a four-layer cryptographic trust stack, all bound together by a SHA-256 manifest.

Captured artifacts

screenshot.png

Full-page screenshot rendered at capture time (Playwright Chromium, 1280px viewport, full-height scroll up to 15000px).

page.html

The raw DOM/HTML actually delivered by the server — useful for inspecting structure, links, and scripts as they were served.

content.txt

Extracted plain text — what a reader would actually have seen, stripped of markup. Good for quoting and searching.

capture.webm

Screen recording of the entire capture session in WebM/VP9 format. Useful for showing dynamic content, animations, and consent dialogs being handled.

Network identity & request evidence

network/capture.har

HTTP Archive (HAR 1.2) of every network request the browser made: URLs, methods, headers, status codes, timings, response sizes.

tls/ + network/tls.json

Server's TLS leaf certificate + full chain (PEM files) plus human-readable JSON metadata. Proves the cryptographic identity of the server that served the page.

network/dns.json + rdap.json

Multi-resolver DNS results at capture time (1.1.1.1 + 8.8.8.8 + 9.9.9.9) plus RDAP registration data. The full identity trail per ISO/IEC 27037 § 6.4–6.5.

Capture context & documentation

proof.json

Main proof record: Proof ID, source URL, final URL after redirects, capture timestamp, all SHA-256 fingerprints, anchor & eIDAS status, Bitcoin block + transaction.

capture/capture_meta.json

Detailed forensic metadata: engine version, user agent, viewport, scroll rounds, consent dialogs auto-handled, image-load status, visual quality score.

README.md + report.pdf

Bilingual (EN + CS) offline verification guide for forensic experts + a human-readable Evidence Report (~5–6 MB) suitable for case files and printouts.

Cryptographic trust stack (4 independent layers)

manifest.json

SHA-256 hash of every other file in the package + chain head + anchor & eIDAS metadata. Verification always starts here. Any byte changed = check fails.

chain/

Append-only hash chain (proof_chain.jsonl + chain_head.json). Each event links to the previous via prev_hash — inserting or modifying anything breaks the chain.

anchor/

Bitcoin OpenTimestamps anchor (anchor_payload.json + anchor_receipt.ots). Once confirmed, the timestamp is preserved by the entire Bitcoin network — not by us.

timestamp/

eIDAS qualified timestamp kit (10 files): RFC 3161 TSR, canonical payload, TSA cert chain (PEM + JSON), EU Trusted List for the signer's country, verification report.

Key property: this export is tamper-evident. If any file changes, the manifest hashes won't match and verification fails. The four trust-stack layers are independent — defeating one doesn't break the others.

Want every file explained one by one with copy-paste verification commands? Read the Evidence ZIP — every file inside tutorial.

Open-source CLI verifier

Independently verify offline — forensic grade

For court-grade analysis, run the open-source CLI against any Evidence ZIP. It performs seven verification layers including RFC 3161 timestamp validation, OpenTimestamps receipt structure, and TLS leaf-cert binding — fully offline, no GetProofAnchor servers involved.

$ pip install gpa-verify

$ gpa-verify path/to/evidence.zip

7 verification layers

Bundle integrity, cross-references, chain integrity, eIDAS signature, anchor canonical hash, OTS receipt structure, TLS evidence.

Pure-Python, no GPA dependency

Runs against any Evidence ZIP using only asn1crypto + cryptography. No network calls to our infrastructure.

MIT licensed, open source

Audit the source, fork it, run it in air-gapped environments. Reproducible verification by any third party.

Supports all evidence formats

Works with evidence-1 through evidence-4 bundles. Verified against production proofs.

View on GitHub View on PyPI

When to use it: The web verifier above gives you a quick yes/no answer. The CLI is for adversarial proceedings where you need court-grade evidence of why a proof passes — with full structural validation of every cryptographic layer.

FAQ

Do I need an account to verify?

No. Verification is public and does not require sign-in.

What does “tamper-evident” mean?

The ZIP includes a manifest with SHA-256 hashes. If any file changes, verification fails.

Can I verify without internet access?

Yes. Download the evidence ZIP and verify it offline on this page.

Is evidence “court admissible”?

We provide forensically useful, verifiable records. Admissibility depends on jurisdiction and context.