MD5
BrokenLegacy checksums only; collisions make it unsuitable for security.
- Output length
- 128 bits
- Typical use
- Integrity
Reference
Algorithm Library
A concise security reference. Security status reflects current cryptographic practice—legacy algorithms remain available only for compatibility and checksum workflows.
SHA-1
BrokenDeprecated for signatures; use SHA-256 or SHA-3.
- Output length
- 160 bits
- Typical use
- Integrity
SHA-224
AcceptableTruncated SHA-2 variant for constrained protocols.
- Output length
- 224 bits
- Typical use
- Integrity
SHA-256
RecommendedWidely supported integrity and signature building block.
- Output length
- 256 bits
- Typical use
- Integrity
SHA-384
RecommendedSHA-2 variant commonly paired with P-384.
- Output length
- 384 bits
- Typical use
- Integrity
SHA-512
RecommendedHigh-throughput SHA-2 digest on 64-bit systems.
- Output length
- 512 bits
- Typical use
- Integrity
SHA-3 family
RecommendedKeccak-based alternative with a distinct construction.
- Output length
- 224–512 bits
- Typical use
- Integrity
RIPEMD-160
LegacyUsed by older cryptocurrency address formats.
- Output length
- 160 bits
- Typical use
- Integrity
bcrypt
Password hashingSlow password hash with a configurable work factor.
- Output length
- Adaptive
- Typical use
- Password storage
Argon2id
PreferredMemory-hard password hashing; OWASP’s preferred modern choice.
- Output length
- Adaptive
- Typical use
- Password storage
scrypt
RecommendedMemory-hard KDF designed to make hardware attacks costly.
- Output length
- Adaptive
- Typical use
- Integrity
PBKDF2
CompatibleNIST-approved password KDF for broad compatibility.
- Output length
- Adaptive
- Typical use
- Password storage