Hash Identifier
Paste a hash and this tells you what made it — useful when you inherit a digest and need to know whether it is SHA-256 or something already broken.
Detection is by length and alphabet, which is how these are told apart in practice. It cannot tell you how the input was produced.
How identification works
Hash algorithms are told apart by output length and alphabet, not by content. A 64-character lowercase hex string is SHA-256 or one of its cousins; a 32-character one is MD5.
Length alone is not proof. A 40-character string could be SHA-1 or RIPEMD-160, and a truncated SHA-256 looks identical to something else entirely — which is why the tool lists every candidate rather than pretending to a single answer.
Frequently asked questions
Is MD5 broken?
Yes, for collision resistance: practical collisions have been demonstrated. It is still fine for detecting accidental file corruption, which is what most MD5 checksums are for.
Is SHA-1 broken?
Yes. SHAttered (2017) produced a real collision, so SHA-1 must not sign anything.
Can this identify bcrypt or Argon2?
Yes — those carry a recognisable prefix, which is why they are listed alongside the fixed-length digests.
Why does a 64-character value match several algorithms?
Because they all produce the same shape. Only the application that produced the hash knows which one it used; check the code or the file that stored it.
Is the hash sent anywhere?
No. Matching happens in this page.