Paste a block starting with
-----BEGIN PGP PUBLIC KEY BLOCK-----
Ready to parse
Paste a PGP key block and click Parse Key// extract fingerprint, algorithm, and uid from pgp keys
Parse armored PGP public keys to extract fingerprint, key ID, algorithm, bit length, creation date, expiry, and User IDs. Free browser-based tool.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Ready to parse
Paste a PGP key block and click Parse KeyExport or copy an armored PGP public key block from your keyring, GPG, or any keyserver.
Paste the full armored block including the BEGIN / END headers into the input field.
Copy fingerprint, check algorithm, review UIDs and subkeys — all extracted instantly in your browser.
The PGP Key Info Parser decodes armored OpenPGP public key blocks entirely in your browser. It extracts the fingerprint, key algorithm, bit length, User IDs, creation date, expiry, and any subkeys — with zero server upload.
No. All parsing happens entirely in your browser using JavaScript. Your key data never leaves your device. This tool is 100% client-side.
A fingerprint is a unique hash (typically SHA-1 for older keys or SHA-256 for newer) of the public key. It's used to verify key identity and prevent impersonation attacks. Always compare fingerprints out-of-band before trusting a key.
OpenPGP supports RSA (1024–4096 bit), DSA, ElGamal, and modern elliptic curve algorithms like Ed25519, Curve25519 (X25519), and ECDSA/ECDH on NIST curves. Ed25519 and Curve25519 are recommended for new keys.
A User ID (UID) contains identity information like name and email address, formatted as Name <email@example.com>. A key can have multiple UIDs. Each UID can be independently signed and certified by others.
Subkeys are secondary keys tied to a primary master key. They are commonly used to separate signing and encryption duties, so the master key can be kept offline while subkeys handle day-to-day operations.
This tool is designed for public key blocks (BEGIN PGP PUBLIC KEY BLOCK). You should never paste private keys into any web tool. Private key data should remain strictly offline and protected.
A PGP Key Info Parser is a tool that reads an armored OpenPGP public key block and extracts the metadata embedded within it — including the key fingerprint, algorithm, bit length, creation date, expiry date, User IDs (UIDs), and any subkeys. Instead of using the GPG command line or specialized desktop software, you can paste any armored key and get a structured summary instantly.
💡 Looking for premium web development assets? MonsterONE offers unlimited downloads of templates, UI kits, and developer assets — worth checking out.
PGP keys are binary data encoded in Base64 and wrapped in ASCII "armor" headers. An armored public key block begins with -----BEGIN PGP PUBLIC KEY BLOCK----- and ends with -----END PGP PUBLIC KEY BLOCK-----. Inside, the key material follows the OpenPGP packet structure defined in RFC 4880 and its successor RFC 9580.
The binary packets inside encode multiple pieces of information: the primary key type, creation time, public key algorithm parameters, and then a sequence of User ID packets and signature packets. This parser decodes those packets to present readable information without requiring GPG or any command-line tools.
The fingerprint is a cryptographic hash of the public key material. For version 4 keys (the most common), it is a 160-bit (40 hex character) SHA-1 hash. For version 6 keys (the newer RFC 9580 format), it is a 256-bit SHA-256 hash. The fingerprint is the canonical way to identify a key — two different keys cannot share the same fingerprint.
When sharing your key, it is good practice to share the full fingerprint alongside the key or key ID so that recipients can verify they received the correct key. The short 8-character Key ID is derived from the last 8 characters of the fingerprint and can be used for lookups, though it is susceptible to collision attacks (two keys can share the same short ID). Always verify the full fingerprint.
OpenPGP supports multiple public key algorithms, each with different security and performance characteristics:
A PGP key is actually a bundle: a primary key plus zero or more subkeys. The primary key certifies the UIDs and other keys. Subkeys handle specific tasks such as signing documents or encrypting messages. This separation allows users to keep the master key offline (reducing exposure) while using subkeys for daily operations. If a subkey is compromised, only that subkey needs to be revoked — the primary key and web of trust remain intact.
This tool lists all subkeys found in the key block, showing each subkey's algorithm, bit length, key ID, creation date, and expiry.
A User ID packet contains a free-form string, conventionally formatted as Full Name <email@example.com>. A key can have multiple UIDs — for example, one for a personal email and another for a work email. Each UID can accumulate third-party certifications (signatures from other keys) that form the OpenPGP Web of Trust.
When you receive a PGP key, checking the UIDs lets you confirm who the key belongs to. Cross-referencing UIDs against keyservers (like keys.openpgp.org) can help confirm that the key is well-known and trusted by others.
PGP keys can optionally have an expiry date. This is good practice: an expired key signals that it should no longer be used for new encryption, which limits the damage from key compromise. Expiry can be extended by the key owner by updating the self-signature, without generating a new key. This tool shows both the creation date and expiry date (if set) for the primary key and all subkeys.
Historically, inspecting PGP keys required running gpg --import followed by gpg --list-keys or gpg --fingerprint. That workflow is inaccessible to many users who do not have GPG installed. This browser-based parser offers an instant alternative: paste the key, see the metadata. Nothing is uploaded to a server. The parsing code runs entirely in your local JavaScript engine, making it safe to use even with sensitive key material (though as a general rule, you should never paste private keys into web tools).