HesapHanem

Hash Identifier

Paste a hash to detect its likely algorithm.

How it is calculated

The tool never decodes or cracks anything; it only looks at the text you paste, after trimming spaces. If it starts with $2a$, $2b$ or $2y$ followed by two digits and another $, it reports bcrypt. Otherwise, if every character is hexadecimal (0-9, a-f, either case), it matches the length: 32 characters MD5, NTLM or MD4; 40 SHA-1; 56 SHA-224 or SHA3-224; 64 SHA-256 or SHA3-256; 96 SHA-384 or SHA3-384; 128 SHA-512, SHA3-512 or Whirlpool. Any other length or a non-hex character gives Unknown hash type with the length and charset. Several algorithms share one length, so the result is a list of candidates, not proof.

Worked example

You find the 40-character string 5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8 in a database dump. It is all hexadecimal, and 40 characters matches one algorithm in the table. The tool answers Likely: SHA-1
Length: 40 chars with the charset hex (0-9a-f). A 32-character hex string would have returned MD5, NTLM, MD4 instead, because those share one length. A string with a 0x prefix is 42 characters and not pure hex, so it is reported as unknown.

Try this example →

Common mistakes

  • Treating the answer as certain: a 32-character hash may be MD5, NTLM or MD4, and a 64-character one SHA-256 or SHA3-256, so context is needed to choose.
  • Pasting a hash with a prefix or extra text such as 0x, a username, a colon or a salt: only a clean hex string or a bcrypt string is recognised, and anything else comes back as unknown.
  • Expecting salted formats such as $1$ or $6$ crypt strings, or Base64-encoded digests, to be named: only bcrypt is detected by prefix, so these return unknown.
  • Pasting an HMAC or a truncated hash and trusting the match: a digest cut to 32 characters looks exactly like MD5, because only length and charset are checked.

About this calculator

Cryptographic and password hashes carry no explicit label saying which algorithm produced them, but their length and character set are usually a strong tell: an MD5 digest is always 32 hex characters (128 bits), SHA-1 is 40 hex characters (160 bits), SHA-256 is 64 hex characters (256 bits), and password-hashing schemes like bcrypt encode their own prefix, such as $2a$, $2b$ or $2y$, followed by a work-factor and a base64-style salt-plus-hash string rather than plain hex.

Penetration testers and digital forensics investigators use this kind of pattern-matching — the same logic tools like hashcat and John the Ripper apply when auto-detecting a hash mode — as the first step before attempting to crack or verify a hash, since picking the wrong algorithm makes every subsequent attempt fail no matter how strong the cracking dictionary is.

Was this helpful?

You can pick up to 3 reactions.

Comments (1)

  • Editorial team

    Length alone cannot separate algorithms that share it, so context does the rest. A 32-character hex string from a web application's user table is usually MD5, while one pulled from a Windows credential dump is more likely NTLM. Note where the string came from before you choose. Which hash formats should the tool learn to recognise next?

Popular calculators

Loan Calculator

Monthly payment, total interest and full amortization schedule.

Percentage Calculator

Percent change, percent of, and ratio calculations.

Discount Calculator

Calculate final price, savings, and discount amount.

BMI Calculator

Body mass index from height and weight (metric or imperial).

Age Calculator

Compute your exact age in years, months and days from a birth date.

Compound Interest Calculator

Calculate the final amount and interest earned with compounding.

All Calculators