Check an audit log or certificate

SafeHanded

Choose the JSON audit export, or a certificate's Signed JSON. The PDF can't be checked.

Drop a file here, or choose one An audit export (.json) or a Signed JSON certificate

The check runs in your browser. The file is never uploaded; the only request this page makes is to fetch SafeHanded's published signing key.

Reading the result

Three answers, in plain English.

Every event is exactly as SafeHanded recorded it, and the file carries SafeHanded's signature.

The events are consistent with each other, but the file carries no SafeHanded signature, so we can't confirm SafeHanded produced it.

Something was edited, added or removed after SafeHanded recorded it. We name the event so you can compare it with a fresh export.

How it works

You don't need to trust this page either. It uses the same rules as the command-line verifiers, and anyone can read its source.

Nothing is uploaded. Your browser reads the file and does the maths itself.
Every event is linked to the one before it, so a change to any of them breaks the chain from that point on.
SafeHanded signs every event with a key it publishes, so a rebuilt or forged file won't match.
Prefer to check offline? Ask us for the command-line verifiers. They give the same answers.