Every check below runs on your own device — never on our servers. Public keys come from the issuer’s public DID document, so results cannot be forged or altered by us.
…
Awaiting verification
Click “Fetch & Verify” to begin; every result is computed independently on your device.
Credential FactsCredential Facts
No credential loaded yet
Tamper Challenge — Try It YourselfTamper Challenge
Change anything in the credential below — raise the score from 95 to 100, or alter the origin — then press “Re-verify”. The signature fails instantly, because the file is locked by the issuer’s private key: a single changed character breaks the signature.
Why this is not an ordinary lookup pageWhy You Can Trust It
Evidence is independently retrievable. The credential is a standard document (a W3C Verifiable Credential), not a page viewable only here — download it and verify it with any third-party system.
Public keys are independently published. The issuer’s identity and public key live in a public DID document; verification uses the issuer’s key, not the website’s say-so.
A mathematical signature locks the content. The Ed25519 signature covers the entire file; without the issuer’s private key no one can mint a fake passport that passes.
The hash chain prevents later repudiation. Each credential hash is append-only and linked into a chain, so issuance records interlock and can be verified end to end.
Verification runs locally on your device. All cryptographic checks happen inside your browser; the server never sees the process and therefore cannot fake it.
The specification is publicly auditable. The verification protocol follows the DPP-CQ Standard (ICO Std 2001) published on dppcq.org — anyone can download the spec and cross-check it against the engine’s source code.
