File Checksum Utility

File and data integrity are critical to information management in both the enterprise, and at home. This utility allows you to calculate a file's checksum "fingerprint" using the top 3 most popular, standard, and reliable algorithms developed by the field of computer science.

CRC32 "basic level" checking

This algorithm is the most popular and commonly used checksum in use today for ensuring successful file and data replication.

The Cyclic Redundancy Check (CRC-32) algorithm produces an 8 character alpha-numeric (hexadecimal) 32-bit check sum "fingerprint" of a specified input file. It uses the standard 32-bit algorithm as used in many popular applications including PKZip, Ethernet and FDDI for file checking as implemented by Oracle in java.util.zip.CRC32.

MD5 "secure level" checking

The MD5 digest is an ideal way to verify data integrity when doing large file transfers. This algorithm is frequently used to check .ISO CD images for download/burn accuracy.

The RSA MD5 algorithm produces a 32 character alpha-numeric (hexadecimal), 128-bit (16 octet) check-sum "fingerprint" or "message digest" of a specified input file per RFC 1321 specifications as implemented by Oracle in java.security.MessageDigest. The MD 5 digest is much more reliable than CRC-32. It is believed to be computationally infeasible to be able to produce two messages having the same message digest, or to produce any message having been given a pre-specified message digest. RSA-MD5 is thus believed to be collision-proof. The MD-5 algorithm is intended for digital signature applications, where a large file must be "compressed" in a secure manner before being encrypted with a private "secret" key under a public-key cryptosystem such as RSA.

SHA-1 "premium level" checking

SHA1 is the highest level of data verification available, for critical or sensitive information in scientific, government, or enterprise-level data warehousing environments.

The "US Secure Hash Algorithm" (SHA-1) produces a 40 character, 160-bit alpha-numeric (hexadecimal) message digest (check sum) fingerprint as specified in RFC 3174 by The Internet Society, and as implemented by Oracle in java.security.MessageDigest. SHA1 is called secure because it is computationally infeasible to find a message which corresponds to a given message digest, or to find two different messages which produce the same message digest. Any change to a message in transit will, with very high probability, result in a different message digest, and the signature will fail to verify. Leverage our technology to detect and eliminate problems!