Credential verification

Check a certificate.
Don’t trust a PDF.

A printed certificate is a copy. The public record is the source of truth. Paste an EduByte credential ID or scan the QR code to confirm the issuer, the dates and the current status.

Try a sample:

Paste the ID printed on the certificate, or scan its QR code to land directly on the public record.

Result states:ValidRevokedExpiredSupersededUnknown

Verification runs server-side against the live EduByte registry. Sample IDs are clearly labelled demo and never represent a live credential.

How it works

Four checks, in order.

If any check fails, the result is not reported as valid.

01

Scan or paste

The QR code on a certificate encodes a stable HTTPS verification URL. You can also type the credential ID.

02

Registry check

The verifier looks up the credential in EduByte’s issuer registry and confirms the record is current.

03

Status check

The live record shows whether the credential is valid, revoked, expired or superseded — never just “looks valid”.

04

Minimal data

Only display-safe claims are returned. No email addresses, birth dates, transcripts or identity documents.

Result states

Every outcome is explicit.

A missing record, a revoked record and an unavailable service are all different. The verifier never guesses, and it never reports “valid” when it cannot check.

Valid

Issued by EduByte and currently valid. Only minimal display claims are shown.

Revoked

Previously issued but no longer valid. A safe reason category may be shown.

Expired

Issued but past its validity date, where an expiry applies to the program.

Superseded

Replaced by a newer credential. The successor is linked where policy allows.

Unknown

No matching issued record. The page avoids detailed enumeration hints.

Unavailable

The service or status check failed. This is never reported as valid.

Built to survive a second look.

Unique 128-bit opaque IDs. Signed issuance. Revocation with an audit trail. Standards-aligned credentials. No invented cryptography, no “fraud-proof” promises.

Explore certifications
Verification FAQ

Common questions.

If something does not look right, do not treat the credential as valid. Contact credential operations with the ID and a screenshot.

Contact credential operations
What does a valid result actually prove?

It proves that EduByte’s issuer registry contains this credential and that it is currently active. It does not prove that the person showing you the screen is the named holder.

How do I check a printed certificate?

Scan the QR code or type the credential ID from the certificate into the verifier. The printed PDF is a human-readable copy; the online record is the source of truth.

What should I do if a credential is revoked?

Treat it as no longer valid. The record will show the reason category and, where policy allows, a successor credential.

Can a credential be copied and reused?

A QR code proves issuance, not ownership. For higher-assurance credentials, request a matching photo ID and confirm the displayed name with the holder.

Is this page a guarantee that the person is the holder?

No. A QR code proves that a credential was issued; it does not verify who is presenting it. For higher-assurance checks, ask for matching photo ID and confirm the display name.