Automatically detect and identify the type of a hash string (MD5, SHA-1, SHA-256, bcrypt, etc.) by analyzing its format.
Hash Identifier classifies a pasted hash by examining visible characteristics such as length, character set, and recognizable prefixes. It can distinguish self-describing password-hash formats such as bcrypt from common hexadecimal digest shapes associated with MD5, SHA-1, and SHA-256. The result is a format identification, not proof of which program or algorithm produced the value. This matters most for bare hexadecimal strings, because unrelated hash algorithms can produce text with exactly the same length and alphabet.
A concrete input and expected output from the current implementation.
Input
$2b$12$LQv3c1yqBWVHxkd0LHAkCOYz6TtxG6sE3YkZ/7vC3qYpYwJ5LhZ0K
Expected output
bcrypt
This is a 60-character bcrypt string. The $2b$ marker identifies the bcrypt variant, 12 is its cost field, and the remaining 53 characters contain the encoded salt and checksum.
The identifier evaluates properties that remain visible after hashing. These include the total number of characters, whether the value is hexadecimal or uses another encoding alphabet, and whether it begins with a structured marker such as bcrypt's $2b$ prefix. A recognizable marker provides stronger evidence than length alone because the format carries information about itself.
Bare digests usually contain no algorithm name. For these values, identification depends on whether the text fits a familiar output shape. For example, an MD5 digest is commonly represented by 32 hexadecimal characters, while SHA-1 commonly uses 40. Those shapes are useful clues, but another algorithm or application-specific identifier can share the same representation.
No. The tool examines the representation of the hash, not its unknown input. A digest does not contain a label for the original text, and identifying its likely family does not reverse it. Verifying a suspected value requires hashing that candidate according to the identified format, including any recorded salt, cost, or other parameters.
Several algorithms emit the same number of bytes and are commonly written with the same character set. A bare 64-character hexadecimal string, for example, fits the usual SHA-256 representation but is not exclusive to SHA-256. Prefix-bearing formats such as bcrypt are less ambiguous, while untagged digests need provenance or application metadata for confirmation.
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.