Evidence verification
Verify an R2PQ Evidence Receipt
Check supplied receipt hashes and supported RFC 3161 tokens locally. Token signatures are checked against embedded keys; trusted TSA identity, operator provenance and assessment correctness are not established.
The checked-in verifier processes receipt data locally and makes no network call for verification. Page loading and hosting behavior are separate.
Provide a receipt
Receipts are JSON files, typically around 10 KB. Nothing you paste leaves this page.
Result
Ready
Choose a file, paste, or load the demo receipt to begin.
What was checked
These are distinct questions. A receipt can be cryptographically sound and still tell you nothing about who produced it.
-
Integrity
Do the receipt's own hashes agree with each other?
Not yet checked
-
Timestamp
Does an RFC 3161 token commit to this evidence?
Not yet checked
-
Signature
Is the timestamp token's signature intact?
Not yet checked
-
Certificate trust
Does the signing certificate chain to a trusted root?
Not evaluated in the browser
-
Provenance
Who performed this assessment?
Not established
Checks that passed
What these checks do not establish
Technical detail
See what tampering looks like
The demo exercises supported checks. The button changes one character of its declared root. Root reconstruction and timestamp binding then fail; unauthenticated display metadata is outside those checks.