Generate Certificate Signing Requests with organization, domain, and key information using Web Crypto API.
Before a certificate authority can issue a certificate for a newly created key, it needs a signed request. This tool takes the domain, organization, and key choices entered in the form, creates the key material with Web Crypto in the current browser, and produces a PKCS #10 CSR containing the public key and requested subject data. Nothing is uploaded. The frequent mistake is treating the CSR as the certificate, or assuming it contains the private key. It is only the enrollment request, and the issued certificate must later be paired with the matching private key.
The form values become requested subject information in the certification request, alongside the generated public key. Web Crypto creates the key material and signs the request data with the corresponding private key. That signature lets a recipient detect changes to the signed request and verify it against the included public key; it does not make the request certificate-authority approved.
The generated request is an input to certificate enrollment, not the final deployable object. A certificate authority can validate the request and issue a certificate whose public key matches the CSR. The private key remains separate and must be retained securely. When the certificate arrives, the server or appliance needs both that certificate and the matching key.
No. A CSR is a signed enrollment request containing a public key and requested identity information. Submit it to a public certificate authority or internal PKI. If the request is approved, the authority returns a certificate. Install that certificate with the private key corresponding to the public key embedded in the CSR.
Generating a new key pair changes the public key and therefore changes the signed CSR, even when the domain and organization fields stay the same. This is expected. Do not test equivalence by comparing CSR text. Instead, inspect the requested identity fields and key properties, and retain the private key belonging to the CSR actually submitted.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.