Parse and analyze GPG/PGP public keys to display key ID, fingerprint, user IDs, subkeys, and expiration.
An OpenPGP public key is more than a single identifier. GPG Key Analyzer reads the packet structure of submitted public-key material and separates the primary key from its User ID records and subkeys. It reports the full fingerprint, shorter key ID, attached identities, and recorded expiration information so you can inspect what the key actually contains. The common surprise is that a User ID is only an identity claim carried by the key. Its presence does not prove that the named person or email address controls the key.
An OpenPGP public-key certificate can contain a primary public key, multiple User ID packets, certification signatures, public subkeys, and subkey-binding signatures. The analyzer parses these related records and presents them as parts of one key. This distinction matters because a User ID is an identity claim rather than a key, while a subkey can have its own fingerprint, key ID, creation time, and expiration.
The analyzer derives the fingerprint appropriate to the key packet's OpenPGP version and displays the corresponding shorter key ID. It also reads expiration information associated with the primary key and subkeys when that information is present. Analysis occurs in the browser, so pasted key material and any email addresses embedded in User IDs are not uploaded for processing.
No. It can show the identity text and structural relationships encoded in the public-key certificate, but ownership is a separate trust decision. Confirm the full fingerprint using a trusted source or communication channel. A familiar name, matching email address, valid packet structure, or unexpired date is not sufficient proof by itself.
They serve different identification needs. The fingerprint is the fuller identifier derived from the public-key packet according to its OpenPGP version. The key ID is shorter and easier to display or search, but it provides less identifying information. Use the full fingerprint when the distinction is security-sensitive, especially when accepting a key for the first time.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.