| Hash | Candidate Types |
|---|---|
| {{ row.hash }} | {{ c.name }} — |
{{ jsonPretty }}
Cryptographic and checksum hashes convert any data — from a short phrase to a multi-gigabyte file — into a fixed-size, seemingly random digest. Although different algorithms share similar hexadecimal or Base64 appearances, each format has a distinctive length or marker that reveals its origin.
The Hash Type Identifier inspects these structural cues and compares them with an internal rule-set to propose one or more plausible algorithms for every supplied digest. Multiple hashes, pasted or uploaded, are processed instantly in your browser, and results appear as a sortable table or prettified JSON for effortless export.
This tool is ideal when you inherit legacy databases, forensic images, or log excerpts and need to prioritise cracking strategies or compliance checks. Do not rely solely on heuristic matches for critical security decisions.
Hash digests act as deterministic, one-way fingerprints. Their bit-length dictates the rendered character count, while optional prefixes (for example “$2b$” in bcrypt) encode algorithm and cost information. By cross-referencing these immutable attributes against a curated catalogue of signature patterns, the engine infers candidate algorithms without calculating any hashes.
Where Ralg is the regular-expression for algorithm alg, and A is the algorithm set.
| Symbol | Meaning | Unit | Typical Range | Sensitivity |
|---|---|---|---|---|
L | Digest character count | chars | 8 – 128 | High |
P | Algorithm-specific prefix | string | “$2b$”, “{SSHA}” | High |
S | Allowed symbol set | regex class | [a-f0-9]+ / [A-Za-z0-9+/=]+ | Medium |
C | Candidate list | array | 0 – 5 items | N/A |
T | Processing time | ms | < 5 ms per hash | Low |
C.length = 1).Input hash: d41d8cd98f00b204e9800998ecf8427e
The 32-character hexadecimal length uniquely identifies MD5. Output array: [{"name":"MD5"}]
The pattern-matching routine executes in O(n · m), where n is the number of hashes and m the pattern count (currently 13). Processing is entirely client-side, guaranteeing near-instant results and zero network latency. The implementation follows ES2020 standards and runs on all evergreen browsers.
Follow this concise sequence to classify your digests accurately.
Both produce 32-character hex digests; the tool reports both when capitalisation alone cannot disambiguate.
No. Everything runs locally in your browser; nothing leaves your device.
No. It only identifies likely algorithms; it does not attempt brute-force or rainbow-table attacks.
Yes, common prefixed variants such as bcrypt or Argon2 are recognised when their headers are intact.
The interface is optimised for a few thousand lines; extremely large files may slow rendering but will not crash.