Verify a certificate online — known codes never 404

Certificate verification exists so employers, regulators, and the public can confirm that a credential is genuine and current. Mutamad assigns each issued certificate a unique verification code and a hosted URL on the verify domain. Anyone with the code or link can open the public page without signing in.

A core guarantee: known codes never return 404. If Mutamad issued the credential, the URL resolves. Active credentials display their details — recipient, programme, date, and fields you chose to show publicly. Grade is hidden on the verify page by default unless your organisation enables it.

Revocation does not break verification. When an issuer revokes a certificate, the status changes to revoked and the page reflects that state. The code and URL remain the same. Credentials are append-only records; revoke is a lifecycle transition, not deletion. Expired credentials similarly remain look-uppable with their expired status visible.

The verify page renders from the same template module as the issued PDF. Bilingual Arabic and English credentials display with the same layout, fonts, and field placement recipients received. Verifiers see what was issued, not a stripped-down text summary.

Organisations on Starter and above can remove Mutamad branding from the verify page alongside credentials. Free tier verify pages carry the Mutamad mark. Pro and Business tiers also support bring-your-own SMTP for delivery; verification itself is included at every plan level.

Verification supports trust for training programmes, professional certifications, and employee recognition credentials. A hiring manager who receives a PDF attachment can follow the verify link or enter the code on mutamad.io/verify to confirm the record matches the document. Years later, the same URL still works.

Mutamad does not expire verification links when a subscription downgrades or cancels. Issued credentials remain verifiable. After a paid period ends, the organisation may return to Free limits for new issuance, but existing verify URLs continue to resolve. That permanence is intentional: credentials outlive billing cycles.

Public verification requires no account. Verifiers enter a code on the verify page or follow a link embedded in a PDF or WhatsApp message. The page loads the credential status and visible fields within seconds. For bilingual credentials, Arabic and English content appears in the same layout the recipient received, so visual comparison between attachment and live page is straightforward.

Issuers can direct verifiers to a dedicated verify path on the landing site or embed codes in credential footers. The verify experience is separate from the authenticated app: no login, no tenant header, no internal identifiers exposed. Only the fields configured for public display appear, preserving employee privacy while still confirming authenticity.