Paste a certificate signing request to read everything inside it before you send it to a certificate authority: the subject fields, Subject Alternative Names, key algorithm and size, requested extensions and signature. Built-in checks flag problems that would make a CA reject the order.
Last updated:
Certificate signing request for
Subject
Subject Alternative Names
Public key
Signature
Validity checks
Requested extensions and attributes
Check it yourself with OpenSSL
Advertisement
Advertisement
How to use the CSR Decoder
Paste the CSR, including the -----BEGIN CERTIFICATE REQUEST----- and -----END CERTIFICATE REQUEST----- lines, or open a .csr file.
Read the summary: the Common Name, signature status, key type and number of SANs appear at the top.
Confirm the names in Subject Alternative Names: these are the host names the certificate will cover.
Review the validity checks. Red items are problems a CA will reject; orange items are worth fixing.
Match the key if needed: compare the modulus MD5 or SPKI SHA-256 with the OpenSSL commands shown for your private key.
What is inside a CSR
A PKCS#10 certificate signing request (RFC 2986) is an ASN.1 structure with three parts: the certification request info (version, subject name, public key and attributes), the signature algorithm, and a signature over the first part made with your private key.
Field
Example
What CAs do with it
CN (Common Name)
www.example.com
Main host name; also added to the SAN list by most CAs
O / OU
Example Inc. / Web Team
Validated for OV and EV certificates; ignored and removed for DV certificates. OU is no longer included by public CAs
L / ST / C
San Francisco / California / US
Location for OV/EV; C must be a 2-letter ISO code
subjectAltName
DNS:example.com, DNS:www.example.com
The list of names the certificate is valid for; each one is domain-validated
Public key
RSA 2048 or ECDSA P-256
Copied unchanged into the certificate
Key Usage / EKU
digitalSignature, serverAuth
Usually replaced by the CA's own profile
Signature
SHA-256 with RSA
Checked to prove you hold the private key
Common reasons a CA rejects a CSR
Weak key or hash: RSA keys under 2048 bits, or MD5 and SHA-1 signatures.
Internal names: host names such as server.local, intranet or private IP addresses like 10.0.0.5 cannot be validated publicly.
Bad characters: spaces, underscores or accented letters in host names, or a country written as "USA" instead of "US".
Key reuse: some CAs refuse a public key that was already used for a revoked or compromised certificate. Generate a fresh key with each CSR when in doubt.
Edited CSR: changing any byte breaks the signature. Generate a new CSR instead of editing an old one.
Prefer a form? The CSR generator builds the key and request in your browser. Once the CA sends the certificate, open it in the SSL certificate decoder to confirm the names and key match.
Frequently asked questions
What is a CSR?
A certificate signing request is a small file in PKCS#10 format that you send to a certificate authority to get an SSL/TLS certificate. It contains your public key, the names the certificate should cover and optional extensions, all signed with your private key. The private key itself is never part of the CSR.
Is it safe to paste my CSR here?
Yes. A CSR contains only public information, and this decoder runs entirely in your browser, so nothing is uploaded. Never paste the private key, which starts with BEGIN PRIVATE KEY; the tool refuses to decode it and warns you.
What does 'signature is valid' mean for a CSR?
Every CSR is signed by the private key that matches the public key inside it. A valid signature proves the requester holds that private key and that the CSR has not been edited since it was created. CAs check the same signature before issuing.
Why do I need Subject Alternative Names?
Since 2017 major browsers ignore the Common Name and only trust the host names listed in the SAN extension. Public CAs usually copy the CN into the SAN for you, but listing every host name you need, such as example.com and www.example.com, avoids surprises.
How do I check that a CSR matches my private key?
For RSA, run openssl rsa -in private.key -noout -modulus | openssl md5 and compare it with the Modulus MD5 shown here. For any key type, compare the SPKI SHA-256 value with the hash of the public key extracted from your private key; the exact commands are shown under the results.
What key size should a CSR use?
Public CAs require RSA keys of at least 2048 bits; 2048 or 3072 bits are the common choices. ECDSA P-256 and P-384 keys are smaller and faster and accepted by all major CAs. The decoder flags 1024-bit RSA keys and SHA-1 signatures, which CAs reject.
Can it decode a certificate instead of a CSR?
No. Issued certificates start with BEGIN CERTIFICATE and have issuer, serial number and validity dates that a CSR does not. Use the SSL Certificate Decoder for those; the tool points you there if you paste one.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.