Security and Identifier Tools

Hashing, signing, decoding and generating the strings that security depends on. Compute a checksum, sign a payload with a shared secret, hash a password the way a login system does, read what is inside a JWT, and generate passwords and UUIDs from a proper random source — all without the input leaving your machine.

Every Security & Identifiers tool

Hashes

The hash tool computes MD5, SHA-1, SHA-256 and SHA-512 for text or a dropped file, with hex and Base64 output. Use it to verify a download against a published checksum, to produce a cache key, or to check what a system stored. The page is honest about which algorithms are still fit for which purposes — MD5 and SHA-1 for checksums, not for anything an attacker might target.

Signatures and password hashing

HMAC combines a hash with a secret key so the result proves both integrity and possession of the key; the tool produces HMAC-SHA256 and siblings for testing webhook signatures and API authentication. Bcrypt is what login systems should use for passwords: slow by design, salted, with an adjustable cost factor. The bcrypt tool hashes a password at the cost you choose and verifies a password against an existing hash, which is exactly what you need when debugging an authentication flow.

Tokens

The JWT decoder splits a token into header, payload and signature and shows the claims with expiry and issued-at times rendered as dates, so you can see why a token was rejected. It decodes; it does not verify unless you supply the secret, and it says so clearly, because a decoded token is not a trusted token.

Generating identifiers

The password generator draws from the browser's cryptographic random source with control over length, character classes and excluded look-alikes, and shows an entropy estimate. The UUID generator produces v4 random UUIDs, and v7 time-ordered ones where you want sortable keys, singly or in bulk. The UUID validator checks a string's format and reports its version and variant.

The important part

Everything runs in your browser via the Web Crypto API. Secrets, tokens and passwords you paste here are not transmitted, logged or stored anywhere, and nothing persists after the tab closes.