6 min read
2026-03-09
When downloading Linux distributions, drivers, or software, compare the SHA-256 of the downloaded file with the hash on the official website. This protects against malicious substitutions.
Compare hashes of build artifacts before and after deployment. Make sure the file that reached the server is exactly the one that passed testing.
During incident investigation, hashing captures file states as evidence. Changing even one byte results in a different hash.
Find duplicate files by matching hashes. This is more efficient than comparing by name or size.
When copying data between servers, compare hashes of source and copied files to confirm complete identity.
Quick check — CRC32 or MD5 (sufficient for corruption detection)
Security — SHA-256 (standard for cryptographic applications)
Maximum protection — SHA-512 (for critically sensitive data)
Calculate a checksum with the Checksum Calculator.
See also: URL Validator, Password Strength, JSON Data Generator