Verify records
Check an export of Mandate records. No account is needed and nothing you upload is stored.
What a pass means
- Every record is signed with a key this service publishes.
- No record's content was changed after it was sealed.
- No record is missing from the middle of a chain.
- No record was removed from the end: the newest record matches the signed checkpoint in the file.
- Where the file carries anchors, the timestamp authority's reply is over the anchored checkpoint, and every chain still holds the records it saw.
What it does not mean
This service holds the signing key, so a signature alone shows that nobody else altered the records, not that the service never reissued them. An anchor closes that gap up to its time: the checkpoint was timestamped by an outside authority (DigiCert), so the history it covers cannot have been reissued since without this check failing. Records sealed after the newest anchor rest on the signature alone. A pass also says nothing about whether what was sealed was right; that is for the auditor.
Checking offline
You do not have to trust this page. The same check runs on your own machine. Give it the key from a source you trust, not the one inside the file:
node cli/mandate.mjs verify mandate-records-2026-09.json --key-url https://mandate.software/.well-known/mandate-signing-key.json
Without a key the result is UNPINNED, not VERIFIED, because anyone can make a file that agrees with itself.