1 scan
from the QR to the record
No account
needed by whoever checks
VC 2.0
signed credential behind every page
Offline
a verifier that runs with the site down
A page per certificate
Unique ID, unguessable URL, and the full record: recipient, issuer, template, issue date — and your logo on the page.
Expiry that enforces itself
Give certifications a validity period. The verify page flips to expired on its own, and reminder emails go out before it happens.
Revocation in one click
Issued in error, or withdrawn for cause? Revoke it and the public page says so immediately — no PDF recall required.
Open Badges endpoints
Machine-readable assertions for platforms that speak the standard, alongside the human-readable page.
One-click LinkedIn
Recipients add the credential to their LinkedIn profile from the email or the verify page — your brand travels with it.
Tamper-evident by design
The document points at the record, not the other way round. A forged PDF fails the only check that matters.
How it runs
- 1
Issue as usual
Every certificate gets its ID, page and QR automatically.
- 2
Anyone scans or clicks
Employers, registrars, border officers — no account needed.
- 3
You stay in control
Expire, revoke or restore; the page always tells the truth.
Who runs this every week
What teams ask before they start
What does a verifier actually see?
A public page with the recipient, the issuing organisation with its logo, the template name, the issue date, the expiry if one was set, and the current standing: valid, expired or revoked. No login, no app. The URL is unguessable, so pages are found by scanning or clicking, not by browsing.
Is the record machine-readable, or only a web page?
Both. Each certificate also exposes an Open Badges 2.0 assertion and a signed W3C Verifiable Credential 2.0. The issuer is a did:web identity published on your domain, so any conformant wallet or verifier can check the signature without contacting CertTrigger.
What happens to the PDF when we revoke a certificate?
Nothing happens to the file, and that is the point. The PDF points at the record, so the moment you revoke it the page reports revoked and the signed credential fails verification. A scanned copy on someone's desk cannot outlive the decision.
Can verification still work if CertTrigger is unavailable?
Yes. The offline verifier is a single self-contained page you can save and run locally. It checks the credential's signature against the did:web document, so a signed credential can be confirmed even while the site is switched off.
The rest of the platform
Your first certificates are minutes away.
Free to start — design a template, send yourself a test, and see the verification page live.