Hash Identifier

Paste any hash, checksum, address, or token and see a ranked list of candidate algorithms. The tool inspects the input's length, character set, and any known prefix (like $2b$ for bcrypt or 0x for Ethereum), then returns a short list of could-be candidates with a one-line reason for each. Pure client-side, no upload.

0 chars

The identifier never sends your input anywhere — every check runs in your browser.

Try one — click any chip to load it
How the identifier works
  • Prefixes come first. A handful of formats are recognised by their leading bytes: $2b$ (bcrypt), $argon2…$, $5$ / $6$ (glibc SHA-256 / SHA-512 crypt), $1$ (md5crypt), bc1 / tb1 (Bitcoin Bech32), 0x (Ethereum & hex blob), Qm (IPFS CIDv0), b… (IPFS CIDv1 in base32), eyJ (JWT).
  • UUIDs are recognised by structure. The 8-4-4-4-12 pattern with a version nibble (1-8) and a variant nibble is checked before any character-set dispatch so UUIDs are not misread as base64url.
  • Everything else is a length / charset match. Hex strings are looked up in a table by their character count (8 / 16 / 32 / 40 / 56 / 64 / 96 / 128), base64 / base64url are matched by size, base58 by Bitcoin / IPFS / XRP address lengths.
  • Disambiguation is conservative. A 16-character all-uppercase alphanumeric chunk could be either base32 or base64 — the tool prefers base32 because real base64 is usually padded, and it labels the choice so you can override it. A mixed-case alphanumeric string with no special characters is base58 (Bitcoin / Ripple / IPFS) rather than base64.
  • The candidates list is a hint, not a verdict. Two algorithms with identical output length — MD5 and RIPEMD-128, for example — cannot be distinguished from the hash alone. The page ranks by popularity within a length class, so the most common algorithm for a given shape appears first.