Hash Format Identifier

Structured formats carry recognizable prefixes and fields. The identifier can parse common bcrypt and Argon2 strings, scrypt and PBKDF2 serializations, Unix crypt variants, LDAP wrappers, and selected application or database formats. It reports only parameters encoded in the value; it does not score the password or validate the hash.

A 32-character hex value is 128 bits and could be MD5, MD4, NTLM, or arbitrary bytes. A 64-character hex value is 256 bits and could fit SHA-256, SHA3-256, Keccak-256, BLAKE2s, a key, or another identifier. Length narrows the possibilities, but it does not identify the algorithm.

A strong result requires an explicit serialization marker and valid field shape. A possible result uses only the encoding and decoded length. Confirm the answer with the system that stored or transmitted the value before you select a verifier, migration path, or security policy.

The tool cannot recover the original password, prove that a raw value is a hash, determine an unmarked algorithm, or establish whether the parameters are appropriate for your application. Identification and verification are separate operations.

• String Format Identifier - Start here when the value may not be a hash at all.
• Verify Bcrypt - Compare plaintext with a confirmed bcrypt hash.
• Verify Argon2id - Verify a confirmed Argon2id PHC string.
• File Checksum - Calculate SHA-256 for a local file and compare it with a published digest.
• SHA-256 Hash Tool - Generate a known SHA-256 digest from text.
• SHA-256 vs MD5 vs bcrypt guide - Choose a workflow based on the job, not the output shape.