Make a certificate signing request and its private key on your device, no upload
Runs in your browser. Nothing you type is sent anywhere. Checked against sources on 16 Nov 2026.Checked against the tool’s code on 18 November 2026. Figures read from their sources on 16 November 2026. What we collect
The CSR generator makes the private key and the signing request on your device with WebCrypto; nothing is uploaded. For the example fields it writes the subject /C=US/ST=California/L=San Francisco/O=Example Shop/CN=shop.example.com with the names shop.example.com and www.shop.example.com, signed with an RSA 2048 key, ready to paste into any certificate authority's order form.
| Key | Signature | When to choose it |
|---|---|---|
| RSA 2048 | SHA-256 with RSA | Accepted by every certificate authority and server; the usual choice |
| RSA 3072 | SHA-256 with RSA | Stronger RSA, a little slower to use |
| RSA 4096 | SHA-256 with RSA | Strongest RSA; takes a few seconds to make |
| ECDSA P-256 | ECDSA with SHA-256 | Small and fast; supported by all current CAs and browsers |
| ECDSA P-384 | ECDSA with SHA-384 | Larger elliptic curve, for policies that ask for it |
Nothing is uploaded: this runs in your browser.
Type the domain name, and any other names the certificate should cover, comma separated.
Fill in the organization, city and two-letter country if your certificate authority asks for them.
Pick a key type (RSA 2048 suits almost every case) and press Generate CSR and key.
Copy the CSR to your certificate authority and save the private key now; it is not stored.
A certificate signing request (CSR) is the form you send to a certificate authority to get an SSL/TLS certificate. It holds the domain names, optionally your organization, and a public key, and it is signed with the matching private key to prove you hold it. The authority checks you control the domains and returns a certificate for that public key.
The private key is the secret half and must stay on your side. A CSR generator that runs on a web server makes the key there, so the site has seen it. Here the key pair is made by your browser's WebCrypto, the CSR is signed in the page, and both are shown once and then forgotten.
| Question | Answer |
|---|---|
| Key types | RSA 2048, 3072 or 4096 with SHA-256; ECDSA P-256 or P-384 |
| Names | The domain plus any extra names, in subjectAltName, as public CAs require |
| Checks | Domain without https:// or a path, two-letter country, 64-character name fields |
| Output | The CSR (PEM) and the private key (PKCS#8 PEM), copied or saved as .csr and .key |
| Where it runs | In your browser; the key is never uploaded or stored |
Checked on 16 November 2026 against RFC 2986, RFC 5280 and the CA/Browser Forum Baseline Requirements. Page last updated on 16 November 2026.
The page prints the matching command, for this example: openssl req -new -newkey rsa:2048 -nodes -keyout shop.example.com.key -out shop.example.com.csr with the same -subj and subjectAltName. To read a CSR back before you send it, use the CSR decoder; when the certificate arrives, the certificate key matcher confirms it fits the key.
Type the domain name, add any other names and optional organization details, pick a key type and press Generate CSR and key. The private key and the signing request appear at once; copy the CSR into your certificate authority's order form and save the .key file somewhere safe on the server.
Only when the private key is made on your own device. Here your browser creates the key pair with WebCrypto and signs the request in the page; nothing is sent to a server or stored. The page cannot show the key again, so save it before closing the tab.
RSA 2048 works with every certificate authority, server and client, and is the usual choice. ECDSA P-256 gives smaller, faster keys and is accepted by all current public CAs and browsers. RSA 4096 is stronger but slower and rarely required; P-384 suits policies that name it.
Yes for public certificates: browsers read the names in subjectAltName, not the Common Name. The generator always puts the main domain there and adds every extra name you type, such as www.example.com. Many authorities add the www name themselves, but listing it does no harm.
The main domain the certificate protects, exactly as visitors type it, such as www.example.com or *.example.com for a wildcard. Leave out https:// and any path. The generator refuses those mistakes before it makes a key, the same ones the CSR decoder warns about.
Nowhere: the key exists only in the open page until you copy or download it. Save the .key file and keep it private; the certificate you receive works only with this key. Losing it means generating a new CSR and asking the authority to reissue the certificate.
Rates and rules change; check the source before you rely on a figure.
Still stuck? Ask about CSR Generator: Create a CSR and Private Key in Your Browser and anybody who knows can answer. No account needed.
Same job, other tools: HMAC-SHA256 Generator – Compute an HMAC-SHA256 signature in hex and Base64 · Bcrypt Generator – Generate a bcrypt hash for a test user or a config file · 2FA Code Generator – Get the current two-factor code from a setup key, without a phone · CSR Decoder – CSR decoder: see what a certificate signing request asks for before it goes to a CA.
On the related tools: JWT Decoder – Paste a token to read its header, payload and expiry.
On the same topic: Certificate Key Matcher: Does the Private Key Match? – Check that a private key belongs to an SSL certificate or CSR; the key is never uploaded · PEM to PFX Converter: Make a .pfx / .p12 in Your Browser – PEM certificate and key to a password-protected .pfx (PKCS#12), key never uploaded.