Skip to content
CertKing

Guide

Verification and security.

Public verification reads one certificate record from the server. The browser never reads the certificate database directly.

What a verification page shows

  • Recipient name and the issuing organisation.
  • The certificate ID and issue date.
  • Status: issued and not revoked, revoked with a reason, or not valid.
  • A short prefix of the stored PDF hash, once a PDF has been generated.
  • A download button for the sealed PDF while the certificate is valid.

Verification needs no account. Recipient email, phone, and custom fields are stored on the record but are not displayed on the public page.

How the seal works

When a certificate PDF is generated, CertKing computes a SHA-256 hash of the exact bytes and stores it on the certificate. The verification page displays a short prefix as a reference. The PDF itself does not print the hash yet.

PDF upload comparison is not available yet

The planned upload-and-compare verifier has not shipped. Today the certificate ID is the reliable check. A hash prefix alone is not proof that a particular file matches — anyone can copy the prefix.

Access control

  • Every dashboard query and mutation checks workspace membership and permission on the server.
  • Invites are single-use tokens; the accept step requires a signed-in account.
  • API keys are stored only as SHA-256 hashes, shown once at creation, and revocable. Scopes are recorded but not enforced because no public endpoint exists yet.
  • The WhatsApp inbound webhook fails closed when no secret is configured and compares a shared secret on every request.

Data and deletion

Settings can generate a JSON export of certificates, templates, and members in the browser. Workspace deletion is not available in the app yet; email support@certking.dpdns.org from the owner account and the workspace, certificates, and audit records are removed.

Not available yet

  • Per-field privacy controls or hiding a certificate from public listing.
  • Custom verification domains or white-label verification pages.
  • PDF upload verification and automated tamper reports.
  • SOC 2, ISO 27001, DPDP, or GDPR certification. CertKing aims to minimise stored data but is not certified.