Service Receipt v2 · Experimental showcase

Inspect an IFF-signed verification result locally.

Paste a standalone receipt or a complete /api/v3/verify response. All checks run in this browser; the input is not uploaded or saved.

Open-source verifier
Local-only input
Separated checks

Receipt input

Inspect one IFF-signed verification result.

Local only

Receipt envelope or full API response

JSON only, up to 256 KiB. Nothing is placed in the URL or browser storage.

Choose a local JSON file No file selected

Independent issuer policy

Expected issuer Trusted public-key fingerprint

A full fingerprint you obtained independently. The embedded key alone is never trusted.

No receipt loaded.

Separated verification results

Receipt inspection

01
Envelope
02
Payload hash
03
Signature
04
Issuer policy
05
Action window
06
Outer binding
07
Evidence reference
08
Compute proof

Receipt ID
Service
Issuer
Issued
Expires
Key fingerprint
Payload SHA-256
Request SHA-256

Signed subject — authoritative result

application/json

Security boundary

A valid signature establishes provenance for the enclosed IFF result only. Issuer trust, the action window, outer-response binding, and referenced evidence remain separate checks.

Why separate the checks?

Integrity is not identity. Identity is not execution.

Signature

Were these bytes changed?

The signature algorithm named in the receipt (ML-DSA-65 for v2, Ed25519 for historical v1) binds the signed payload to one public key.

Issuer

Do you trust that key here?

A pin or same-origin key directory is evaluated independently.

Evidence

Was the referenced evidence checked?

A signed reference is not proof that its Merkle path, signed tree head, or anchor was verified.