OpenPGP Key Inspector
Inspect fingerprints, user IDs, subkeys and expiry from armored or binary OpenPGP keys without contacting a keyserver.
Identify the key you actually received
The inspector reads public fingerprints, key IDs, creation times, algorithm details, user IDs and subkeys using pinned OpenPGP.js 6.3.2. It accepts ASCII armor or a binary file; pasted binary bytes use Base64 or hex. Up to 20 keys, 500 packets per key and 1 MiB of binary input are allowed.
Private key packets can be inspected without a passphrase. The tool converts them to public metadata and marks privateMaterialPresent; it never exports secret parameters or decrypts a private key. The sample is a generated example identity at example.invalid, not a trusted person.
Expiry, revocation and identity
The optional inspection time must be a UTC ISO timestamp such as 2026-10-25T00:00:00Z. Self-signature and binding checks use that time. Expiration metadata is selected by the library from supplied signatures; unknown and never-expiring are reported separately. This is not a complete historical key-state reconstruction.
Revocation checks see only the packets you supply. No keyserver, transparency log, external certification or ownership database is queried. A valid self-signature means internal consistency, not that the claimed name or email belongs to the sender; compare the full fingerprint through a separate trusted channel.
Reference
Questions & answers
Does a matching short key ID prove identity?
No. Use the complete fingerprint and an independent trusted channel; this page cannot establish ownership.
Why can expiry be unknown?
Missing, invalid or revoked signatures may prevent the library from determining a reliable expiry. Unknown is not reported as never.
Is my input uploaded?
No. Processing runs in your browser. Engines load from this site; the tool does not send input to a processing API or save it. Clear removes the visible input and result.