Generate Elliptic Curve key pairs (P-256, P-384, P-521) for digital signatures and key exchange.
Pick P-256, P-384, or P-521 to create a new elliptic-curve private key and its mathematically corresponding public key. Generation occurs in the browser, so the key material is not uploaded by the tool. Curve selection fixes the domain parameters; it does not make the result repeatable, and generating again should produce a different pair. A frequent source of confusion is the name P-521: it identifies a 521-bit prime-field curve, not a misspelling of P-512.
Each offered choice is a named NIST prime-field curve. The selected name determines the finite field, curve equation, base point, and group order used to relate the two keys. P-256, P-384, and P-521 are not interchangeable labels. The curve affects key and signature component sizes, but key generation does not choose the message digest later used by ECDSA.
The private half is a secret scalar in the valid range for the selected curve. Its public half is the curve point obtained by multiplying the curve's base point by that scalar. A verifier can receive the public half without learning the private value. Pair generation does not sign data, calculate a shared secret, issue a certificate, or attach an identity.
The underlying private scalar and public point can be suitable for either operation on these supported curves, but protocol rules, key-usage restrictions, and import formats may forbid reuse. Generating the pair does not perform an ECDH exchange or establish a shared secret. Confirm that the destination accepts the named curve and encoding for key agreement; otherwise, no.
Use the exact named curve required by the protocol or receiving application. A P-256 key cannot become P-384 or P-521 by changing its label, and support for one EC curve does not imply support for the others. If no requirement is documented, this generator cannot determine compatibility; inspect the destination's accepted curve and key format first.
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.