Security tools generate and inspect the values used for authentication and encryption — passwords, hashes, tokens, and SSL certificates. Protect accounts, review server certificates, or build API auth headers, all handled safely inside your browser.
What are security tools?
Logging in, connecting over HTTPS, and calling an API all come down to “create a secret, then verify it.” That means generating strong random passwords, fingerprinting data with a hash, and checking an SSL certificate's validity and issuer. The tools in this category process these values locally — using the browser's Web Crypto API and similar — without sending them to a server, so your actual passwords and private keys never leave your machine.
🔑
Password Generator
Generate strong random passwords
#️⃣
Hash Generator
Generate MD5, SHA-1, SHA-256 hashes
📱
QR Code Generator
Turn text/URLs into a QR code
🗝️
htpasswd Generator
Generate APR1-MD5 hashed passwords
🔍
SSL Certificate Viewer
Check issuer, validity & SANs
📜
CSR Viewer
Check CSR subject & public key info
♻️
SSL Certificate Converter
Convert PEM ↔ DER (HEX)
🤝
Cert/Key Pair Checker
Verify a certificate matches its private key
🩺
SSL Checker
Check HTTPS connectivity & trust
🪄
Self-Signed Certificate Generator
Generate a self-signed SSL cert & key
🔐
Base64 Encode/Decode
Convert text ↔ Base64
🔑
HTTP Auth Header Generator
Build Basic/Bearer Authorization headers
🪪
JWT Decoder
Inspect JWT header/payload, verify HS256
🎫
Random Token Generator
Generate Hex/Base64/UUID tokens
🔒
Jasypt Encrypt/Decrypt
Encrypt/decrypt Spring Boot ENC(...) values
When to use them
- New accounts & server setup — use the Password Generator and Random Token Generator for unpredictable secrets
- File integrity checks — use Hash Generator to confirm a downloaded file matches the original
- Tracking certificate issues — use SSL Certificate Viewer and SSL Checker to inspect expiry, issuer and chain status
- API integration — use the HTTP Authentication Header generator and JWT Decoder to build and inspect auth headers
Frequently asked questions
- Are the passwords/keys I enter sent to a server?
- No. Hashing, encryption and certificate parsing all run in your browser, and your input never leaves the page.
- Can I use MD5/SHA-1 hashes to store passwords?
- Not recommended. They're fine for file integrity checks, but for storing passwords use a dedicated algorithm like bcrypt or Argon2.