Certificate and CSR decoder

Paste a certificate, a bundle or a CSR and read every field in plain words.

One or more PEM blocks, or base64 DER. Processed in memory and never stored.

Processed in memory and never stored.

A .pem, .crt, .cer, .der, .csr or .p7b file, base64-encoded. Send either this or the pasted text.

Processed in memory and never stored.

Free: nothing is charged, and what you paste is never stored.

A certificate is a small signed file, but reading one usually means an OpenSSL command and a wall of text. This decoder shows the parts that matter in plain words: which names it covers, when it expires, who issued it, what key it uses, and whether a bundle is in the right order. It reads certificate signing requests too, so you can check a CSR before you send it to a certificate authority.

How to use it

Paste one or more blocks of PEM text, the kind that starts with -----BEGIN CERTIFICATE----- or -----BEGIN CERTIFICATE REQUEST-----, or upload the file your certificate authority or server gave you. A whole bundle works: paste the server certificate and its intermediates together, in any order. Base64 without the BEGIN and END lines works as well, and so does a binary .der or .p7b file.

Never paste a private key. If the text holds one, the decoder refuses all of it without reading further, and you should replace that key.

What each card shows

Every certificate and request gets its own card, in the order you pasted them.

  • Names covered. The Subject Alternative Name list: the host names, addresses and email addresses the certificate is valid for. Browsers ignore the common name, so a name that isn't in this list isn't covered.
  • Dates. When the certificate starts and stops being valid, how many days are left at the moment you decoded it, and how long it was issued for.
  • Issuer. The certificate authority that signed it, or the certificate itself when it is self-signed.
  • Key and signature. The key type and size, and the algorithm the issuer signed with.
  • Validation level. Domain validated, organization validated or extended validation, read from the policies the issuer wrote into the certificate.
  • Fingerprints. SHA-256 and SHA-1, in the form browsers and servers show, so you can match a file to the certificate a server presents.

Under "All fields" you'll find the rest: the full subject and issuer, the serial number, key usage, the basic constraints that make a certificate an authority, key identifiers, the revocation and issuer addresses, policy identifiers and the embedded SCT timestamps from certificate transparency logs. We show each SCT's log ID and time; we don't keep a list of log names, so we don't name the log.

For a CSR the card shows the subject, the names it requests, the key, and whether its signature matches its own key. A request whose signature doesn't match was changed after it was made, or was signed with another key, and a certificate authority will reject it.

How bundles are checked

When you paste more than one certificate, we sort them into a chain: the leaf (the certificate that issued none of the others) first, then each issuer in turn, matched by key identifier and then by name. Every link is checked: the issuer's key must have made the signature below it. A link that fails means the bundle mixes certificates from different issuers, often an old intermediate after the authority renewed its own.

The chain ends at a root in Mozilla's trust store, at a self-signed certificate that store doesn't hold, or at an intermediate. Ending at an intermediate is what servers normally send. We say when the bundle was out of order, when the same certificate appears twice, and when a certificate doesn't belong to the chain at all.

What the findings mean

Findings flag what usually goes wrong: a certificate that has expired, isn't valid yet or expires within 30 days; an RSA key under 2048 bits or an elliptic curve key under 256 bits; a SHA-1 or MD5 signature; a certificate with no Subject Alternative Name; validity longer than the 398 days browsers accept for public sites; a self-signed certificate. For requests, we flag a signature that doesn't match, a short key, no requested names, and a common name missing from the requested names. Each finding names the certificate or request it is about, and the ones with a fix link to a guide.

The decoder grades nothing and gives no score: a certificate can be perfectly valid and still be the wrong one for your server.

Pasted certificates stay private

Certificates are public once a site serves them, but a pasted bundle can include an internal host name or a request for a site that isn't live yet. Everything you paste is processed in memory and discarded when the answer is sent. It is never cached, stored, logged, shared or repeated in an error, and the tool fetches nothing from the addresses inside the certificates.

Related tools

To see the certificate a live site actually serves, with its chain, expiry and TLS versions, use the SSL checker. To make a new key and CSR without OpenSSL, use the CSR generator; it runs in your browser and its "Decode this CSR" button opens the request here.

Questions

Is what I paste stored?
No. It is decoded in memory and thrown away as soon as the answer is sent. It is never cached, logged, written to a database or shared, and an error message never repeats it. Your usage history records only that the tool ran.
What happens if I paste a private key?
We refuse the whole input before reading any of it, even when certificates are pasted alongside the key. Treat that key as exposed anyway: make a new key, get a new certificate for it and replace the old one. The decoder never needs a key, and neither does any honest website.
Which formats work?
PEM text (certificates, certificate requests and PKCS#7 bundles), base64 DER pasted on its own, and .pem, .crt, .cer, .der, .csr and .p7b files. Up to 10 certificates and requests at a time, each at most 64 KB.
Does the decoder contact the certificate authority?
No. It fetches nothing: no revocation check, no download of a missing intermediate, no transparency log lookup. Each of those would tell a third party which certificate you are looking at. To see what a live site serves, use the SSL checker.
Why does my bundle stop at an intermediate?
That is normal. Servers send their own certificate and the intermediates; browsers already hold the roots. A bundle that ends at a root in Mozilla's store is fine too, but the root adds bytes to every connection without helping.