Developer

Gerador de par de chaves RSA

Gere pares de chaves RSA públicas e privadas seguras (até 4.096 bits) inteiramente em seu navegador. Ele roda inteiramente no seu navegador — nenhum dado é enviado para nenhum servidor, nenhuma conta é necessária e é totalmente gratuito.

Security Note: These keys are generated securely entirely within your browser using the WebCrypto API. They are never transmitted over the internet or stored on our servers.

The Complete Guide to RSA Keys: Public-Key Cryptography Explained

RSA is the backbone of modern public-key cryptography. From TLS/HTTPS certificates to SSH authentication to PGP email encryption, RSA key pairs secure billions of connections every day. Our free RSA Key Generator creates 1024, 2048, or 4096-bit key pairs entirely in your browser — no server, no storage, no exposure.

How RSA Works

RSA is based on the mathematical difficulty of factoring the product of two large prime numbers. The process works as follows:

  1. Two large prime numbers (p and q) are randomly selected
  2. They are multiplied to produce the modulus n = p × q
  3. A public exponent (usually 65537) is chosen
  4. The public key is (n, e); the private key uses the modular inverse of e
  5. Anyone with your public key can encrypt data that only your private key can decrypt

RSA Key Sizes and Security Levels

  • 1024-bit: Deprecated. Broken by well-funded attackers. Do not use for production.
  • 2048-bit: Current standard. NIST-recommended until at least 2030. Used in most TLS certificates.
  • 4096-bit: Future-proof. Significantly more secure but ~4× slower operations. Recommended for long-lived keys.

Common Use Cases

  • SSH authentication: Replace password login with RSA key-pair authentication (more secure, more convenient)
  • TLS/HTTPS certificates: Web servers use RSA keys in their TLS certificates
  • JWT signing: RS256 JWTs use RSA private keys for signing and public keys for verification
  • PGP/GPG email encryption: RSA keys encrypt email content end-to-end
  • Code signing: Proving that software hasn't been tampered with

Private Key Security

Your private key is the crown jewel — losing it or exposing it compromises everything protected by the key pair. Best practices:

  • Store private keys with filesystem permissions 600 (owner read-only)
  • Encrypt private keys with a passphrase at rest
  • Never commit private keys to version control (add *.pem to .gitignore)
  • Rotate keys periodically — most organizations rotate annually

For general password generation, see our Password Generator. To hash data, use our Hash Generator.

Compartilhar: