Security & Crypto tools handle the primitives of modern application security, hashing, encryption, key generation, token handling, and password policy. These are the tools you reach for when implementing authentication, auditing token claims, or verifying that your password storage meets current NIST and OWASP guidelines.

Common Workflows & Recommended Tools

Generate an RSA key pair for JWT signing (RS256/PS256)

→ RSA Key Pair Generator

Encrypt a payload with AES-256-GCM before storing it

→ AES Encrypt / Decrypt

Generate a cryptographically strong password or token

→ Password Generator

Decode a JWT to inspect claims without sending it to a server

→ JWT Decoder

Check if a password meets entropy and length requirements

→ Password Generator

Common Mistakes to Avoid

✗Encrypting large files directly with RSA-OAEP, RSA-2048 can only encrypt 245 bytes; use hybrid encryption with an AES session key.
✗Generating 1024-bit RSA keys because an old tutorial said so, NIST deprecated 1024-bit in 2013 and browsers reject them for TLS.
✗Using MD5 or SHA-1 for password hashing, use Argon2id or bcrypt with a per-user salt and adequate work factor.
✗Storing JWTs in localStorage where any XSS vulnerability can exfiltrate them, prefer httpOnly Secure cookies with SameSite=Strict.

Privacy-First by Design

Key material, passwords, and tokens are among the most sensitive data a developer handles. Every cryptographic operation in this category uses the Web Crypto API or runs entirely client-side, private keys and secrets never cross a network boundary.

Frequently Asked Questions

Is it safe to generate cryptographic keys in a browser?

Yes. The Web Crypto API uses the same cryptographic backends (BoringSSL, NSS, CoreCrypto) that power TLS handshakes. Keys are generated locally and never transmitted.

Which hashing algorithm should I use for passwords?

Use Argon2id (winner of the Password Hashing Competition) or bcrypt with a cost factor of at least 12. Never use MD5, SHA-1, or plain SHA-256 for passwords.

What RSA key size do I need in 2026?

2048-bit RSA provides ~112 bits of security and is NIST-approved through 2030. Use 4096-bit for long-lived signing keys where performance is acceptable.