Compute MD5, SHA-1, SHA-256, and SHA-512 cryptographic checksums instantly. Verify chain of custody, identify malware IOCs, and detect unauthorized alterations with mathematical certainty.
In physical criminal investigations, forensic scientists rely on biological fingerprints to confirm the identity of individuals. In digital forensics, cryptographic hashes serve as the mathematical fingerprints of digital evidence.
Whether examining hard drive images (E01/DD), suspicious Windows executables, network packet captures (PCAP), or confidential documents, the primary question in any court of law is: "Has this evidence been altered in any way since seizure?"
By computing a cryptographic hash immediately upon acquisition and recording it in the Chain of Custody manifest, examiners establish an immutable baseline. If even a single byte, bit, or whitespace character changes, the avalanche effect of algorithms like SHA-256 completely randomizes the resulting checksum.
| Algorithm | Digest Size | Status in Forensics | Primary Applications |
|---|---|---|---|
| MD5 | 128 bits (32 hex chars) | Deprecated for Crypto | Legacy deduplication, rapid NSRL known-file filtering. |
| SHA-1 | 160 bits (40 hex chars) | Collision Risk | Git commit hashes, legacy digital signature verification. |
| SHA-256 | 256 bits (64 hex chars) | Industry Standard | Incident response, malware IOC matching, court evidence. |
| SHA-512 | 512 bits (128 hex chars) | Military Grade | High-security government storage, long-term cryptographic archives. |
In 2004, cryptographic researchers demonstrated practical collision attacks against MD5, followed by the SHAttered demonstration against SHA-1 in 2017. A collision occurs when two different inputs produce the exact same digest.
However, there is a fundamental distinction between a collision attack and a pre-image attack:
H, it remains computationally infeasible for an adversary to forge a new meaningful file that matches H.malware.exe to notes.txt leaves the hash value completely identical.
window.crypto.subtle.digest() interface. When you drop a file onto our dropzone, the file can be read locally using a JavaScript FileReader and digested directly by your CPU. Your file data never traverses the internet, guaranteeing complete privacy and zero data leakage.