Paste a hash into this hash type identifier tool and it lists the candidate algorithms for that unknown hash in seconds, so you can identify it without guessing. It is a free online hash identifier that reads the length, characters and leading symbols of a hash fingerprint, whether it came from an MD5 dump or a file of stored passwords.
Identify a Hash Online with the Hash Type Identifier
To identify a hash, copy the hash value without spaces or quotes, paste it into the box and read the ranked matches. The hash identifier can detect and analyze the string in your browser, so the value never has to leave the page. Try 7fbb9e3a5da886575819073614773b75, a hash of the made-up phrase "harbor-lantern-42":
- Paste the 32 characters and run the check.
- See MD5 listed first, with close alternatives behind it.
- Confirm with the system that stored it, because the match is a candidate, not proof.
Check an Unknown Hash Privately
Security teams often handle hashes from live systems, so privacy matters. Matching runs locally against a list of known patterns, and because a hash is a one-way digest, pasting it exposes no readable secret. Treat the output with confidence only after cross-checking it.
Fix a Hash Identifier Showing No Matches
No result usually means the value is damaged or custom. Remove trailing spaces, check that the hash format is intact, and test whether it is a salted construction from an application database. Strings that mix several families, such as a salt glued to a hash, will not match a single pattern.
How Hash Identification Works
Hash identification works by comparing structure, not by analyzing content. A hash function is deterministic: the same input always gives the same fixed-length cryptographic digest. A hash analyzer or hash detector therefore reads structural clues and matches the signature to an algorithm family. Because several algorithms share a format, the answer is probabilistic.
Hash Length and Character Set Clues
A hash length and character set narrow the field quickly. Hexadecimal output uses 4 bits per character, so \(\text{characters} = \text{bits} \div 4\). A 32-character string holds 128 bits, which fits MD5, MD4 and NTLM. A 40-character string is 160 bits: SHA-1 (also written SHA1) or RIPEMD-160. A 64-character value holds 256 bits: SHA-256 (SHA256) or SHA3-256. A 128-character string suggests SHA-512 (SHA512). A short 8-character value is usually a CRC32 checksum, not an authentication scheme, and the bit length alone never separates same-size hashes from encryption output.
Prefix and Salt Format Markers
A prefix is the strongest hint. The format markers $2y$ mean bcrypt, $argon2id$ means Argon2, and $1$ means MD5crypt, while $5$ and $6$ mark sha256crypt and sha512crypt. A dollar sign is a delimiter between the salt and the hash, so the salt sits inside the stored string. Base64 text, phpass values starting $P$, a MySQL hash with a leading asterisk, a WordPress password and a Linux shadow entry each have their own pattern. Argon2 follows the PHC format and records its cost settings, so you can read them directly. Each password hash style also hints at authentication age, since MD5 and SHA-1 are legacy algorithms today.
Reference Table of Hash Types and Lengths
Use this table to match a value you hold against the most common hash types and their cracking modes.
| Algorithm | Length or prefix | Mode |
|---|---|---|
| MD5 | 32 hex | 0 |
| MD4 | 32 hex | 900 |
| NTLM | 32 hex, same as MD5 | 1000 |
| LM | 32 hex, often uppercase | 3000 |
| SHA-1 | 40 hex | 100 |
| SHA-256 | 64 hex | 1400 |
| SHA3-256 | 64 hex, same as SHA-256 | 17400 |
| MD5crypt | $1$salt$hash | 500 |
| bcrypt | $2y$10$, 60 characters | 3200 |
A dictionary attack is the usual next step, once you know the family.
Why MD5 and NTLM Look Identical
MD5 and NTLM both output 128 bits, so the two strings look the same. The tool ranks MD5 first because it is more common in web databases, while an NTLM value more likely comes from Windows. That is a real cryptography limit and a vulnerability for anyone assuming one match is final: use the source system as the tiebreaker. A 7fbb9e… MD5 value and its Windows twin are indistinguishable by shape, and the same password gives different digests under each.
Auditing a Legacy Users Table with an Online Hash Analyzer
I'm migrating a small forum whose old PHP login code nobody remembers, and the first question is how those passwords were stored. I copy one value from the users column, 870649b871326883bd8b5e102eea88f51af18a7e, and paste it into the hash identifier.
It reports 40 hexadecimal characters, so \(40 \times 4 = 160\) bits. That rules out MD5 and fits SHA-1 first, with RIPEMD-160 as the same-length alternative. No dollar signs means no embedded salt, so every account sharing a password also shares a hash. I cross-check by hashing a test password, "ledger-owl-318", with SHA-1 myself, and the output matches the pasted value exactly.
The result: unsalted SHA-1, which is a legacy scheme. OWASP's password storage guidance recommends Argon2id, and NIST has deprecated SHA-1 for digital signatures, so the decision is to rehash each account at its next login with bcrypt or Argon2id rather than force a reset for everyone.
A quick sensitivity rerun shows why the length matters. If the same cell had held 64 characters, the field would be 256 bits and I would be looking at SHA-256 or SHA3-256, a very different migration story. If it had held 32, the choice would split between MD5 and NTLM, and I would have to read the application code to decide.
The caveat I would not skip: a match is a format guess. Some older systems wrap a digest twice, for example MD5 of an MD5, and the output is still 32 characters, so the tool cannot see it. The number to watch is the match rate on a sample, not one row. I test five values; all five agree, so I trust the family and move on to the hashcat mode only if an audit needs it.
Hashcat and John the Ripper Modes for Each Hash Identifier Result
Once you identify hash candidates, choose the matching hashcat mode or John the Ripper format, as in the table above. A hash cracker needs the exact mode to recover plaintext, and penetration testers use it during an audit of an authorized dump. Picking the wrong mode only wastes time, so confirm the algorithm before you start.
Kali Linux Command Output
The Kali Linux command line tool does the same job and prints a "Possible" list and a "Least Possible" list. It is a quick way to identify hash types offline, but it shows a long tail of weak guesses, so the entry at the top of the first list is the one to test.
Can a Hash Analyzer Decrypt Hashes?
No. A hash type analyzer only classifies a value, and it stops there; it does not encrypt or decrypt anything and cannot restore a decoded password. Hashes are not encryption.
Why a Hash Cannot Be Reversed
Hashing destroys the original input, so a long hexadecimal string never converts back into text. People instead guess inputs and compare the results, using rainbow tables or a hash generator to test candidates quickly. A strong salt and a slow algorithm make that guessing expensive, which is why modern systems store passwords that way.
Who Uses a Hash Detector in Security Work
Incident response teams classify indicators from malware cases, threat intelligence analysts normalize feeds before querying them, and developers inspect old login code to see which scheme stored each record. Auditors also use the result to rank accounts by risk and report it plainly to owners, since a weak match points to the records that need attention first. In each case the identifier answers one question, which algorithm family produced this value, before any other step begins.
Moving from Legacy Algorithms to Argon2id
If the match is MD5 or SHA1, plan a migration to bcrypt or Argon2id, which add salt and tunable cost.
Frequently Asked Questions
- Can this tool tell me the exact algorithm with certainty?
- Not always -- many algorithms produce identically-sized output (MD5 and NTLM are both 32 hex characters; SHA-256 and SHA3-256 are both 64), so length and character set alone can't always distinguish them. When a hash has a clear format prefix (like bcrypt's $2b$ or Argon2's $argon2id$), identification is high-confidence; plain hex digests are narrowed to a shortlist of possibilities instead.
- Why does a 32-character hex string match both MD5 and NTLM?
- Both algorithms produce a 128-bit (16-byte) digest, which is always 32 hex characters regardless of algorithm. There's no structural difference in the output itself -- you'd need to know the context it came from (a Windows SAM database vs. a general-purpose hash) to tell them apart.
- What does the $2b$ prefix in a bcrypt hash mean?
- It identifies the bcrypt variant (2a, 2b, 2x, and 2y all exist for historical reasons around a padding bug fix), immediately followed by a two-digit cost factor and then the salt and hash digest together, Base64-encoded in bcrypt's own alphabet. This structure is unique enough that bcrypt hashes are always identified with high confidence.
- Is my hash sent anywhere to be identified?
- No. Identification runs entirely in your browser using pattern matching against known formats -- nothing is transmitted, logged, or stored.
- What should I do once I know the hash type?
- If it's a fast, unsalted hash like plain MD5 or SHA-1 used for passwords, that's a red flag -- those algorithms are unsuitable for password storage and should be migrated to bcrypt, scrypt, or Argon2. If you need to verify a password against a bcrypt hash specifically, use the Bcrypt Hash Verifier.