ToolsForWeb

Saved

Tap ☆ on any tool to keep it here.

toolsforweb

Security

Hashing, tokens, certificates, and vulnerability scoring in your browser: JWT/JWKS tools, password generators, CSR/X.509 decoders, CVSS/SSVC calculators.

21 tools

About Security

Security utilities that run in your browser, so tokens, keys and passwords never leave the page. Decode a JWT and inspect its claims, sign a test token with HS256, and inspect a JWKS key set with JWK to PEM conversion. Generate strong passwords or passphrases with their entropy, hash text with MD5, SHA-1 or SHA-2, compute HMACs, identify an unknown hash, create and verify bcrypt hashes, and generate TOTP codes.

For certificates and incident work, decode X.509 certificates and CSRs, verify a downloaded file against its checksum, trace an email's route and authentication results from its headers, and unwrap SafeLinks and other rewritten URLs. Score vulnerabilities with the CVSS and SSVC calculators, generate and analyze Content-Security-Policy headers, and generate a security.txt file.

Questions

Is it safe to paste a JWT into an online decoder?

Only if the decoder runs locally. This one decodes in your browser and sends nothing to a server. A JWT's payload is only base64url-encoded, not encrypted, so anyone who holds the token can read it; treat live tokens like passwords.

Is MD5 or SHA-1 safe for passwords?

No. They are fast hashes, which makes brute-forcing easy, and both have known collision attacks. Store passwords with a slow, salted algorithm such as bcrypt or Argon2. MD5 and SHA-1 are still fine for non-security checksums.

How long should a password be?

Aim for around 80 bits of entropy or more: about 13 random characters drawn from upper and lower case, digits and symbols, or an 8-word passphrase from a 1,000-word list. The password generator shows the entropy of every result so you can compare.