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
Parses RFC 4880 OpenPGP packet headers (Public Key Packet, User ID Packet), extracts key fingerprint and creation date Runs entirely in-memory using Web Crypto primitives to keep sensitive tokens, certificates, and cryptographic keys secure from third-party interception.
Encoding & cryptographic principles
Reads ASCII-armored PGP block metadata such as its armor label, body-line count, version-header presence, and whether fingerprint-looking text appears. It does not parse OpenPGP packets, verify trust, or verify signatures.
Worked verification example
Scenario: Read the outer armor metadata of a synthetic PGP-labeled text block; its body is not a valid public key.
Sample input:
Processing: Matches the armor labels and counts non-header body lines without parsing OpenPGP packets or validating the Base64 body.
Illustrative output:
Security parameters & input constraints
This is a text-pattern inspection only: it does not decode OpenPGP packets, verify fingerprints or signatures, assess trust, check key strength or decrypt messages. A 40-hex match is not a verified fingerprint.
Cryptographic digests, encoded strings, and signatures generated by PGP / GPG Public Key Inspector should be verified against target authentication systems before production use.
Client-side Web Crypto boundary
Key derivation, hashing, and encoding in PGP / GPG Public Key Inspector execute in local memory using Web Crypto APIs without remote socket transmission.
Cryptographic specifications & RFC standards
Technical specifications and cryptographic RFC standards governing algorithms and key representations:
PGP / GPG Public Key Inspector verification · Audit standards
How to use it
- Paste ASCII-armored PGP public/private key or message text.
- Find a matching BEGIN/END armor block and count non-header body lines.
- Read armor type, Version-header flag and 40-hex-text flag in JSON.
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 example can I run locally?+
A PUBLIC KEY BLOCK with Version: CZOA and one body line returned that type, bodyLines 1, hasVersionHeader true, and hasFingerprintLikeText 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.