Verify a certificate.

Paste the code from the PDF, or scan the QR.

The code sits under the QR on every certificate, or in the verify link from the issuance email — a string like 8f2a9c1e-4b3d….

How verification works

Every certificate pramaan.me issues gets a SHA-256 hash computed at the moment of issuance, then stored against its certificate id. The hash is a fingerprint of the exact PDF bytes — change one pixel, one date, one name, and the fingerprint no longer matches. This page checks the live record, not a copy: what you see is what the issuer's system has on file right now.

Tamper-evidence works by absence, not by watermark. Nothing on the PDF itself stops someone editing it in a graphics tool. What stops them is that the edited file's hash won't match the one on record — so a verifier here sees a hash mismatch, or no match at all, and knows to distrust the document. The certificate that matches is the certificate that was actually issued.

A certificate can also be revoked after issuance — a correction, a fraud finding, an event the issuer later invalidated. A revoked certificate stays on record rather than disappearing: this page will say it was revoked, and when, so anyone who saved the original link still gets a true answer instead of a dead page.