CSR Builder (with SAN)
Create a new key pair and a PKCS#10 certificate signing request with Subject Alternative Names for DNS names, IP addresses, emails and URIs. You get the CSR and the private key in PEM format.
Use the tool
Why this tool exists
Modern browsers ignore the common name and look at Subject Alternative Names, so a request without SANs gives a certificate that browsers reject. Command-line OpenSSL can do it, but it needs a config file with a SAN section, and getting the syntax right on the first try is rare.
This builder takes a list of names, a key type and your organisation details, then creates the key and request in your browser. Nothing is uploaded, and the private key is shown only on your screen. You must still store that key safely, as anyone who has it can impersonate your site. Treat a key generated on any web page with caution, and for production systems prefer generating the key on the server.
How to use it
- Enter the Subject Alternative Names, one per line, with optional DNS:, IP:, email: or URI: prefixes.
- Choose a key type: ECDSA P-256, P-384 or RSA 2048, 3072 or 4096.
- Fill in the common name, organisation and other subject fields as needed.
- Copy the CSR to send to your certificate authority, and store the private key safely.
Frequently asked questions
Is the private key sent anywhere?
No. Both the key and the CSR are made in your browser and shown on the page. Copy and store the key yourself. If you reload the page, it is gone and cannot be recovered.
Should I use this for a production server?
Prefer generating production keys on the server itself, where they never leave the machine. This tool suits test environments, internal labs and learning how a CSR is structured.
What if I leave the common name blank?
It defaults to the first DNS name in the SAN list. Browsers rely on the SAN entries anyway, so make sure every hostname the certificate must cover is listed there.