THE TOOLBOX / SECURITY & TLS CERTIFICATES
CSR Generator —
SSL Certificate Signing Request & SAN Builder.
Generate standards-compliant PKCS#10 SSL/TLS Certificate Signing Requests (.csr) with Multi-Domain SAN extensions and matching private keys (.key) using ECDSA P-256/P-384 or RSA-2048/4096—100% locally via Web Crypto.
Generate an RSA PKCS#10 CSR and PKCS8 private key locally, or paste a CSR PEM to inspect it.
The private key is downloadable and must be kept secret. No certificate is issued.
TLS / PKCS#10 CSR GUIDE
How to create and submit an SSL Certificate Signing Request (CSR).
1. Submit Only the .csr File
Send the -----BEGIN CERTIFICATE REQUEST----- block to your Certificate Authority (DigiCert, Sectigo, Let's Encrypt, AWS ACM, etc.). Never share your .key private key—save it securely on your web server or secret manager.
2. Multi-Domain & Wildcard SANs
List every hostname you want covered (e.g., example.com, www.example.com, or *.example.com). All entries are encoded as ASN.1 DER dNSName records inside OID 2.5.29.17.
3. Related Security & Crypto Tools
Split private key backups with Shamir's Secret Sharing, test Web Crypto encryption in the Web Crypto Playground, or generate bcrypt hashes in the Bcrypt Generator.
Frequently Asked Questions
Is it safe to generate an SSL CSR and private key in my browser?
Yes. This CSR generator uses your browser’s native Web Crypto API (crypto.subtle) to generate the RSA or ECDSA keypair and sign the PKCS#10 CSR entirely in local RAM. Neither your private key nor your CSR is ever sent to any server.
Should I choose ECDSA P-256 or RSA 2048 for my TLS certificate?
ECDSA P-256 delivers stronger cryptographic security than RSA 2048 with much smaller keys and faster TLS handshakes, and is supported by all modern browsers and Certificate Authorities. Choose RSA 2048 only if you must support legacy enterprise appliances.
Why are Subject Alternative Names (SANs) required?
Modern browsers (Chrome, Safari, Firefox, Edge) ignore the legacy Common Name (CN) field and validate hostnames strictly against the Subject Alternative Name (SAN) extension. This tool automatically embeds your primary CN and every additional domain into the CSR’s SAN extension.
How can I verify the generated CSR with OpenSSL?
After downloading your .csr file, run "openssl req -in domain.csr -noout -text" in your terminal to inspect the Subject fields, public key algorithm, SAN DNS entries, and valid cryptographic signature.