Paste any hash and automatically identify its type (MD5, SHA-1, SHA-256, bcrypt, Argon2, etc.) by format and length.
Hash Type Identifier examines a pasted hash and reports the family suggested by its length, character set, prefixes, and separators. It can recognize bare hexadecimal digests such as MD5, SHA-1, and SHA-256, as well as structured password hashes such as bcrypt and Argon2. The important caveat is that appearance is not proof of origin. Several algorithms can produce identically shaped strings, so an unprefixed digest may have more than one plausible interpretation. Inspection occurs entirely in the browser, which is relevant when the value came from credential data.
A concrete input and expected output from the current implementation.
Input
$2a$10$N9qo8uLOickgx2ZMRZoMyeIjZAgcfl7p92ldGxad68LJZdL17lhWy
Expected output
bcrypt
The $2a$ family marker and the remainder of the structured record match bcrypt's encoded form. This classification comes from the format, not from recovering or testing the password.
For an unprefixed value, the detector compares the exact character count and character set with known digest forms. A 32-character hexadecimal value fits the common MD5 presentation, 40 hexadecimal characters fit SHA-1, and 64 fit SHA-256. These checks classify the representation; they do not establish which program created it.
Password-hash encodings can expose stronger clues than raw hexadecimal digests. A bcrypt record such as the example begins with a $2a$ family marker and contains delimited settings plus encoded data. Argon2 encodings similarly name variants such as $argon2id$. Those visible markers allow a more specific identification than digest length alone.
No. It only classifies the visible representation. It does not reverse the hash, search candidate inputs, or verify a guessed password. Even a confident bcrypt or Argon2 identification says what encoding the string resembles, not what secret produced it or whether recovery is practical.
Many formats carry no algorithm name. They are simply hexadecimal or encoded bytes of a particular length, and unrelated algorithms can share that shape. Prefix-bearing formats such as bcrypt or Argon2 are usually easier to distinguish. For an unlabeled digest, context from the producing system may be needed for a definitive answer.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.