Decode a certificate signing request before you send it to a CA: subject, names, extensions, key size and signature
Paste a certificate signing request to check its subject, the names and extensions it asks for and its key before you submit it. When you paste the certificate too, the page shows whether it has the same key.
How to use it
Paste the CSR, from -----BEGIN CERTIFICATE REQUEST----- to the END line. Check the subject, the requested names (SANs), the key and the signature, and read What a CA will say. Got the certificate back? Paste it under the CSR: both say “same public key” when they match.
Example
Check a request
-----BEGIN CERTIFICATE REQUEST----- MIIC/DCCAeQCAQAwZjELMAkGA1UEBhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWEx…
Subject: C=US, ST=California, L=San Francisco, O=Example Inc, CN=example.com Names: DNS: example.com, DNS: www.example.com, IP: 192.0.2.1, Email: ops@example.com Public key: RSA, 2,048 bits
The page’s sample, a test request.
OpenSSL errors on a CSR
| OpenSSL says | Usual cause |
|---|---|
unable to load X509 request from file | The file is not a CSR: a key, a certificate, or text with the BEGIN line missing. Paste it here: the page says what it is. |
Could not find or decode certificate | openssl x509 was given a CSR; read it with openssl req instead. |
Certificate request self-signature verify failure | The CSR was changed after it was signed, or cut while copying: make it again from the key. |
openssl req -in request.csr -noout -text -verify
Why check a CSR before you submit it
Sources: RFC 2986 (PKCS #10), RFC 2985 §5.4.2, CA/Browser Forum Baseline Requirements
The same check with OpenSSL
| To see | Command |
|---|---|
A certificate | openssl x509 -in cert.pem -noout -text |
A request (CSR) | openssl req -in request.csr -noout -text |
The SHA-256 fingerprint | openssl x509 -in cert.pem -noout -fingerprint -sha256 |
A DER file as PEM | openssl x509 -inform der -in cert.der -out cert.pem |
Certificates inside a .p7b | openssl pkcs7 -in bundle.p7b -print_certs |
Sources: OpenSSL x509 manual
Questions
- Is the CSR uploaded?
No. Everything runs in your browser, so your request stays on your device. Nothing you paste is uploaded unless you share a result, which is locked with your password first. - Does a CSR contain the private key?
No. It holds the public key and is signed with the private key, which stays where the request was made. You need that private key to install the certificate you get back. - How do I know a certificate matches my CSR?
Paste both. When they hold the same public key, each says “same public key as” the other; the key pin is the same too. - What key size should a CSR have?
RSA 2,048 bits or more, or an EC key on P-256 or P-384. Certificate authorities don’t issue public certificates for RSA keys under 2,048 bits. - Why would a CA refuse my CSR?
Most often a name it can’t issue for: an internal name such as server.local, a name with an underscore, a private IP address, or a wildcard in the wrong place. A key that is too small, on an unusual curve or with a bad exponent is refused too. What a CA will say lists each one it finds, marked Fix. - Can I paste a private key here?
The page names a private key block when it finds one and doesn’t read it. A private key never needs to leave the server it belongs to, so keep it out of chats, tickets and websites.