Skip to main content
Open verify.sanning.io and drop the pack on it. The page runs the same open kernel your counterparty would run at a command line, in your browser. The pack is not uploaded. Nothing about it reaches Sanning, which is what lets an auditor check evidence about a company we have never heard of. It also reads a case file, the single archive case writes when several parties’ packs are handed over together. Drop it the same way, and the page reads it as one case. You need no account.

What the page shows

Each card answers one question, and says plainly when it cannot answer. A card that could not run says so rather than passing. An absent check is never rendered as a passed one, which is the failure mode the page is built against.

The report

The page offers a report of what it checked. It is your own re-verification, rendered from the verdict computed in your browser, and it is unsigned because that is what it is. It is not a Sanning attestation and does not claim to be.

When the browser is not enough

Use the command line when you want to:
  • script the check, or run it in CI
  • confirm the witness against a gateway you choose
  • read per-record output rather than a summary

What a verdict does not claim

Four limits, and they matter more than the green banner. See What a verdict means.