Skip to content

Webinar: Register For Our Upcoming Webinar

Register Now
The CSR Generator is a fast, form-based tool that takes the complexity out of certificate request creation. Instead of running multi-step OpenSSL commands and manually tracking output files, you simply choose a compliance profile, fill in your certificate details, and walk away with everything you need: your CSR, private key, OpenSSL command, and openssl.cnf, generated correctly, every single time.
1
Compliance Profile
Custom
Organization security policy
Custom Fields
NIST
SP 800-57
OID optional
CA/B Forum
TLS BR v2
OID required
RFC 5280
IETF X.509
OID partial
ETSI 319
EU eIDAS
OID required
FIPS 140-3
CMVP
OID optional
TPM 2.0
TCG Spec
OID required
DICE X.509
TCG DICE
OID required
SPDM
DSP0274
OID required
Common Criteria
ISO 15408
OID required
2
Certificate Details
Wildcard: *.yourdomain.com
Comma-separated
Key Settings
keyUsageAllowed cryptographic operations
OFF
Recommended- clients use this to check what the key is allowed to do.
extendedKeyUsageAllowed certificate purpose
OFF
Usually not critical — allows multi-purpose certs
basicConstraintsCA or end-entity rule
OFF
Must be critical when CA:TRUE- RFC 5280
CA
pathLen max SubCA chains allowed (CA:TRUE only)
subjectKeyIdentifier= hash: public key fingerprint
OFF
Always set to hash — OpenSSL computes a SHA-1 hash of the SubjectPublicKeyInfo. Enables key-based chain building by CAs and path validation.
subjectKeyIdentifier = hash
authorityKeyIdentifier= keyid, issuer — filled by CA at signing
OFF
References the issuing CA's key. Include in .cnf as a hint — the actual value is computed by the CA during signing, not stored in the CSR.
authorityKeyIdentifier = keyid, issuer
certificatePoliciesPolicy OID for this certificate
OFF
Custom OID ExtensionsProfile-specific / proprietary
OFF

Add OIDs for SPDM, DICE, TPM 2.0, ETSI, or any profile-specific extension. Written into [v3_req] in the downloaded .cnf.

Your output will appear here

Fill in your certificate details on the left and click Generate CSR + Private Key. Everything runs in your browser — nothing is sent to any server.

Certificate Signing Request .csr
RSA Private Key .key
OpenSSL Command
openssl.cnf Config .cnf
✓ Compliant
CSR (PEM Format)
Private Key (PEM Format)
OpenSSL Command
openssl.cnf Config

Frequently Asked Questions

Everything you need to know about generating and using your CSR.

How to generate a CSR using EC's CSR Generator tool?

Generating a CSR has never been easier. Simply open the CSR Generator tool and follow three straightforward steps.

1
Select a Compliance Profile

Choose the profile that matches your requirements — whether that's an industry standard like NIST SP 800-57, CA/B Forum, FIPS 140-3, or a fully Custom profile based on your organization's own security policy.

2
Fill in Certificate Details & Key Settings

Enter your domain name (Common Name), Organization, Department, City, State, Country, and optionally Subject Alternative Names (SANs) if the certificate needs to cover multiple domains. Choose your Key Type (RSA, ECC), ECC Curve, and Signature Hash algorithm.

3
Optionally configure X.509 v3 Extensions

If your use case requires it, toggle on extensions such as keyUsage, extendedKeyUsage, basicConstraints, or custom OID extensions.

Once everything is filled in, click "Generate CSR + Private Key" and the tool instantly produces your Certificate Signing Request and private key in .pem format.

What to do once you get the CSR and Private Key?

Once the tool generates your CSR and Private Key, here is what you do with each.

1
Submit the CSR to your Certificate Authority (CA)

Such as Microsoft CA. The CA will verify the CSR and issue your signed digital certificate.

2
Download and install the Private Key

Install it on your server alongside the signed certificate once the CA has processed your request.

3
Store the private key securely

Keep it in a hardware-based module and never share it with anyone. It cannot be recovered once lost.

Please Note: Encryption Consulting LLC does not possess or store any information entered or generated here. The user is solely responsible for securing and managing their private key.

What is the use of the openssl.cnf file?

The openssl.cnf file is the configuration file that OpenSSL uses behind the scenes to generate your CSR. Normally you would have to write this file yourself, defining all your certificate fields, extensions, key usage flags, OIDs, and SANs in the correct format. The CSR Generator builds it automatically based on the details you provide.

1
Full transparency

See exactly what parameters were used to generate your CSR.

2
Reproducibility

If you need to regenerate the same CSR or automate the process in a pipeline, use this file directly with the OpenSSL command the tool also provides.

3
Auditing

Security teams can review the openssl.cnf to verify that the certificate was generated according to the organization's cryptographic policy and standards.