SHA-1
Deprecated SHA-1 hash - cryptographically broken, use SHA-256 or SHA-3 for secure applications
Short explanation
SHA-1 is a legacy 160-bit cryptographic hash that is now considered broken for collision resistance. It should be treated as a compatibility tool, not a safe choice for new security work.
Example input
old-git-object-or-certificateTypical use
Use SHA-1 only when checking or reproducing hashes from older protocols, archives, or systems that still expose SHA-1 values.
When to use it
- Compatibility with existing SHA-1 identifiers or legacy manifests.
- Historical data migration where SHA-1 values already exist.
- Non-adversarial lookup workflows where security is not required.
When not to use it
- New digital signatures, certificates, or software supply-chain verification.
- Any workflow where an attacker could craft colliding inputs.
- Password hashing or token generation.
FAQ
Is SHA-1 broken?
Yes. Practical collision attacks exist, so SHA-1 should not be used for new security-sensitive designs.
Is SHA-1 the same as SHA-256?
No. SHA-1 outputs 160 bits and is deprecated. SHA-256 is part of SHA-2, outputs 256 bits, and remains widely trusted.
Can I use SHA-1 for file checksums?
Only for legacy compatibility or trusted internal checks. For public integrity checks, use SHA-256 or stronger.
Deprecated SHA-1 hash - cryptographically broken, use SHA-256 or SHA-3 for secure applications
MD5
Legacy MD5 hash - deprecated for security, use SHA-256 or BLAKE2 instead for any security needs
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