Example proof packages

See exactly what you get.

Every proof you create comes back as a single downloadable .zip — your proof package. Inside is a human-readable certificate, the evidence we captured, an independently-witnessed record of the network traffic plus the keys to decrypt it, and a cryptographic manifest that ties it all together and fixes it in time. Here is the package, file by file, before you create one.

Create your first proof Jump to examples ↓

What every package contains

Whatever you capture, the package is built the same way — five layers, each one independently checkable.

1 · A signed certificate (PDF)A plain-language summary anyone can read: what was captured, when (UTC), a unique certificate ID, the verification URL, and the SHA-256 hashes of every other file in the package.

2 · The captured evidenceThe thing itself — a video recording, a page screenshot, a rendered transcript, or your original file — exactly as captured.

3 · Independently-witnessed network captureThe raw (encrypted) network traffic, recorded and signed by an independent witness that can see it but never read it — delivered with the session keys so anyone can decrypt it back to the real HTML/JSON, plus the full network log (HAR).

4 · A signed manifestA manifest.json that lists every file and its SHA-256 hash, sealed with a digital signature. Change one byte of anything and the seal breaks.

5 · A trusted timestampAn RFC-3161 / eIDAS timestamp token from an independent authority, fixing the moment the evidence existed — not a date we typed in.

Verifiable by anyoneNothing in the package depends on trusting us: the signature checks against a public key, the capture decrypts with the included keys, and the timestamp is third-party. See how a certificate is verified.

Examples, by what you capture

The same five layers, tailored to the job. File names below are illustrative.

Website / URL capture

A live web page

A social-media post, a marketplace listing, a published statement — captured in a clean-room browser.

proof-2026-06-30-S-1042.zip ├─ certificate.pdf signed summary + all hashes ├─ screenshot.png the page as rendered ├─ network.har every request & response ├─ witness/ │ ├─ capture.pcap encrypted traffic, witnessed │ ├─ capture.sig witness signature (Ed25519) │ ├─ tls-keys.log keys that decrypt the capture │ └─ timestamp.tsr RFC-3161 trusted timestamp ├─ manifest.json SHA-256 of every file └─ manifest.sig seal over the manifest

screenshot.pngWhat a viewer saw at capture time.
capture.pcap + tls-keysProof the content came from the real server — decryptable to the actual HTML/JSON, carrying the server’s own certificate.
manifest.sigTamper-evidence: any later edit breaks the seal.

Browser session recording

A recorded session (video)

You drive a clean, isolated browser — log in, navigate, scroll — and the whole session is recorded.

proof-2026-06-30-S-1043.zip ├─ certificate.pdf signed summary + all hashes ├─ recording.mp4 the full session, on video ├─ network.har every request & response ├─ witness/ │ ├─ capture.pcap encrypted traffic, witnessed │ ├─ capture.sig witness signature (Ed25519) │ ├─ tls-keys.log keys that decrypt the capture │ └─ timestamp.tsr RFC-3161 trusted timestamp ├─ manifest.json SHA-256 of every file └─ manifest.sig seal over the manifest

recording.mp4What you saw and did, end to end.
capture.pcap + tls-keysThe network underneath the video — decryptable and independently witnessed, so the recording can’t be a fabrication.
isolated containerEach session runs in a clean environment that resets every time. Origin IPs are recorded in the certificate.

WhatsApp export

A WhatsApp chat export

You upload an export from your phone; we render it to a clean, fixed-in-time transcript and bind both.

proof-2026-06-30-S-1044.zip ├─ certificate.pdf signed summary + all hashes ├─ transcript.pdf faithful rendering of the export ├─ original-export.zip exactly the file you uploaded ├─ manifest.json SHA-256 of every file ├─ manifest.sig seal over the manifest └─ timestamp.tsr RFC-3161 trusted timestamp

original-export.zipThe exact bytes you submitted, bound by hash.
transcript.pdfA readable version a court or lawyer can review, provably matching the export.

Honest limit: a WhatsApp export has no signature from WhatsApp, so we cannot certify the conversation is genuine or untampered. This package proves only that the transcript faithfully renders the file you uploaded, fixed in time. Want stronger proof? Have the other person send a message while you record a live WhatsApp Web session — captured and witnessed on the wire, that proves the message genuinely arrived from WhatsApp’s servers. See how →

File certification

A file you already have

A document, photo, video or archive — sealed and timestamped exactly as submitted.

proof-2026-06-30-S-1045.zip ├─ certificate.pdf signed summary + all hashes ├─ contract-final.pdf your file, exactly as submitted ├─ manifest.json SHA-256 of every file ├─ manifest.sig seal over the manifest └─ timestamp.tsr RFC-3161 trusted timestamp

your fileBound by SHA-256 — proof this exact file existed at this time.
timestamp.tsrIndependent proof of when — useful for priority, authorship and pre-dating disputes.

What the certificate looks like

The PDF certificate is the human-readable front page of the package. Every field is also bound, by hash, in the signed manifest.

Certificate ID: IP-2026-001042
Captured subject: https://example.com/posts/9281
Session ID: S-1042
Requested at (UTC): 2026-06-30T09:14:02Z
Generated at (UTC): 2026-06-30T09:14:48Z
Origin IPs: 203.0.113.7
Metadata file: …-S-1042-metadata.zip · SHA-256 4f9a…c1d2
Signing key: SHA-256 a17b…9e44
Verify URL: https://secure.instantproof.legal/verify/IP-2026-001042
Software version: instantproof @ git c027506

New to certificates? Read what a digital certificate is · or what a HAR file is.

How anyone verifies it

Check the sealVerify the manifest signature against our public key, then recompute the SHA-256 of every file and match it to the manifest. One altered byte fails the check.

Decrypt the witness captureApply the included session keys to the independently-witnessed capture.pcap to recover the real HTML/JSON the servers returned — and the servers’ own certificates.

Confirm the timeValidate the RFC-3161 / eIDAS timestamp token against the timestamping authority. The moment is fixed by a third party, not by us.

Now create one of your own.

Capture a web page, a session, a message thread or a file, and walk away with the exact package you just saw — independently witnessed, sealed and timestamped.

Create your first proof Request early access →