← All Tools
PGP / GPG Key Lookup
Find an OpenPGP public key by email, fingerprint, or 16-hex key ID. The lookup is proxied through this server (your IP is never forwarded) and the returned key is parsed in your browser to reveal user IDs, aliases, subkeys, capabilities, and the key timeline.
Privacy. Queries are sent to public keyservers (
keys.openpgp.org, then keyserver.ubuntu.com if not found). The browser never contacts those servers directly — the request is proxied server-side so your IP stays private. Parsing of the returned key happens locally in your browser.
Examples: alice@example.com · 3AA5C34371567BD2 (16-hex key ID) · 1A09 1C12 ... full 40-char fingerprint. Spaces / colons / leading 0x are ignored.
What you get
- All user IDs on the key — real name, email, and comment parsed out separately. A single PGP key often carries several aliases (work email + personal email + handle).
- Fingerprint & long key ID for the primary key and every subkey.
- Algorithm (RSA bit length, curve name for ECC) and key flags: certify, sign, encrypt, authenticate.
- Timeline — creation date and expiration for the primary key and each subkey, so you can see when subkeys were rotated.
- Source provenance — which keyserver answered, plus the trace of which servers were tried.
Important caveats
- A fingerprint match does not establish identity. Always confirm the fingerprint with the owner via a separate trusted channel.
keys.openpgp.orgonly publishes user IDs whose email was verified through a confirmation message; some keys appear with no user IDs there.keyserver.ubuntu.comdoes not verify emails — anyone could have uploaded a UID claiming any address.- Keyservers expose creation and expiration, not the full signature graph. For Web-of-Trust analysis use
gpg --recv-keysandgpg --check-sigslocally. - Short 8-hex key IDs are not accepted — they are collidable. Use the 16-hex long form or the full fingerprint.