Generate RSA & ECC Certificate Signing Requests Online
Generate a secure Certificate Signing Request (CSR) and Private Key for your SSL certificate. Supports 2048-bit RSA, 4096-bit RSA, and modern ECC Elliptic Curve algorithms.
📖 Learn more: What is a CSR? Beginner's guide
Generate CSR
What is a Certificate Signing Request (CSR)?
A Certificate Signing Request (CSR) is an encoded text file that contains information about your organization and the domain you want to secure. You submit this CSR to a Certificate Authority (CA) to obtain an SSL/TLS certificate.
RSA vs. ECC: Which Should You Use?
RSA (Rivest–Shamir–Adleman)
The industry standard for decades. Highly compatible with almost all web browsers, servers, and devices. RSA 2048-bit is the minimum recommended strength, while 4096-bit offers future-proof security but requires more CPU power.
ECC (Elliptic Curve Cryptography)
The modern alternative. ECC provides the same security level as RSA but with much smaller key sizes (e.g., 256-bit ECC is as secure as 3072-bit RSA). This results in faster handshakes and lower server overhead.
CSR Information Fields:
- Common Name (CN): Your domain name (e.g., example.com)
- Organization (O): Your company name
- Organizational Unit (OU): Department name
- City/Locality (L): City where your organization is located
- State/Province (ST): State or province
- Country (C): Two-letter country code
- Public Key: Generated using RSA or ECC algorithm
Frequently Asked Questions
What is a CSR?
A Certificate Signing Request (CSR) is a block of encoded text containing your public key and details such as your domain name. You submit it to a Certificate Authority to apply for an SSL certificate.
Should I use RSA or ECC for my CSR?
RSA 2048-bit works with virtually every client. ECC (P-256) gives equivalent security with a much smaller key and faster handshakes, and is supported by all modern browsers and servers.
Is my private key stored on your server?
No. Your private key is generated and returned to you immediately, and it is never stored on our systems. Save it securely, because your certificate will only work with this key.
What should I enter as the Common Name?
Enter the exact hostname you want to secure, such as www.example.com, or *.example.com for a wildcard certificate covering all first-level subdomains.