CSR & Certificate Decoder

Paste a CSR or certificate to see what's inside and whether it's right.

Decoded in your browser: nothing is uploaded. You can paste several blocks at once (a CSR and its certificate, or a whole chain). Never paste a private key.

A CSR decoder shows what a certificate signing request contains (domain names, organization, country, public key and signature) so you can catch mistakes before ordering a certificate. Paste a CSR or a certificate above: it's decoded in your browser and checked for weak keys, SHA-1, missing names and expiry.

What Is a CSR?

A certificate signing request (CSR) is the file you send to a certificate authority to get an SSL/TLS certificate: it holds your public key and the names the certificate should cover.

Your server creates a key pair and keeps the private key; the CSR holds the public key and the names example.com and www.example.com; the certificate authority returns a certificate with the same public key and names, a validity period and its signature
The CSR and the certificate hold the same public key; the private key stays on your server.

Your server, hosting panel or OpenSSL creates two keys. The private key stays secret on the server. The CSR carries the public key and the names, and is signed with the private key to prove you hold it. The format is PKCS #10 (RFC 2986), usually sent as Base64 text between -----BEGIN CERTIFICATE REQUEST----- and -----END CERTIFICATE REQUEST-----. The authority checks that you control the domain, then returns a certificate (X.509, RFC 5280) with the same public key and names, a validity period and its own signature.

What the Decoder Shows

Every field the certificate authority will read, with what it should contain.

FieldWhat it should contain
Common name (CN)The main domain, such as www.example.com or *.example.com. Kept for compatibility: browsers read the SANs.
Subject alternative names (SAN)Every name the certificate must cover: example.com and www.example.com are two names.
Organization (O)The legal company name, checked for OV and EV certificates; ignored for domain-validated (DV) ones.
Organizational unit (OU)Dropped from public certificates since 1 September 2022 (ballot SC47): leave it empty.
City, state (L, ST)Full names, not abbreviations, for OV and EV certificates.
Country (C)Two letters (ISO 3166): US, GB, FR. "USA" or "UK" is an error.
Public keyRSA 2048 bits or more, or ECDSA P-256 / P-384.
SignatureSHA-256 or stronger, and valid: it proves the request wasn't changed.
Certificate onlyIssuer, validity dates, serial number, key usages, OCSP and CRL addresses, validation level (DV, OV, EV), Certificate Transparency timestamps, SHA-256 fingerprint.

Do it yourself

How to Generate a CSR

Most hosting panels (cPanel's SSL/TLS page, Plesk) and servers (IIS) create the CSR and key for you, and our CSR generator makes both in your browser. With OpenSSL 1.1.1 or newer, one command makes both, with the SANs:

openssl req -new -newkey rsa:2048 -nodes -keyout example.com.key -out example.com.csr -subj "/CN=example.com" -addext "subjectAltName=DNS:example.com,DNS:www.example.com"

For a smaller, faster ECDSA key, replace -newkey rsa:2048 with -newkey ec -pkeyopt ec_paramgen_curve:P-256. Keep example.com.key on the server; send only example.com.csr.

How to Decode a CSR or Certificate With OpenSSL

openssl req -in example.com.csr -noout -text -verify
openssl x509 -in certificate.crt -noout -text

For a binary (DER) file add -inform der. To check that a certificate, its CSR and its private key belong together, compare the hash of their public keys; the three lines must print the same value:

openssl req -in example.com.csr -noout -pubkey | openssl sha256
openssl x509 -in certificate.crt -noout -pubkey | openssl sha256
openssl pkey -in example.com.key -pubout | openssl sha256

Common CSR and Certificate Problems

Most rejected orders and browser errors come from a few mistakes the decoder flags.

ProblemWhy it mattersFix
RSA key under 2048 bitsRefused by every public authorityCreate a new key and CSR with rsa:2048 or ECDSA P-256
SHA-1 or MD5 signatureBroken hash functions, refusedRecreate the CSR; OpenSSL uses SHA-256 by default
Missing SANs, or no wwwThe certificate won't cover the name visitors typeAdd every name with -addext "subjectAltName=…"
Country written in full"USA" or "United Kingdom" is invalidUse the two-letter code: US, GB
Certificate doesn't match the keyThe server refuses to start, or browsers show an errorPaste the CSR and the certificate above to compare their keys; reissue with the right CSR
Chain in the wrong orderSome clients reject the connectionServer certificate first, then each intermediate
Expired or about to expireBrowsers block the siteRenew; with lifetimes of 200 days and less, automate it (ACME)

PEM, DER, CRT, PFX: Certificate File Formats

The extension doesn't say what's inside: a .crt or .cer file can be PEM text or binary DER.

FormatWhat it isOn this page
PEM
.pem .crt .cer .csr
Base64 text between BEGIN and END lines; can hold several certificatesPaste or open it
DER
.der .cer
The same data in binaryOpen the file
PKCS #7
.p7b .p7c
A bundle of certificates, no keyConvert first: openssl pkcs7 -print_certs -in file.p7b
PKCS #12
.pfx .p12
Certificate and private key, protected by a passwordNot read here (it contains the key). Extract the certificate: openssl pkcs12 -in file.pfx -clcerts -nokeys

How This Decoder Works

PartDetail
WhereIn your browser. The text or file never leaves your device; the page works offline once loaded.
FormatsCSRs (PKCS #10, RFC 2986) and X.509 certificates (RFC 5280), as PEM text or PEM/DER files, several blocks at once.
SignaturesChecked with the browser's Web Crypto API: the CSR's own signature; a certificate's when its issuer is pasted below it, or when it's self-signed. RSA (PKCS #1 v1.5), ECDSA P-256/P-384/P-521, and Ed25519 where the browser supports it; RSA-PSS is shown but not checked.
ChecksRSA under 2048 bits, curves other than P-256/384/521, SHA-1 and MD5, country codes, missing SANs, common name not among the SANs, OU, expiry and lifetime, chain order, CSR and certificate key match.
Not doneRevocation (OCSP, CRL) and browser trust: use the SSL checker on a live site for those. Private keys and PFX files are never read.
Tested againstOpenSSL 3.0 output for the same files (names, SANs, keys, extensions, fingerprints, signatures).
Last verified22 November 2026

Frequently Asked Questions

What is a CSR decoder?
A tool that shows what a certificate signing request contains: the domain names, the organization and country, the public key and how the request was signed. Check it before you send the CSR to a certificate authority: a typo or a missing name means a certificate you can't use, and a new order.
Is it safe to paste my CSR here?
Yes. A CSR holds only public information (names and a public key), and this page decodes it in your browser: nothing is sent to our server. The private key is a different file. Never paste a private key into any website: this page refuses it, but anyone who gets it can impersonate your server.
How do I check that a certificate matches my CSR?
Paste both, the CSR and the certificate, in the box above: the page compares their public keys and says whether they match. To check a certificate against a private key, do it on your own server with OpenSSL: the commands are under "How to Decode a CSR or Certificate With OpenSSL".
Why does my CSR need a subject alternative name (SAN)?
Browsers check only the SAN list, not the common name, since Chrome 58 in 2017. Most authorities copy the common name into the SANs, but if you need both example.com and www.example.com, or several subdomains, list them all.
What key size should a CSR use?
RSA 2048 bits or an ECDSA P-256 key. Both are accepted by every public certificate authority; RSA 3072 or 4096 and ECDSA P-384 also work but are slower. Keys under 2048 bits and SHA-1 signatures are refused.
How long are SSL certificates valid?
Public certificates issued since 15 March 2026 last at most 200 days. The limit drops to 100 days on 15 March 2027 and to 47 days on 15 March 2029 (CA/Browser Forum ballot SC-081). Certificates from a company's own (private) CA can last longer.

Next steps

Related Tools

CSR Generator
Create a CSR and its private key, in your browser.
SSL Certificate Checker
A live site's certificate, chain, expiry and TLS versions.
HTTP Header Checker
HSTS and the other security headers of any URL.
DNS Lookup
CAA records: which authorities may issue for a domain.
Website to IP Lookup
The IP addresses behind a site, and who hosts it.