Public trust repository · Operated by METASHIP LIMITED, registered in England and Wales (company 16185486)
Preview build. Not yet published: 1 go-live item(s) open.
TrustedAnchor

Verify

Check a signed record

Paste or drop a credential below. Your browser checks the signature against the signer’s published key. If you choose, it also asks the TrustedAnchor register whether the record and signer are on file.

A .json file exported from the inspection app, or text copied from one.

— or drag one onto this box. Files are read locally.
No record to hand?

The result appears here: each check is listed separately, so you can see exactly what was proven and what was not.

What exactly is checked?
  1. Format. The document is a W3C Verifiable Credential and carries a proof.
  2. Proof type. DataIntegrityProof using eddsa-jcs-2022, made for an assertion.
  3. Signer. The signing key belongs to the stated issuer, and the issuer’s DID document lists it as allowed to make assertions. For did:key the key is the identifier itself. For did:web the document is fetched from the issuer’s domain.
  4. Signature. SHA-256 over the canonical (RFC 8785) proof options and document, checked with Ed25519 by your browser’s WebCrypto.
  5. Register (optional). Whether the key is enrolled and active, whether a matching sealed record is on file, and whether it has been voided.

The verifier is one readable file: verify.js. Save it with this page to check records offline.