Build a tamper-evident hash chain for digital evidence. Each file gets a timestamped hash linked to the previous entry.
Evidence Hash Chain Builder creates an ordered manifest for digital evidence. For each selected file, it records a cryptographic hash and timestamp, then links the entry to the one before it. The resulting chain can expose later changes to file contents, entry order, or recorded links when compared with the preserved original. Files are processed in the browser and are not uploaded. The important limitation is that a consistent chain does not prove who collected the evidence, when the underlying event occurred, or who controlled the files afterward.
Each entry identifies one file through its hash and records a timestamp and a link to the preceding entry. The first file starts the sequence because no earlier evidence entry exists. Later entries depend on the chain position before them, so processing the same files in a different order produces a different chain record.
The chain becomes useful when its original result is preserved for comparison. If file bytes or an earlier entry change, the recorded hash or following link will no longer agree with that baseline. A hash chain is not self-authenticating: someone who can replace both the evidence and the only saved chain record could construct a new, internally consistent chain.
No. It records an ordered relationship among file hashes and timestamps, which can support later integrity checks. A complete custody record also needs documented acquisition methods, responsible people, transfers, storage controls, access history, and preserved originals. Depending on the setting, signatures or independently trusted timestamps may also be required.
Preserve the complete chain result, the exact file order, and the evidence files under controlled storage. Keep an independently protected copy of the result, especially its final linked value. If the only chain record remains beside files that another person can replace, that person may be able to alter the files and build a new consistent record.
The 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.