Check the evidence yourself.

Drop in a CapchaCloud evidence bundle or a chain consistency proof. This page recomputes every hash and signature in your browser. The file is not uploaded and no account is needed. If you do not trust this page either, the same checks run from the command line.

What to check

Drop a .json file here, or

choose a file

Or paste the JSON

For a chain proof: the block hash you already trusted for the first height (optional)

For a chain proof: signing keys you saved earlier, as JSON (optional)

For a sanctions absence proof: the list commitment root you trust, from a sealed receipt (optional)

For a bundle: the operator public key, base64 (optional)

Result

Nothing checked yet.

What this does and does not prove

It proves the contents were not changed after they were signed, that a chain run is unbroken and correctly signed, and that a newer head extends a block you recorded earlier.
It does not prove that what was recorded was true when it was recorded. A faithful record of a false statement is still false.
Trust is only as strong as what you already hold. Keys fetched from this same site are a convenience. Paste keys you saved earlier to remove that trust.
Not checked in the browser: post-quantum signatures, RFC 3161 and OpenTimestamps witnesses, and ISO 20022 or examiner bundles. The command-line verifier covers those: scripts/capcha-verify.mjs and scripts/verify-evidence-bundle.mjs.