Security
Create htpasswd entries for Apache and nginx — bcrypt by default, random salts, no server round-trips.
Hashing runs locally in your browser. Your password is never uploaded, logged, or stored.
bcrypt ($2b$) is the right choice for anything new: it is deliberately slow, salted with 128 bits of cryptographic randomness, and supported by Apache 2.4+, nginx (via the ngx_http_auth_basic module compiled with libcrypt), and Caddy. SHA-1 ({SHA}) is kept for legacy servers only — it is fast and unsalted, so treat it as a compatibility fallback, not a security choice.
The bcrypt salt is generated with crypto.getRandomValues, never a predictable PRNG. Want to work with raw bcrypt hashes? Use the bcrypt tool, or generate a strong password first with the Password Generator.
Add basic auth to a staging environment or admin panel with a single .htpasswd entry.
Re-hash old SHA-1 or plaintext entries as bcrypt when you update your server config.
Decode JWT header and payload locally, then run security checks: weak algorithms, expiry, risky claims.
Generate strong random passwords with crypto.getRandomValues — pick length and character sets.
Generate cryptographically secure random tokens in hex, base64, or URL-safe base64.
Generate bcrypt password hashes with adjustable cost and verify hashes against passwords.
Looking for something else? Browse all tools