Use this inspection tool to examine encoded security material without changing it or treating successful parsing as proof of trust.

PEM text

Required string. Text containing one or more "-----BEGIN LABEL----- ... -----END LABEL-----" blocks.

The cited overview of Privacy-Enhanced Mail supplies background for the terminology and domain context used by this tool.^[1]

Inspect PEM armored text for block metadata only: BEGIN/END labels, decoded byte counts, and RFC 1421 header line count; no ASN.1 parsing. Inputs are interpreted exactly in the displayed units and the calculation returns the following fields without presentation rounding.

Block count

Returned integer. Number of complete PEM blocks found.

Decoded byte counts

Returned list. Decoded byte length of each block's base64 body, in order.

Header line count

Returned integer. Non-empty body lines that are not base64, such as Proc-Type or DEK-Info headers.

Labels

Returned list. BEGIN label of each block in order.

• Readable metadata does not establish identity, trust, revocation status, key possession, algorithm safety, or suitability for a particular protocol.
• Use finite inputs in the displayed units, preserve source measurements and assumptions, and independently verify consequential decisions.

Verify the complete trust chain and intended usage with current platform or protocol tooling before making a security decision.

• Base64 Decoder

  Decode canonical Base64 into UTF-8 text.

• Base64 Encoder

  Encode UTF-8 text as canonical Base64 text.

• Hex to Base64 Converter

  Decode a hexadecimal string into bytes and re-encode it as Base64.