CSR Generator
Advanced CSR, Private Key and Certificate triplet generator
- 100% Free
- Files stay private
- Works in your browser
Extra DNS names, IP addresses, emails or URLs the certificate should cover.
Everything runs locally with node-forge. Your details and the generated private key never leave this device. Submit the CSR to a Certificate Authority to obtain a signed certificate.
How it works
Enter your details
Type your domain into Common Name (CN), then add optional details like Organization (O), Country (C) or Subject Alternative Names (SAN).
Generate your CSR
Choose a Key size, then press Generate CSR. The key and request are created right in your browser, which can take a few seconds.
Copy or download files
Switch between the CSR, Private Key and Certificate tabs, then copy each one or download it as a file.
Generate a PKCS#10 Certificate Signing Request, a matching RSA private key, and a self-signed certificate entirely in your browser. Fill in your subject details, choose a key size, and download all three in PEM format.
What is CSR Generator?
CSR Generator is a free tool that creates a Certificate Signing Request, the standardized message you submit to a Certificate Authority to obtain an SSL/TLS certificate. It builds an RSA keypair locally, assembles the request from your subject fields and optional Subject Alternative Names, and signs it with SHA-256. Alongside the CSR it emits the matching private key and a self-signed certificate, so you have everything needed to request or test a certificate.
Who Benefits from This Tool
- Web administrators: prepare a CSR to submit to a Certificate Authority for a domain.
- DevOps engineers: generate keys and requests as part of provisioning or automation testing.
- Developers: create a self-signed certificate for local HTTPS during development.
- System integrators: produce CSRs with multiple SANs for multi-domain deployments.
- Students: learn how CSRs, keys, and certificates relate in the TLS trust chain.
Key Features
- Full subject fields: Common Name, Organization, Unit, Locality, State, Country, and Email.
- Subject Alternative Names: add extra DNS names, IP addresses, emails, or URLs, one per line or comma-separated.
- Selectable key size: choose 2048, 3072, or 4096-bit RSA keys.
- SHA-256 signing: the request is signed with a modern, widely accepted algorithm.
- Three outputs: CSR, private key, and a matching self-signed certificate in separate tabs.
- Copy and download: export each PEM block with a filename derived from your Common Name.
- Local generation: the keypair is built in your browser with node-forge and never uploaded.
How to Use
- Enter the Common Name (the domain the certificate is for). This field is required.
- Fill in the optional Organization, Unit, Locality, State, Country, and Email fields.
- Add any Subject Alternative Names, then choose a key size.
- Click Generate CSR and wait a few seconds while the key is created.
- Switch between the CSR, Private Key, and Certificate tabs to copy or download each PEM file.
Common Use Cases
- Requesting a production SSL/TLS certificate from a commercial or free Certificate Authority.
- Creating a self-signed certificate for a staging or internal environment.
- Generating a multi-domain CSR with several SAN entries for a single certificate.
- Producing test keys and requests while building certificate automation.
- Replacing an expiring certificate by generating a fresh key and request.
Tips and Best Practices
- Use 2048-bit keys for broad compatibility, or 3072/4096-bit when you need stronger keys and can accept slower generation.
- Set the Common Name to the exact domain, and list every hostname the certificate must cover in the SAN field.
- Enter the Country as a two-letter ISO code, such as US or GB.
- Save the private key immediately and store it securely. You cannot recover it later, and it must match the issued certificate.
- Submit only the CSR to your Certificate Authority; never share the private key.
Limitations and Notes
Everything runs locally in your browser using node-forge, so your details and the generated private key never leave your device. The self-signed certificate included here is convenient for testing and internal use, but browsers will not trust it automatically. Production sites require a certificate signed by a recognized Certificate Authority, which you obtain by submitting the CSR. Larger key sizes take noticeably longer to generate. Because the private key exists only in your browser session, download and back it up before leaving the page.
FAQs
A Certificate Signing Request contains your public key and subject details. You send it to a Certificate Authority, which validates your information and issues a signed certificate that matches your private key.
No. The keypair is generated in your browser with node-forge and never transmitted. You must download and store the private key yourself.
2048-bit is the recommended default and works everywhere. Choose 3072 or 4096-bit for stronger keys, keeping in mind that generation takes longer.
Only the Common Name is required. Other fields are optional, though many Certificate Authorities expect Organization and Country for business certificates.
It works for local or internal testing, but browsers will warn visitors because it is not signed by a trusted authority. For public sites, submit the CSR to a Certificate Authority instead.
SANs are additional identities the certificate should cover, such as extra domains, subdomains, IP addresses, or emails. List them so one certificate can secure multiple hostnames.