Skip to content
ToolsMinify logo
Developer Tools

PEM Certificate Decoder

Paste a PEM-encoded X.509 certificate and read subject, issuer, serial number, validity window, Subject Alternative Names (SANs), SHA-1 / SHA-256 fingerprints, signature…

About PEM Certificate Decoder

Paste a PEM-encoded X.509 certificate and read subject, issuer, serial number, validity window, Subject Alternative Names (SANs), SHA-1 / SHA-256 fingerprints, signature algorithm, and public key size - entirely in your browser. Nothing is uploaded and this page never contacts a remote host for SSL expiry. Use Load sample to try a demo cert, or paste a leaf from your chain (the first BEGIN CERTIFICATE block is decoded). Pair it with the Base64 Encoder / Decoder when you need to re-wrap DER bytes, or the Hash Generator for other digests.

How to Use PEM Certificate Decoder

  1. Paste a PEM block that starts with -----BEGIN CERTIFICATE----- (or click Load sample).
  2. If you paste a chain, only the first certificate is decoded.
  3. Read subject, issuer, serial, not before / not after, SANs, and fingerprints.
  4. Copy the summary when you need the fields in a ticket or change request.
  5. Everything runs locally - the PEM never leaves this tab.

PEM Certificate Decoder Examples

Leaf TLS certificate

A server leaf PEM shows CN / O / C in subject, the issuing CA in issuer, DNS and IP SANs, and SHA-256 fingerprint for pinning notes.

Validity window check

Not before and not after are shown as ISO timestamps, with a local-clock status (valid now / not yet valid / expired) - no remote SSL probe.

SAN inventory

Subject Alternative Names list DNS names, IPs, emails, and URIs when present so you can confirm hostname coverage.

Fingerprint for docs

SHA-1 and SHA-256 fingerprints are colon-separated uppercase hex, matching common openssl x509 -fingerprint output style.

Reject private keys

BEGIN PRIVATE KEY or CERTIFICATE REQUEST blocks are rejected so you only decode public certificates.

Common Use Cases

  • Inspect a leaf PEM before installing it on a load balancer
  • Confirm DNS SANs match the hostnames you expect
  • Copy SHA-256 fingerprints into runbooks or pin configs
  • Check not-before / not-after without openssl on the machine
  • Decode a pasted chain and review the first (leaf) certificate

Frequently Asked Questions about PEM Certificate Decoder

How do I use this PEM certificate decoder?
Paste a -----BEGIN CERTIFICATE----- block (or click Load sample). The page shows subject, issuer, validity, SANs, and fingerprints immediately. Nothing is uploaded.
What is a PEM certificate?
PEM is a Base64 encoding of DER-encoded X.509 data between BEGIN CERTIFICATE and END CERTIFICATE markers. It is the common text form for TLS certificates.
Do you check remote SSL expiry?
No. This tool only decodes the PEM you paste. It does not connect to any host, fetch live certificates, or perform OCSP / CRL checks.
Is my certificate uploaded?
No. Decoding runs only in this tab. The PEM never leaves your browser.
What if I paste a certificate chain?
Only the first BEGIN CERTIFICATE block is decoded (usually the leaf). Paste intermediate or root blocks separately if you need those fields.
Can I paste a private key or CSR?
No. Private keys and certificate requests are rejected. Paste a public certificate PEM only.
How are fingerprints calculated?
SHA-1 and SHA-256 digests of the DER-encoded certificate, shown as uppercase colon-separated hex - the same idea as openssl x509 -fingerprint.
How is this different from openssl x509 -text?
openssl remains the gold standard on servers. This page is a quick local viewer for pasted PEM without installing tools - same fields for subject, issuer, SANs, and fingerprints.