Tamper-evident credentials
Every credential is signed with the issuing institution's key, and its fingerprint is registered at issuance. Editing, backdating or forging it makes verification fail.
Verify a documentW3C Verifiable Credentials · ES256 signatures · No holder data stored
Check a diploma or credential in seconds
Use the ID or QR code on the certificate, or check the PDF itself.
For digital wallets and developers. The token is checked in your browser.
Why you can trust the result
Built to make forgery fail
Digital signatures, published issuer keys and a public revocation registry — checked on every verification.
Signed by the institution itself
Only the institution's own staff can issue, and every issuance is audited. Its public keys are published at its did:web address, so the source is checked directly.
Staff sign inOpen standards, no holder data
Credentials follow W3C Verifiable Credentials 2.0 and Open Badges 3.0. The registry stores no personal data — the holder's name lives only in the signed document.
How verification works