CSR Decoder
Paste a certificate signing request to see its subject, domain names, key type and size, and whether its signature is valid before you send it off.
How to check a CSR
Paste your certificate signing request
Paste or type your certificate signing request into the box, or press Try an example.
Read the details
Check the subject, the names and the key size.
Check the signature
A valid signature means the request is intact and matches its key.
When to use CSR Decoder
Someone else generated the CSR and you want to confirm the names and key before submitting it to a certificate authority.
A certificate authority rejected a CSR and you need to see what it actually contains.
Tips for a better CSR Decoder result
Check the list of names first: every domain the certificate must cover has to be there, including the bare domain if you use it.
Compare the key type and size with your authority's requirements, which commonly start at RSA 2048 or ECDSA P-256.
CSR Decoder: limits and what to check
Extensions other than subject alternative names, such as key usage, are not listed, though authorities usually set those themselves.
A valid signature proves the CSR matches its own key, not that the key is the one stored on your server.
About CSR Decoder
Check a certificate signing request before you pay for a certificate. Mistakes in the names or a weak key mean the certificate has to be reissued. The signature is verified too, which proves the CSR was made with the private key that matches it and was not edited afterwards.
FAQs
Why does it say there are no names?
The CSR has no subject alternative name extension. Most authorities copy the common name in, but some refuse such requests.
Can it read a CSR in DER form?
Paste it as Base64 and it is read the same way, or convert it first with PEM to DER Converter.
What key size is enough?
RSA 2048 or ECDSA P-256 at least. Smaller keys are refused by public certificate authorities.