SSL certificate decoder
Runs in your browserDecode PEM certificates and CSRs, see names, expiry and fingerprints, check the chain order and signatures, and whether a private key matches.
Paste a certificate, a full chain (fullchain.pem), a CSR or a private key. Paste a certificate and its key together to check that they belong together.
Leaf, intermediate, root
A server sends its own certificate (the leaf) followed by the intermediate certificates, each signed by the next. The certificate authority’s root is already in the client’s trust store and doesn’t need to be sent. If an intermediate is missing, browsers often cope (they cache or fetch it), while curl, Java, Android and many API clients fail with “unable to get local issuer certificate”.
The tool checks the order, whether each certificate was really signed by the next one (RSA, RSA-PSS, ECDSA and Ed25519 signatures are verified in your browser), and suggests the right order.
The same with openssl
openssl x509 -in cert.pem -noout -text openssl x509 -in cert.pem -noout -subject -issuer -dates -fingerprint -sha256 openssl req -in request.csr -noout -text -verify
# Same output = same key (works for RSA, EC and Ed25519) openssl x509 -in cert.pem -noout -pubkey | openssl sha256 openssl pkey -in key.pem -pubout | openssl sha256
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null # expires within 30 days? openssl x509 -in cert.pem -noout -checkend 2592000 || echo "renew now"
openssl verify -CAfile root.pem -untrusted intermediate.pem cert.pem # public key pin (HPKP / certificate pinning in apps) openssl x509 -in cert.pem -noout -pubkey | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | base64
Why clients reject the certificate
cert.pem instead of fullchain.pem in the server config. Let’s Encrypt’s certbot writes both; nginx needs fullchain.pem.
The leaf must come first, then its issuer. Some servers and clients don’t sort the chain.
Browsers ignore the common name. Every host name, including www, must be in the Subject Alternative Name. Wildcards cover exactly one level.
After re-issuing, the old key is still on the server. Compare the public keys as shown above.
Questions about the certificate decoder
How do I decode a PEM certificate?
Paste it above, or run openssl x509 -in cert.pem -noout -text. A PEM file is Base64 of the DER structure between the BEGIN and END lines.
How do I check that a private key matches a certificate?
Paste both into the field above. The tool derives the public key from the private key and compares it with the one in the certificate. On the command line compare the SHA-256 of openssl x509 -pubkey and openssl pkey -pubout.
Is it safe to paste my private key here?
The key is read in your browser and never leaves it; the page’s security policy forbids sending data. Even so, a production key is better checked with openssl on the server.
What is the SHA-256 fingerprint?
The SHA-256 hash of the certificate in DER form. It identifies exactly one certificate. The public key pin is the hash of the key only, so it stays the same when the certificate is renewed with the same key.
Can it read .pfx or .p12 files?
Not yet. Convert them first: openssl pkcs12 -in file.pfx -nodes -out all.pem, then paste the result.