Hash Verifier Guide
Use this guide to identify likely digest algorithms from hex length, verify whether candidate text produces a known hash, and understand why hashes cannot be decrypted or cracked in the browser.
Overview
The Hash Verifier is the practical counterpart to the Hash Generator. Generation turns text into a digest; verification checks whether a candidate input reproduces a known digest or identifies which algorithm a hex string likely uses. Neither operation reverses a hash.
What verification can and cannot do
- Can do: Detect MD5, SHA-1, SHA-256, SHA-384, or SHA-512 from hex length and compare candidate text locally.
- Cannot do: Recover unknown plaintext from a hash, break password hashes with salts, or verify bcrypt/Argon2 using plain SHA logic.
- Best practice: Compare full digests over a trusted channel and standardize new integrity work on SHA-256 or stronger.
Digest Length Reference
| Algorithm | Hex length | Typical use |
|---|---|---|
| MD5 | 32 | Legacy checksum compatibility only. |
| SHA-1 | 40 | Deprecated for signatures; still seen in older artifacts. |
| SHA-256 | 64 | Current standard for integrity and signatures. |
| SHA-384 | 96 | SHA-2 family; common in TLS signatures. |
| SHA-512 | 128 | SHA-2 family; strong margin on 64-bit systems. |
Verification Workflow
Verify a published SHA-256 checksum
Paste the published digest, enter the exact file contents or string you hashed, and confirm a SHA-256 match in the browser.Identify an unknown digest
Paste only the hex value first. The tool reports the likely algorithm from digest length before you test any candidate text.Recommended Remediation Flow
- Compare full values Never rely on prefix matches for security decisions; compare the entire digest.
- Use the matching algorithm A SHA-256 file will not match an MD5 or SHA-1 computation of the same bytes.
- Separate password hashing from digests Password storage requires salted KDFs such as bcrypt or Argon2, not plain SHA verification.
Troubleshooting Common Issues
Candidate text does not match
Verification fails when the algorithm, encoding, or input bytes differ.
- Confirm trailing newlines and file encoding.
- Check whether the published value uses a different algorithm.
- Password hashes with salts will not match plain SHA output.
Validation Checklist
Post-fix validation
- Identify the digest format before testing candidates.
- Compare full digests, not prefixes.
- Use SHA-256 or stronger for new integrity workflows.
FAQ
Is this the opposite of the Hash Generator?
It is the verification counterpart, not a decryption tool.
- Generation creates a digest from text.
- Verification checks whether known text reproduces a digest.
- Unknown plaintext cannot be recovered from the hash alone.