PGP / GPG Public Key Inspector
PGP / GPG Public Key Inspector: Parses RFC 4880 OpenPGP packet headers (Public Key Packet, User ID Packet), extracts key fingerprint and creation date.
About this pgp / gpg public key inspector
PGP / GPG Public Key Inspector — browser-based utility.
How this tool works
Implements client-side PGP / GPG Public Key Inspector operations. Parses RFC 4880 OpenPGP packet headers (Public Key Packet, User ID Packet), extracts key fingerprint and creation date specifically designed for a security analyst inspects an openpgp / gpg public key block to check key id and user identity.
- PEM Armor Stripping & DER Decoding: Strips '-----BEGIN CERTIFICATE-----' headers and decodes Base64 to raw ASN.1 DER binary bytes.
- ASN.1 Structure Traversal: Parses the TBSCertificate sequence, extracting serial numbers, signature algorithms, and X.500 distinguished names.
- Extension Extraction: Decodes X.509v3 extensions, extracting SAN DNS names, basic constraints (CA flag), and key usage flags.
- Diagnostic Reporting: Computes SHA-256 fingerprint, checks expiration status against the current date, and warns if certificates are expired or self-signed.
Worked example
Scenario: Read the armor metadata of a supplied OpenPGP public-key block.
Sample input:
Processing: Matches the ASCII armor and counts non-header body lines without parsing OpenPGP packets.
Illustrative output:
Limits and verification
Rejects corrupted PEM files with invalid Base64 characters or missing encapsulation boundaries. Warns users when inspecting self-signed root certificates or certificates with weak 1024-bit RSA keys.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the PGP / GPG Public Key Inspector workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
Which PGP input shape does the inspector require?+
It requires one ASCII-armored block with matching BEGIN and END PGP labels. Without armor it raises an error instead of parsing arbitrary key material.
Which metadata does the inspector report?+
It reports armored status, the armor type, non-header body line count, whether a Version header appears, and whether a 40-hex-character fingerprint pattern is present.
What did the browser fixture verify?+
A PUBLIC KEY BLOCK with Version: CZOA and one body line returned that type, bodyLines 1, hasVersionHeader true, and fingerprintAvailable false.
Does it verify OpenPGP trust or signatures?+
No. The implementation explicitly limits itself to armor metadata. It does not parse packets, validate a fingerprint, or verify key trust or signatures.