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
Getting the decoder ready…
- Paste or drop a certificateOne certificate, a whole fullchain.pem, a .p7b bundle, or the output of openssl s_client.
- See what matters firstExpiry, the names it covers, who issued it, and anything that will break a connection.
- 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.
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.
| File | Holds | Looks like |
|---|---|---|
.pem, .crt, .cer | One or more certificates as text | -----BEGIN CERTIFICATE----- |
.der, .cer | One certificate in binary | Unreadable bytes; choose the file |
.csr, .req | A certificate signing request | -----BEGIN CERTIFICATE REQUEST----- |
.p7b, .p7c | A bundle of certificates (PKCS#7) | -----BEGIN PKCS7----- or binary |
fullchain.pem | The leaf, then its intermediates | Several CERTIFICATE blocks |
.pfx, .p12 | Certificates and the private key | Binary; 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 profileSSL & CSR FAQ
Certificates,
explained.
Paste the certificate into the decoder - the validity section shows the notBefore/notAfter dates and the exact days remaining, with a warning when fewer than 30 days are left. Offline, run: openssl x509 -in cert.pem -noout -dates.
Certificates and CSRs are public data - your server sends the certificate to every visitor. This decoder additionally runs entirely in your browser with no uploads, which you can verify in the network tab. Never paste a private key anywhere; this tool detects and refuses them.
A CSR (Certificate Signing Request) is what you generate and send to a certificate authority - it holds your public key, subject, and requested SANs, signed with your key. The certificate is what the CA sends back after signing. This tool decodes both and auto-detects which one you pasted.
Almost always a missing intermediate certificate. Browsers cache intermediates from other sites, so they forgive an incomplete chain; curl, Java, and embedded clients do not. Paste your fullchain.pem here - the tool detects missing intermediates and wrong ordering, and produces a corrected bundle.
No browser-based tool can - browsers cannot open raw TLS connections, so "online SSL checkers" run the check server-side. Run openssl s_client -connect yoursite.com:443 -servername yoursite.com locally instead (the tool shows this command with a copy button), then paste the output here.
Subject Alternative Names are the list of hostnames (and IPs) a certificate is valid for. Browsers have ignored the Common Name field since 2017, so a certificate without a SAN entry for your hostname fails verification even if the CN matches. The decoder lists every SAN and warns when a server certificate has none.
The decoder shows a "Self-signed" badge when the subject equals the issuer and the certificate verifies against its own public key. Self-signed certificates are fine for testing and internal services, but public clients will show trust warnings unless the certificate is explicitly installed.
RSA 2048-bit is the minimum for publicly-trusted TLS; RSA 3072/4096 or ECDSA P-256 are stronger choices, and ECDSA gives smaller handshakes. The decoder shows the exact algorithm and size, and flags RSA keys under 2048 bits as too weak.
Keep working
Tools and guides for your next step.