Public signature verification
Anyone with the signed payload + public key can verify a signature — no login, no account.
What it does
Signatures are useless if they can only be checked by the issuer. DocSign ships a public verify page that takes a public key (or a signer's email), the payload, and a signature; runs Ed25519 verification client-side; and shows pass/fail plus the audit trail server-side has stored about that key.
How it works
- 1
Visit /verify (no login).
- 2
Paste the payload, the signature, and either the signer's public key or their fingerprint.
- 3
The page runs Ed25519 verification in-browser using @noble/ed25519.
- 4
DocSign also cross-checks the key against its registered + email-confirmed set and shows the audit row.
Why it matters
- Auditors and counterparties don't need DocSign accounts to verify your signatures.
- Open standard primitives — Ed25519 + SHA-256 — so verification works in any language with no DocSign dependency.
- Fingerprint mismatch flags impersonation: a forged key won't match the server-registered one.
Want to try it?
Most features are available the moment you sign up. No card required.
Related features
Signing requests
Hand someone a one-time link; their browser signs and the signature lands in your app via webhook.
Three key-storage modes
Pick where the private key lives — your machine, your browser, or end-to-end encrypted on the server.
Tamper-evident audit log
Every security-relevant event is recorded with user, action, IP, user-agent, and timestamp.