A digital credential can look genuine and still be unusable because it has expired, been suspended, or been revoked. This checklist explains how to check credential status, interpret issuer responses, and document a decision before using a certificate for hiring, onboarding, access renewal, an audit, or another high-impact process.
Overview
Checking whether a digital credential is trustworthy involves more than reading its name or opening a QR code. You need to establish which credential you are reviewing, confirm its validity period, check the issuer’s status mechanism, and understand what a “valid” response actually means.
The workflow differs by credential type. An X.509 certificate used for TLS or enterprise authentication may publish revocation information through a certificate revocation list (CRL) or Online Certificate Status Protocol (OCSP). A digitally signed document may rely on the signer’s certificate, a trusted timestamp, and the validation features of the document software. A verifiable credential may use an issuer-controlled status list or a public verification endpoint. A training or employee certificate may instead use a credential ID and an issuer lookup page.
Expiration and revocation are separate conditions:
- Expired: The credential is outside its stated validity period. It may still be authentic, but it should not be treated as currently valid unless the relying process explicitly permits historical credentials.
- Revoked: The issuer has withdrawn the credential before its scheduled expiration. This can happen after a key compromise, an error in issuance, a change in eligibility, or another issuer-defined event.
- Suspended: The issuer has temporarily disabled or placed a credential under review. Suspension rules vary, so do not treat it as equivalent to either valid or permanently revoked.
- Unknown or unverifiable: The checker could not obtain or interpret a status result. This is not proof that the credential is revoked, but it is also not proof that it is valid.
For related checks, see the guide to certificate revocation status, OCSP, CRL, and validation errors. If your task involves identity proofing rather than a previously issued credential, use the identity proofing and KYC workflow as a separate reference.
Checklist by scenario
For an online certificate or X.509 credential
- Capture the certificate details. Record the subject name, issuer, serial number, validity dates, and public key or fingerprint. For a website certificate, verify the hostname and inspect the complete chain, not only the leaf certificate.
- Check the validity window. Confirm that the relevant date and time fall between the “not before” and “not after” values. Check the system clock on the validating device if the result appears inconsistent.
- Locate status endpoints. Inspect the certificate extensions for CRL distribution points and OCSP responder information. A certificate validator or X.509 certificate checker can help expose these fields.
- Query the issuer’s status service. Use the issuer’s documented endpoint or a trusted validation tool. Preserve the response time and result if the decision may need to be audited.
- Validate the chain and trust. Confirm that the chain leads to a trusted root for the intended environment, that intermediates are present, and that key usage and name constraints fit the use case. A status response alone does not prove that the certificate is suitable.
For a website-specific process, the SSL certificate checker guide covers expiry, hostname, chain, and TLS errors. Do not confuse a successful browser connection with a complete archival or compliance-grade validation record.
For a training, employee, or professional certificate
- Find the credential ID. Look for a certificate number, recipient identifier, issue date, issuer name, or QR code. Avoid relying on a recipient’s name alone because names can be duplicated or entered inconsistently.
- Use the issuer’s official lookup. Navigate to the issuer’s site independently rather than trusting an unfamiliar link in an email or document. Enter the credential ID exactly as shown.
- Compare the returned fields. Check the recipient, title, issue date, expiration date if present, issuer, and current status. A matching ID with mismatched details requires clarification.
- Ask about status meanings. Determine whether the issuer distinguishes active, expired, suspended, superseded, and revoked credentials. Keep the issuer’s explanation with the verification record.
A QR code can make lookup easier, but it is not by itself evidence of authenticity. Scan it only with a trusted device, inspect the destination domain, and compare the returned data with the credential. The training certificate verification checklist provides a broader authenticity workflow.
For a digitally signed document or verifiable credential
- Preserve the original file. Do not validate a screenshot, re-exported PDF, or copied text when the original signed object is available.
- Verify the signature and integrity. The validation tool should indicate whether the signature matches the document and whether the content changed after signing. If a hash is supplied, compare it using a trusted hash tool.
- Check the signer and issuer. Confirm that the signing certificate or credential was issued to the expected organization or person and chains to a trust source appropriate for the task.
- Check status and time. Review expiration, revocation, suspension, and any trusted timestamp. A signature may remain mathematically intact even when the signer’s certificate is no longer valid for new transactions.
For document-specific steps, read how to verify a digitally signed document and check for tampering. For an organization-owned lookup service, a public certificate verification page can provide a clearer audit trail than an informal email confirmation.
CRL versus OCSP versus status lists
| Method | How it works | Useful checks | Limitations |
|---|---|---|---|
| CRL | The issuer publishes a signed list of revoked certificate serial numbers. | Offline or batch validation; environments that cache issuer data. | Lists can be large or stale, and availability may affect validation. |
| OCSP | A validator asks an issuer-controlled responder about a specific certificate. | Near-real-time status checks for supported PKI workflows. | Requires responder access and correct interpretation; an unavailable response is not automatically a revocation. |
| Status list | A credential ecosystem publishes encoded status information that a verifier maps to a credential or entry. | Modern digital credentials and scalable privacy-conscious status checks. | Format, caching, privacy behavior, and status meanings depend on the implementation. |
These methods answer a status question, not every trust question. Always combine status with issuer identity, credential purpose, signature integrity, validity dates, and the requirements of the relying organization.
What to double-check
- Use the correct credential. Similar names, renewed certificates, and replacement credentials can make an old identifier look relevant when it is not.
- Check the issuer’s authority. A result from a lookalike domain or an unofficial database should not be treated as an authoritative certificate authenticity check.
- Read the complete response. “Good,” “valid,” or a green indicator may refer only to one layer, such as signature integrity. Review warnings about trust, purpose, chain, policy, and dates.
- Consider caching. CRL, OCSP, and status-list data may be cached. Record when the response was retrieved and follow the issuer’s guidance on freshness.
- Protect personal data. Credential lookups can expose names, IDs, or employment information. Use the minimum data needed, restrict access to verification logs, and avoid posting credential contents in public issue trackers.
- Record an evidence trail. Save the credential identifier, issuer, result, timestamp, tool or endpoint used, and any follow-up confirmation. Do not store more personal information than the process requires.
Common mistakes
Confusing expiration with revocation. An expired credential does not necessarily indicate fraud, while a revoked credential may be invalid even before its printed expiration date.
Assuming no response means valid. A network failure, blocked OCSP request, unavailable CRL, or unsupported status-list format should be recorded as an inconclusive check. Apply the organization’s fail-open or fail-closed rule rather than guessing.
Checking only the leaf certificate. A certificate can have acceptable dates while its chain, trust anchor, hostname, or intended key usage is wrong.
Trusting a QR destination without inspection. A QR code can point to an unofficial page, a copied credential, or a page that does not display current status. Verify the domain and returned fields.
Ignoring replacement or suspension states. Issuers may replace credentials after an update or temporarily suspend them during review. Ask the issuer what each state means before making a hiring, access, or compliance decision.
When to revisit
Revisit a credential status before granting access, accepting a qualification, completing onboarding, renewing trust, or relying on a document for an audit. Repeat the check when the credential’s expiration date is near, when an issuer announces a key or credential incident, when a certificate is renewed or replaced, or when the verification tool and workflow change.
Organizations should review their status-checking runbook before seasonal planning or onboarding cycles. Confirm that issuer endpoints, trust stores, validation libraries, status-list parsers, and escalation contacts are still current. After a failed or inconclusive check, preserve the original evidence, contact the issuer through an independently verified channel, and postpone the decision when the risk of relying on an unverified credential is material.
Reusable final checklist: identify the credential, verify its dates, confirm the issuer, check the appropriate revocation or status mechanism, validate the chain or signature, compare the returned details, interpret the status correctly, record the result, and set a date for the next review.