Glossary
What Is Certificate Verification?
Certificate verification is confirming that a certificate was really issued by the organisation it names, to the person it names, and hasn't been altered since.
Also called: verify a certificate, certificate authentication
What it's for
Someone hands you a certificate. It has a logo, a signature, a date and a seal. None of that tells you anything, because all of it can be copied in ten minutes by anyone with the original and an image editor.
Verification is the step that turns a plausible-looking document into a checked one. It answers three questions: did this organisation issue it, to this person, and has it been changed since?
How it works
There are three approaches, in increasing order of how well they work:
- Ask the issuer. Phone or email the organisation named on the certificate. Reliable and unbearably slow — which is why in practice almost nobody does it, and why forgeries survive.
- Look it up. The certificate carries an ID or a link; a verifier opens the issuer's own record and compares. Fast, and good enough for nearly everything. Its weakness is that it depends on the issuer's site still being there.
- Check the signature. The certificate is a Verifiable Credential carrying cryptographic proof. A verifier confirms it mathematically, offline, with no need for the issuer at all.
A well-issued certificate offers the second and third at once: a link and a QR code for the human being holding it, and a signed credential for anything checking it automatically.
Two things verification can't do. It can't tell you the claim is true — only that the named issuer made it. And it can't tell you the issuer is trustworthy. A perfectly verifiable certificate from an organisation nobody has heard of is exactly as worthless as it sounds.
Where you'll see it
Employers checking a candidate's qualifications. Registrars processing admissions. Conference organisers confirming CPD hours. Anyone who has been burned once by a document that turned out to be edited.
In Verifycate
Every certificate has a public page and a QR code. Anyone with the link or the code can open it and see the issuer's own record: recipient name, issuer, issue date, and whether it's current or expired. No account, no login.
Behind that page is an Open Badge 3.0 credential signed with the workspace's own key, downloadable as JSON, so a verifier who wants to check it independently can. And the QR on a downloaded PNG or PDF still resolves back to the same page — so a printed copy, three forwards later, is still checkable.
Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free
Common questions
- How do I verify a certificate is genuine?
- Scan its QR code or open its verification link and compare what the issuer's own record says with the document in front of you. If the certificate has neither, the only remaining option is contacting the issuer directly.
- Can a verification page itself be faked?
- A convincing lookalike page can be built, which is why the domain matters — check the link resolves to the issuer's real domain, not something close to it. A signed credential closes the gap properly, because the signature can't be forged without the issuer's key.
- Does verifying a certificate cost anything?
- Not on Verifycate — verification pages are public and free to open, with no account needed. Some enterprise credentialing platforms charge issuers for verification volume.
- What if the issuing organisation no longer exists?
- Lookup verification breaks; signature verification doesn't, since the proof travels with the credential. It's one of the strongest arguments for issuing a signed credential rather than only a hosted page. Verifycate keeps issued pages up after a workspace stops paying, for the same reason.
Related terms
- QR Code VerificationQR code verification puts a scannable code on the certificate itself, so anyone holding a copy — printed or digital — can reach the issuer's own record of it in one scan.
- Credential IDA credential ID is the unique reference for one issued credential, used to look it up, verify it, and tell it apart from every other credential the same issuer has given out.
- Credential ExpiryCredential expiry is a date set at issue after which a credential is no longer current — the record stays, but verification reports it as expired rather than valid.
- Verifiable CredentialA Verifiable Credential is a claim about someone, signed by whoever made it, in a W3C format any verifier can check on its own — without contacting the issuer.
Issue certificates people can actually check.
Every certificate gets a QR code, a public page, and an Open Badge 3.0 credential. 300 free credits, no card.
“We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF
Start for free