CSR Decoder — Check a Certificate Signing Request

What is a CSR?

A Certificate Signing Request (PKCS#10) is what you send to a certificate authority to get a TLS certificate. It contains your public key, the identity you want in the certificate and any requested extensions such as Subject Alternative Names, all signed with your private key to prove you hold it. The private key itself never leaves your server.

Checklist before submitting

• Domains: every hostname — including www and bare domain — must appear in the SAN list. Many CAs copy the CN into the SANs, but not all.
• Key: RSA 2048 bits or more, or ECDSA P-256 / P-384. Smaller RSA keys are rejected.
• Organization fields: for OV/EV certificates, O, L, ST and C must match your legal registration exactly. For DV certificates they are ignored.
• Signature: SHA-256 or better.

Creating a CSR with OpenSSL

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

Keep example.key secret and on the server. After the CA issues the certificate, decode it with the certificate decoder and check the live site with the SSL checker.

Auch gesucht als: decode csr, csr checker, csr viewer, certificate signing request decoder, check csr, pkcs10 decoder.

Passende Tools zu: CSR Decoder

• RSA Key Generator — Create a public/private key pair for JWT signing, TLS testing, encryption experiments or SSH — generated by your browser’s Web Crypto API and never sent anywhere.
• SSH Key Generator — Create an SSH key pair for GitHub, GitLab, servers or CI deploy keys — Ed25519 by default, in standard OpenSSH format, without installing anything.
• DNS Lookup — Query all common DNS record types for a domain in one go, with TTLs, sorted MX records and an SPF/DMARC email-authentication summary.
• JWT-Decoder — Füge ein JSON-Web-Token ein, um dessen Header und Payload zu überprüfen, das Ablaufdatum zu ermitteln und die Signatur zu verifizieren.