CSR Decoder

Paste a certificate signing request to decode it and check it before you send it to a certificate authority. See the subject, SANs, key type and size, signature algorithm and any problems, decoded entirely in your browser.
Decoded in your browser. Nothing is uploaded.
Paste the full block including the BEGIN and END lines, or drop a .csr file on the box. Never paste your private key here, or anywhere else.

How to Use the CSR Decoder

Check your CSR before you submit it. Mistakes in a CSR end up in the issued certificate, and fixing them means generating a new request and reissuing.

1

Paste your CSR

Copy the text that starts with -----BEGIN CERTIFICATE REQUEST----- from your server, hosting panel or OpenSSL output, or upload the .csr file.

2

Decode it

The decoder reads the request in your browser and shows the subject, Subject Alternative Names, public key, signature and extensions.

3

Fix issues before ordering

Each check shows pass, warning or fail. Correct any problems and generate a new CSR before you send it to your certificate authority. The decoder gives you the OpenSSL command for it.

What the CSR Checker Tests

Decoding shows what's in the request. The checks below tell you whether a certificate authority will accept it, using the same rules CAs apply before they issue.

Signature

The request's signature is verified with its own public key. A valid signature proves the CSR wasn't changed after it was made, and that whoever made it holds the private key.

Key strength

Key type and size against CA rules (RSA 2048-bit or more, ECDSA P-256 or P-384), the public exponent, and the broken-key patterns CAs screen for: ROCA, primes too close together and small factors.

Hostnames

Every Subject Alternative Name: hostname syntax, wildcards, internationalized (xn--) names, internal names and private IP addresses, and whether the Common Name is listed too.

Subject details

Country codes against ISO 3166 (the United Kingdom is GB, not UK), state names, field lengths, text encodings, and the default values OpenSSL and Java keytool fill in.

Extensions

Requests a CA can't or won't honor: a CA certificate (CA:TRUE), certificate-signing key usage, OCSP Must-Staple, unknown critical extensions and challenge passwords.

Fingerprints and DANE

The SHA-256 of the public key, to match the CSR with its private key and certificate, and the TLSA 3 1 1 record to publish for DANE before you switch certificates.

What Is a CSR (Certificate Signing Request)?

A certificate signing request is a block of encoded text you send to a certificate authority (CA) to apply for an SSL/TLS certificate. It contains your public key and the details to put in the certificate, and it is signed with your private key to prove you hold it. The format is defined by PKCS #10 (RFC 2986).

The fields of a CSR
FieldExampleWhat it means
CNwww.example.comCommon Name: the main hostname. CAs copy it into the SANs.
SANexample.com, www.example.comSubject Alternative Names: every hostname the certificate will cover.
OExample IncOrganization: your legal company name (used for OV and EV).
OUITOrganizational Unit. Public CAs no longer include it in certificates.
L / STWilmington / DelawareLocality (city) and state or province, spelled out in full.
CUSCountry: a two-letter ISO 3166 code.
Public keyRSA 2048-bitGoes into the certificate. The matching private key stays on your server.

How to Generate and Decode a CSR with OpenSSL

Most hosting panels generate CSRs for you. On a server, OpenSSL does it in one command. Use OpenSSL 1.1.1 or later for -addext.

# Generate a 2048-bit RSA key and CSR with SANs
openssl req -new -newkey rsa:2048 -nodes \
  -keyout example.com.key -out example.com.csr \
  -subj "/C=US/ST=Delaware/L=Wilmington/O=Example Inc/CN=example.com" \
  -addext "subjectAltName=DNS:example.com,DNS:www.example.com"

# Generate an ECDSA P-256 key and CSR instead
openssl req -new -newkey ec -pkeyopt ec_paramgen_curve:P-256 -nodes \
  -keyout example.com.key -out example.com.csr -subj "/CN=example.com"

# Decode a CSR
openssl req -in example.com.csr -noout -text -verify
Keep the private key safe .key stays on the server Generating a CSR also creates a private key file. Only the CSR goes to the certificate authority. Anyone who has your private key can impersonate your site or mail server, so never email it, paste it into online tools, or commit it to a code repository. If it leaks, generate a new key and CSR and reissue the certificate.

Common CSR Problems and How to Fix Them

These are the problems that most often make a CA reject a CSR or issue a certificate that doesn't work.

Weak key

RSA key smaller than 2048 bits

CAs reject RSA keys under 2048 bits. Older servers and appliances sometimes still default to 1024.

Generate a new key with rsa:2048 or larger, or use ECDSA P-256.

SHA-1 signature

The CSR is signed with SHA-1

SHA-1 is no longer considered safe for signatures, and some CAs refuse SHA-1 signed requests. MD5 signed requests are rejected everywhere.

Regenerate with -sha256. Current OpenSSL versions use SHA-256 by default.

Missing SANs

Only a Common Name, no Subject Alternative Names

Browsers ignore the CN and only check SANs. Most CAs add the CN as a SAN, but other names you need won't be there.

Add every hostname with -addext "subjectAltName=DNS:...", or list them in your CA's order form.

Wrong country code

Country is not a two-letter code

Values like USA, United States or UK in the C field make the CA reject the order. The United Kingdom's code is GB.

Use the ISO 3166 two-letter code, such as US, GB or AM.

Internal names

Private hostnames or IP addresses

Public CAs can't issue for names like server.local or private IPs like 10.0.0.5.

Use a public domain name, or an internal CA for internal-only services.

Default values

Placeholders left in the subject

Pressing Enter at OpenSSL's prompts leaves values like Some-State and Internet Widgits Pty Ltd, and Java keytool fills in Unknown. CAs that validate the organization reject them.

Type your real details, or leave the optional fields out for a domain-validated certificate.

Broken key

A key with a known weakness

Keys made by flawed chips (ROCA) or flawed libraries (primes too close together) can be factored, which exposes the private key. CAs screen for both.

Generate a new key with current software or patched firmware, and replace every certificate that used the old one.

Private key pasted

A private key was shared instead of the CSR

The decoder refuses private keys and doesn't read them. If you've pasted a key into any website, treat it as exposed.

Generate a new key pair and CSR, and reissue any certificate that used the old key.

CSRs for Email Security Certificates

You'll also create CSRs for the certificates that protect email, so it's worth checking them the same way.

Mail server certificates

Your MX hosts need certificates whose SANs match their hostnames for MTA-STS to work. Include every MX name, such as mx1.example.com, in the CSR.

Check MTA-STS →

DANE TLSA records

With DANE, a TLSA record pins your mail server's key. The decoder shows the 3 1 1 value for the CSR's key, so you can publish it next to the current record before you switch certificates.

Check DANE →

BIMI VMC and CMC

Verified Mark Certificates and Common Mark Certificates that show your logo in Gmail and Apple Mail are ordered with a CSR too. The organization details must match your legal entity.

Check BIMI →

S/MIME certificates

S/MIME certificates sign and encrypt individual messages. Their CSRs carry an email address as the SAN instead of a hostname, and the decoder checks them as S/MIME requests.

Frequently Asked Questions

What is a CSR decoder?
A CSR decoder reads a certificate signing request and shows what's inside it in plain text: the Common Name, Subject Alternative Names, organization details, public key type and size, and signature algorithm. Use it to confirm the CSR is correct before you send it to a certificate authority.
Is it safe to paste my CSR into an online decoder?
Yes. A CSR contains only public information: your public key and the details that will appear in the certificate. This decoder also runs entirely in your browser, so the CSR is never uploaded. Never paste your private key into any tool. This decoder refuses private keys and clears them from the box.
What is the CSR code?
"CSR code" usually means the encoded text block of a certificate signing request. It starts with -----BEGIN CERTIFICATE REQUEST----- and ends with -----END CERTIFICATE REQUEST-----. Your certificate authority asks you to paste it during the order.
How do I decode a CSR with OpenSSL?
Run openssl req -in request.csr -noout -text -verify. It prints the subject, public key, extensions and signature, and confirms the request's signature is valid.
How do I open a CSR file?
A .csr file is plain text. Open it in any text editor (Notepad, TextEdit, VS Code) to copy its contents, or upload it to the decoder above to see the decoded fields.
How do I generate a CSR?
Most hosting panels (cPanel, Plesk) and servers (IIS, Exchange) have a CSR generator. On Linux or macOS, run openssl req -new -newkey rsa:2048 -nodes -keyout example.com.key -out example.com.csr. Keep the .key file private and send only the .csr to your CA.
Does a CSR contain the private key?
No. A CSR contains the public key and is signed with the private key, but the private key itself is never included. The private key is saved separately when you generate the CSR and must stay on your server.
How do I check that my CSR matches my private key?
Compare the SHA-256 of the public key. The decoder shows it for the CSR under Key fingerprints. For the key, run openssl pkey -in private.key -pubout -outform der | openssl dgst -sha256. For the issued certificate, run openssl x509 -in certificate.crt -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256. They belong together when the values are the same.
Why do I need SANs in my CSR?
Browsers only check Subject Alternative Names, not the Common Name, when they validate a certificate. Most CAs copy the Common Name into the SANs automatically, but any other hostnames, such as www or mail subdomains, must be listed in the CSR or in the order form.
What key size should my CSR use?
Use RSA 2048-bit or larger, or ECDSA P-256. RSA keys smaller than 2048 bits are rejected by public CAs. An ECDSA P-256 key is as strong as a 3072-bit RSA key, and it is much smaller and faster.
Can I reuse a CSR when renewing a certificate?
Technically yes, but it's better practice to generate a new key pair and CSR at each renewal. Reusing a key means a key that was ever exposed stays in use. Many automated tools such as Certbot create a new key by default.

More Free Email Security and DNS Tools

Protect your domain beyond the certificate

A valid certificate encrypts the connection, but it doesn't stop attackers from sending email as your domain. PowerDMARC gets you to DMARC enforcement and monitors SPF, DKIM, MTA-STS and BIMI in one place.