Prove What Any Website Showed, At Any Point in Time

Every capture automatically gets a SHA-256 cryptographic hash, a unique Certificate ID and an independent RFC 3161 timestamp from a third-party timestamp authority. The time of capture does not rest on our clock alone, and anyone can verify the certificate from day one.

How it works

From capture to court-ready in seconds

1

Capture

Automatic captures run on your schedule. We record the URL, HTTP status, viewport, geo-location, and precise time in UTC.

2

Hash & Timestamp

A SHA-256 hash is computed from the original file and bound to a unique Certificate ID. An independent timestamp authority then signs that hash with the time from its own clock. The image can never be altered without breaking the hash.

3

Verify

Anyone — a lawyer, auditor, or judge — can check the certificate on our public verification page using just the Certificate ID, for as long as the certificate exists. Verification never expires and does not depend on your subscription being active.

What's in a Certificate

SHA-256 Hash

Cryptographic proof that the screenshot file has not been modified since the moment of capture.

URL + Independent Timestamp

Exactly what page was captured and when, down to the second in UTC. The time is also signed by an independent RFC 3161 timestamp authority, so our clock is not the only witness.

HTTP Status

Confirms the page was live and accessible at the time of capture.

EU Storage Region

Data stored in Germany on Hetzner infrastructure, meeting EU data residency requirements.

Plus additional metadata recorded for a complete forensic record: page title, viewport, device type, geo-location, proxy type, and more.

Independent timestamp

Our clock is not the only witness

A hash proves that a file has not changed. On its own it does not prove when the file existed, because that time would come from our server and our database, and you would have to take our word for it.

So every Certificate of Capture also carries an RFC 3161 timestamp from an independent, third-party timestamp authority. The authority receives only the hash, never the screenshot or anything about your account. It signs the hash together with the time from its own clock and returns a token that is stored with the certificate.

Anyone can check that token with standard tools such as OpenSSL, without contacting us or trusting our records. The verification page shows the authority, the signed time and the exact command to run, and lets you download the token. If a certificate was ever issued without one, the page says so plainly.

Why plain screenshots fail in court

Unverifiable

Plain Screenshot

  • No verifiable date or time
  • No cryptographic hash
  • Metadata editable in any image editor

"Opposing counsel challenges authenticity. Auditor asks for proof. You have nothing."

Verifiable

Captureze Certificate

  • SHA-256 hash
  • Independent RFC 3161 timestamp
  • Public verification link

"Tamper-evident. Independently timestamped. Checkable by anyone, without asking us."

Scenarios that demand certified proof

IP & Trademark Disputes

A counterfeiter copies your product page. By the time your lawyer sends a cease-and-desist, the listing is gone. Without a hash-verified archive captured before the takedown, your case has no evidence. Captureze captures and certifies automatically — before you even know about the infringement.

Regulatory Audits

A DPA asks what your cookie banner looked like six months ago. Your team has no timestamped record. With Captureze, every version is archived with a verifiable certificate — ready for the auditor before they finish asking.

Price Compliance

You run a Black Friday sale. A competitor reports your "50% off" claim. The regulator asks for proof of the original price. Captureze archives every product page with timestamps — your pricing history is already documented.

Contract & Terms Disputes

A client claims your website promised different terms at the time of purchase. Without a certified archive, it's your word against theirs. With Captureze, you have a hash-verified snapshot of exactly what was published and when.

Anyone can verify a certificate

1

Go to captureze.com/verify

No login or special tools required.

2

Paste the Certificate ID

Found on any Captureze screenshot or notification.

3

Get instant confirmation

See capture details and cryptographic proof, verified against the stored hash.

Technical verification (CLI)
Download the original file, run sha256sum filename.png, and compare the output with the hash shown in the certificate.
Verify Certificate
CZ-9K2M4P
Verify
Verified
URLexample.com/pricing
Time2026-04-07 15:43:22 UTC
Status200 OK
Hasha8f5f167f44f4964e6...

Built on open standards

SHA-256 (NIST FIPS 180-4)
UTC Time (ISO 8601)
EU-Hosted (Hetzner, Germany)
GDPR-Compliant

Start capturing court-ready evidence today

Every screenshot you take with Captureze is automatically certified. No extra steps, no extra cost.

Start Free

No credit card required