MD5
Legacy MD5 hash - deprecated for security, use SHA-256 or BLAKE2 instead for any security needs
Short explanation
MD5 is a legacy 128-bit hash function. It is fast and still appears in older systems, but it is broken for cryptographic security because practical collision attacks exist.
Example input
legacy-file.binTypical use
Use MD5 only when you need compatibility with an existing checksum, API, database column, or old file manifest.
When to use it
- Legacy compatibility where another system already requires MD5.
- Non-security file identification in trusted internal workflows.
- Quick comparison against an existing MD5 checksum from old tooling.
When not to use it
- Digital signatures, certificates, package verification, or tamper-resistant integrity.
- Password storage or password reset tokens.
- Any new security design. Prefer SHA-256, SHA-3, BLAKE2, or BLAKE3.
FAQ
Is MD5 secure?
No. MD5 is cryptographically broken and should not be used for security-sensitive integrity or signatures.
Why do people still use MD5?
Mostly compatibility. Many older systems, databases, and manifests still store MD5 checksums.
What should I use instead of MD5?
Use SHA-256 for broad compatibility, SHA-3 for a newer standard, or BLAKE3 for high-performance modern hashing.
Legacy MD5 hash - deprecated for security, use SHA-256 or BLAKE2 instead for any security needs
SHA-1
Deprecated SHA-1 hash - cryptographically broken, use SHA-256 or SHA-3 for secure applications
RIPEMD-160
European RIPEMD-160 cryptographic hash - alternative to SHA-1 for digital signatures
Keccak-224
Original Keccak-224 hash - foundation of SHA-3 standard for Ethereum and blockchain
Keccak-256
Keccak-256 hash algorithm used in Ethereum blockchain and cryptocurrency security
Keccak-384
High-security Keccak-384 cryptographic hash for advanced digital security applications
Keccak-512
Maximum-security Keccak-512 hash for large-scale data integrity and encryption