Hash & Token Tools Hub
About this hub
When you compare a checksum, mint ids, or debug a JWT, you want a local check. This hub groups HASH, UUID, JWT verify, and password strength. It is not a substitute for salted password hashing or server-side auth.
What it is for
When you compare a checksum, mint ids, or debug a JWT, you want a local check. This hub groups HASH, UUID, JWT verify, and password strength. It is not a substitute for salted password hashing or server-side auth.
When to use it
- A doc lists SHA-256 and you want to confirm a string
- You need bulk UUID v4 or v7 for keys or request ids
- An API returns signature invalid and you want to reproduce it
Why use these tools
- The hash page is for digests; the MD5 page only covers 16/32-character layouts
- UUIDs identify records; hashes fingerprint bytes—different jobs
- JWT verify answers the signature; decode only shows claims
FAQ
Are passwords uploaded?
No. Strength checks, hashing, and verify run in the browser.
Can I store passwords with the hash tool?
No. Use a salted password hash. This hub only computes common digests.
Is a UUID a password?
No. It is an identifier. Use the strength checker for passphrases.
JWT verify vs decode?
Decode shows claims. Verify checks signature, expiry, and iss/aud/sub. Production still verifies on the server.
Why is there a separate MD5 page?
Some legacy APIs want 16/32-character MD5. Prefer the hash generator for SHA-256 checksums.
Is the string cipher for production?
No. Demo keys only. Real systems need proper key management.
Tools in this hub