Skip to content

SSL Certificate & CSR Decoder

See when a certificate expires, which names it covers, and whether its chain will work.

Free · No signupDecoded in your browser

Try an example

Getting the decoder ready…

  1. Paste or drop a certificateOne certificate, a whole fullchain.pem, a .p7b bundle, or the output of openssl s_client.
  2. See what matters firstExpiry, the names it covers, who issued it, and anything that will break a connection.
  3. Fix the chainEach link’s signature is checked, and a correctly ordered fullchain.pem is ready to download.

The same with OpenSSL

  • Decode a certificate
    openssl x509 -in certificate.pem -noout -text
  • Check the dates
    openssl x509 -in certificate.pem -noout -dates
  • SHA-256 fingerprint
    openssl x509 -in certificate.pem -noout -fingerprint -sha256
  • Decode and verify a CSR
    openssl req -in request.csr -noout -text -verify
  • See a live site’s certificates
    openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null
  • Check a chain
    openssl verify -untrusted intermediate.pem certificate.pem
  • Does the key match?
    openssl x509 -in certificate.pem -noout -pubkey | openssl sha256; openssl pkey -in key.pem -pubout | openssl sha256

Certificates live on servers

Hear about expiry before your visitors do.

CtrlOps alerts you on Slack or Telegram before an SSL certificate on your server expires, and its security audit checks that renewal is automated.

Explore AlertsDownload for MacDownload for Windows

Keep it handy

Certificate files,
by their extension.

The same certificate travels in several containers. Everything here except .pfx can be pasted or chosen above.

Certificate file types, what they hold and how to recognise them
FileHoldsLooks like
.pem, .crt, .cerOne or more certificates as text-----BEGIN CERTIFICATE-----
.der, .cerOne certificate in binaryUnreadable bytes; choose the file
.csr, .reqA certificate signing request-----BEGIN CERTIFICATE REQUEST-----
.p7b, .p7cA bundle of certificates (PKCS#7)-----BEGIN PKCS7----- or binary
fullchain.pemThe leaf, then its intermediatesSeveral CERTIFICATE blocks
.pfx, .p12Certificates and the private keyBinary; not opened here

How the decoder works

Read the certificate.
Then check the chain.

What the decoder shows you

Every field a browser looks at: when the certificate becomes valid and when it expires, the subject alternative names it covers, who issued it, the key type and size, the signature algorithm, its key usages, where to check revocation, and its SHA-256, SHA-1 and SPKI fingerprints. Problems that break connections, such as an expired date, a SHA-1 signature, a weak key or a missing SAN, are listed first.

Decoding a CSR before you send it to a CA

A CSR carries your public key, the subject and the names you are asking for, signed with your private key. The decoder checks that signature, so a damaged or edited CSR shows up before the CA rejects it, and warns when no SANs are requested. Add them with -addext "subjectAltName=DNS:example.com" when you run openssl req.

Chain order: why fullchain.pem order matters

A server must send its own certificate first, then each intermediate up towards the root. Browsers often cope with mistakes, because they cache intermediates; curl, Java, Android and most API clients do not. Paste the whole bundle and the decoder puts it in order, checks each link’s signature with the issuer’s key, spots a missing or wrong intermediate, and gives you a corrected fullchain.pem without the root, which clients already have.

Checking a live website

A browser cannot open a raw TLS connection, so this page cannot fetch a site’s certificate itself. Run openssl s_client -connect example.com:443 -servername example.com -showcerts and paste the whole output: the decoder picks out every certificate and checks the chain the server actually sends.

Is it safe to paste a certificate here?

Certificates and CSRs are public; your server sends its certificate to every visitor. The decoder still runs entirely in your browser, with no uploads. A private key is different: if one is pasted, it is skipped without being read, and the page tells you so.

Read RFC 5280, the X.509 certificate profile

SSL & CSR FAQ

Certificates,
explained.

Keep working

Tools and guides for your next step.

Your privacy preferences. We use product analytics to improve CtrlOps. Google measurement runs without analytics cookies. Live chat stays off until you allow it. Cookie policy