Security

PEM Inspector

Paste or drop PEM text to see what each block is: certificate, public key, private key, request or something else. Everything is read in your browser, and private key material is never displayed.

Private keys never leave this page. Everything is decoded in your browser. Nothing is uploaded, sent to a server, written to the URL, saved in browser storage or logged, and there is no analytics. A private key is only identified (type and size), is never displayed or copied, and is removed from the input box. Parsed is not verified: this tool reads structure only. It does not check signatures against a trust store, revocation, expiry policy or whether a key matches a certificate.
Before you paste: prefer public certificates and public keys. Do not paste a production private key into any web page. If a private key is pasted anyway it is identified only and removed from the box, but treat a real key that has been pasted into a web page as exposed.

Drag and drop a PEM or DER file here (.pem, .crt, .cer, .key, .csr, .der), or choose one.

Ready. Paste PEM text, choose a file or drop one here. Nothing is uploaded.

What it does

A PEM file is Base64 text between -----BEGIN …----- and -----END …----- lines, wrapping binary DER data. This tool finds every block in what you paste, decodes it and tells you what it is, how it is encoded and how big it is, and shows the details it can read safely.

Supported blocks

  • Certificates (CERTIFICATE, TRUSTED CERTIFICATE): subject, issuer, validity, serial, public key, signature algorithm and SANs, using the same parser as the X.509 Certificate Inspector. Chains are listed in order.
  • Public keys: PUBLIC KEY (SubjectPublicKeyInfo) and RSA PUBLIC KEY (PKCS#1): algorithm, key size, exponent or curve.
  • Private keys (identified only): PKCS#8 PRIVATE KEY, ENCRYPTED PRIVATE KEY, PKCS#1 RSA PRIVATE KEY, EC PRIVATE KEY, DSA PRIVATE KEY, OpenSSH keys and traditional OpenSSL encrypted keys.
  • Others: certificate requests (CSR), CRLs, PKCS#7, DH and EC parameters. Unknown labels are still recognized and sized, with an ASN.1 outline when the data is DER.

Parsed is not verified

Decoding Base64 and reading a structure is not analysis of whether anything is genuine. Every block is marked Parsed locally — not cryptographically verified. The chain workspace does check each certificate's signature against the certificate it links to, when that certificate is in your input, using your browser's Web Crypto. A valid result means only that the linked key made the signature. This tool does not build a path to a trust store, check revocation (CRL or OCSP), match host names, evaluate name constraints, path length or policies, check Certificate Transparency, decrypt anything, or test that a private key belongs to a certificate.

How private keys are handled

  • Only public facts are read from a private key: its type, modulus size or curve, and whether it is encrypted. The key bytes are never shown, copied, downloaded or handed to another tool, and the decoded buffer is overwritten after use.
  • The key text is removed from the input box as soon as it has been identified. Encrypted keys stay encrypted: nothing is decrypted.
  • Nothing is uploaded or put in the URL, and nothing is written to localStorage, sessionStorage or cookies. There is no analytics and no logging.
  • No web page can guarantee that every trace is erased from browser memory, undo history or the clipboard. For a real production key, inspect it offline with openssl and treat any key you have pasted into a web page as exposed.

Using the tool

  • Paste, choose or drop: PEM text, a PEM bundle, or a binary DER file. Text before, between and after the blocks is ignored. Line endings (LF, CRLF), indentation and wrapped Base64 are accepted.
  • Block navigator and filter: jump to any block, and filter every decoded field by text (for example a SAN, a curve or a fingerprint).
  • Certificates: names, SANs (DNS, IP, email, URI), serial, validity in UTC and your local time with the time remaining or elapsed (from your device clock), key and signature algorithms, key identifiers, key usage, policies, CRL, AIA and OCSP locations, with critical flags, and SHA-256, SHA-1, SHA-512 and public key (SPKI) fingerprints.
  • Chain workspace: roles (leaf, intermediate, root), issuer links by name and key identifier, duplicates, missing or ambiguous issuers, ordering problems and a tree, with a signature check on each link. It says plainly that this is not validation.
  • Compare: two certificates field by field, or a fingerprint you paste against every block.
  • Export: public metadata as JSON, public keys as SubjectPublicKeyInfo PEM or DER (an RSA PKCS#1 key is converted), and the chain summary as text. Each value also has its own copy button.
  • Hand-off: a certificate can be opened in the X.509 Inspector, a public key sent to the JWT Decoder as the verification key, and the decoded bytes of any public block sent to the Hex Viewer, File Magic Number Inspector or Hash Generator. Only public data you click on is sent, and only within your browser tab.
  • Malformed input: an invalid Base64 character is reported with its line and column, and a missing END line, mismatched labels, truncated data or malformed ASN.1 are each named, with the byte offset where it can be known.
  • Limits: up to 8 MB of input, 500 blocks and 1 MB of decoded data per block. Processing runs in the page and takes a fraction of a second for hundreds of certificates. Web Crypto cannot check SHA-224 signatures or curves other than P-256, P-384, P-521 and Ed25519; those are reported as not checked.

Related

For a certificate’s full detail use the X.509 Certificate Inspector. For tokens signed with these keys see the JWT Decoder and JWT Generator. To convert the Base64 yourself use the Base64 tool.

Share this tool

Your data is not included in this link.