Create and verify signatures, and generate keys — all client‑side
PGP (RFC 4880) provides confidentiality (encryption), authenticity (signatures), and integrity.
Common issues: invalid signature (wrong key/tampered), wrong passphrase, mixed line-endings.
or click to browse
or click to browse
or click to browse
Every coffee helps keep the servers running. Every book sale funds the next tool I'm dreaming up. You're not just supporting a site — you're helping me build what developers actually need.
Q: What is the difference between cleartext and detached signatures?
A: Cleartext signatures keep the message human‑readable with an inline signature block; detached signatures are separate .asc/.sig files used to verify any file without changing it.
Q: How do I verify a signed message?
A: Paste the signed text and the signer’s public key in the Verify tab and click Verify. You’ll see validity, signer KeyID, fingerprint, UID and the signature time.
Q: How do I verify a file with a detached signature?
A: Select the original file and the .asc/.sig signature, paste the signer’s public key, then verify. The suite lists each signature and status.
Q: Can I recover my private‑key passphrase if I forget it?
A: No. Passphrases are not recoverable. Generate a new key pair and distribute the new public key; revoke the old key if possible.
Q: Is this secure? Do keys leave my device?
A: All operations happen client‑side in your browser using OpenPGP.js. Keys and files never leave your device.
Q: How do I confirm I have the right public key?
A: Compare the fingerprint over a trusted channel (in‑person, voice, QR, business card) before trusting signatures or encrypting to the key.
Q: Can I sign with multiple keys or add notations?
A: Advanced options like multi‑sign and notations are planned. For now, you can sign with one key and verify multi‑signature messages.