RIPEMD-160 Hash Generator
Calculate RIPEMD-160 hashes online. Used in Bitcoin address generation (SHA-256 → RIPEMD-160 = HASH160). Supports HMAC-RIPEMD160, UTF-8, Hex, and Base64 input encodings.
Share Link
Related Hash Tools
Frequently Asked Questions
What is RIPEMD-160?
How is RIPEMD-160 used in Bitcoin?
Is RIPEMD-160 vulnerable?
RIPEMD-160 vs SHA-1 — both are 160 bits?
About RIPEMD-160 Hash Generator
RIPEMD-160 (RACE Integrity Primitives Evaluation Message Digest, 160-bit) was published in 1996 by a team at KU Leuven as a strengthened replacement for RIPEMD-128 and a European alternative to SHA-1. It processes input in 512-bit blocks through two parallel pipelines of five rounds each, producing a 160-bit (20-byte) digest shown as a 40-character hexadecimal string.
RIPEMD-160 in Bitcoin Address Generation
RIPEMD-160 plays a critical role in Bitcoin's security model. Every P2PKH (Legacy) and P2WPKH (SegWit) Bitcoin address derives from HASH160 = RIPEMD160(SHA256(publicKey)). The 20-byte RIPEMD-160 output serves as the "public key hash" that appears in transaction scripts. By using two independent hash functions, Bitcoin address derivation is resistant to vulnerabilities in either algorithm individually.
RIPEMD-160 in PGP and OpenPGP
RIPEMD-160 was previously used in PGP for key fingerprinting and is listed in RFC 4880 (OpenPGP) as an optional algorithm. While SHA-256 is now preferred for new implementations, legacy PGP keys using RIPEMD-160 fingerprints are still widely used.
RIPEMD vs SHA Family
Unlike SHA-1 and SHA-2 (designed by the NSA), RIPEMD was designed by a European academic consortium, making it attractive for implementations seeking algorithm diversity. While no SHA backdoor has ever been demonstrated, using both SHA-256 and RIPEMD-160 together (as Bitcoin does) provides protection against vulnerabilities in either family.
HMAC-RIPEMD-160
HMAC-RIPEMD-160 can be used for message authentication with a shared secret key. Enable the HMAC option in Settings and enter your key. This is rarely seen in modern protocols but may be needed for legacy system compatibility.