Check a Seal receipt yourself

Paste a signed record. Your browser checks its signature against Seal’s published key. No account, nothing uploaded to us, and no request to Aqta is made to produce the verdict. The same check runs offline from a terminal with npx aqta-verify-receipt, and there are two separately written implementations, on npm and on PyPI, which must agree on the same bytes.

What a valid result establishes

That these exact fields verify against the issuer’s published key, and that not one character has changed since they were signed. Alter a single field and the signature fails. That is worth trying rather than believing.

What it does not establish

That the decision recorded was the right one, that the policy behind it was sound, or that every decision reached Seal at all. A valid signature proves which key signed and that nothing has changed. It says nothing about judgement, and a decision that never entered Seal leaves no record to check.