Generate a CSR and private key in your browser

Most online CSR generators create your private key on their server, so the website has seen the one secret your certificate depends on. Here the key is generated by your browser’s own cryptography, inside this tab: you can switch the network off after the page loads and it keeps working. You get the CSR to send to the certificate authority and the key to install on your server, both in the PEM format OpenSSL, Apache, nginx and IIS read.

Loading the tool…

How it works

  1. Choose the key type (RSA 2048 if unsure, ECDSA P-256 for a smaller, faster key) and fill in the common name and the other subject fields your certificate authority asks for.
  2. List every host name and IP address the certificate must cover; the common name is added to the list by default. Optionally set a passphrase to encrypt the key file.
  3. Generate, then download or copy the private key at once — it exists only in this tab — and send the CSR to your certificate authority.

Why nothing is uploaded

Every operation on this page is done by code running inside your browser tab, using the same engine that renders web pages. The file is read from disk into your tab’s memory, transformed there, and written back out as a download. It is never sent anywhere — not to us, not to a third party.

Verify it yourself

  1. Open your browser’s developer tools (F12) and select the Network tab.
  2. Load your file and run the tool.
  3. The only requests you will see fetch the tool’s own code — and, for a few heavy tools, their open-source engine (also from this site) or an AI model from Hugging Face — plus one small page-view ping to loreatec.jp (page address and title, nothing more). None of them carry your file.

Proof it stays local →

Frequently asked questions

Why should the private key not be generated by a website?

Whoever holds the private key can impersonate your server and, with older key exchange methods, read recorded traffic. A generator that runs on a server has had your key in its hands, and you cannot check whether it kept a copy. This page makes the key with WebCrypto inside your browser tab; nothing is uploaded, and you can verify that by disconnecting the network before you press Generate.

Which key type should I choose?

RSA 2048 works everywhere, including old clients and appliances. ECDSA P-256 gives the same security with a much smaller key and faster handshakes, and every current public certificate authority accepts it. RSA 3072/4096 and P-384 are for policies that demand them. Ed25519 is offered only where your browser supports it, and only for private infrastructure: public certificate authorities do not issue Ed25519 certificates.

Do I still need the common name?

Browsers ignore the common name and check only the Subject Alternative Names, so every host name must be in the SAN list; the common name is copied there by default. International domain names are converted to Punycode (xn--…), which is how they must appear in a certificate.

Will OpenSSL and my server accept the files?

Yes. The CSR is standard PKCS#10 and the key is PKCS#8 PEM, the format OpenSSL 1.1 and 3.x, Apache, nginx and most appliances read. The page reads the CSR back and verifies its signature before showing it, and gives the two OpenSSL commands to check both files yourself. An encrypted key uses PBES2 with PBKDF2-HMAC-SHA256 and AES-256-CBC, which OpenSSL opens with your passphrase.

What if I lose the key?

It cannot be recovered: it was never stored anywhere but this tab. Generate a new key and CSR and ask your certificate authority to reissue the certificate; most do it free of charge.