AnyHash
Skip to content

RIPEMD-160 Hash Generator

Compute a 160-bit RIPEMD-160 digest of any text or file instantly — entirely in your browser. Your input never leaves your device.

Or drop a file to hash its full contents

Drag & drop · up to 64 MB

RIPEMD-160 hash

 

Type or paste input to see its hash instantly.

Code snippets

Generate RIPEMD-160 in your language

import { createHash } from "node:crypto";

console.log(createHash("ripemd160").update("hello world").digest("hex"));

RIPEMD-160 ships with OpenSSL, Node.js, and Python — the digest is always 40 lowercase hex characters.

What RIPEMD-160 is

RIPEMD-160 is a 160-bit hash from the European RIPE project, published in 1996 by Hans Dobbertin, Antoon Bosselaers, and Bart Preneel. It was designed as an independent alternative to the NSA-designed SHA family — a true advantage in the patent-heavy 1990s.

Its construction runs two parallel 80-step lines with different message orderings and merges their states at the end — a design that has resisted collision attacks far better than its MD4 lineage suggests.

What it powers

  • Bitcoin addresses: SHA-256 the public key, then RIPEMD-160 (base58check)
  • Legacy PGP fingerprints
  • OpenSSL / Node.js compatibility hashes
  • Older IPsec and PGP contexts

For new security work, reach for SHA-256 or BLAKE3 instead.

Algorithm guide

RIPEMD-160 explained

What is RIPEMD-160?

RIPEMD-160 is a 160-bit cryptographic hash function from the European RIPE project. It produces a fixed 20-byte digest — forty hexadecimal characters — and was one of the first credible non-American hash designs, published to give European standards bodies an alternative to the NSA-authored SHA family.

The two-line construction

RIPEMD-160 processes 512-bit blocks with ten rounds of 16 steps — five rounds in a left line and five in a right line that apply the same boolean functions but traverse the message words in different orders. The two 160-bit states are then combined by addition along with the previous chaining value. This parallel, symmetric design is the main reason collisions have stayed out of reach for the full 80 steps.

Role in cryptocurrency

RIPEMD-160's best-known job is Bitcoin address derivation. A compressed public key is hashed with SHA-256, then the digest is hashed again with RIPEMD-160 to yield the 160-bit hash — an intentional double-hash that both shortens the address and sidesteps any hypothetical weakness in a single hash. Legacy and P2SH addresses are then base58check-encoded (with a version byte and checksum), which is how a 160-bit hash becomes the familiar 27–34 character address.

Security status

More than 25 years of analysis have produced no practical collision attack on the full RIPEMD-160, and it appeared to gain from the same Hamming-weight arguments used against SHA-1. However, at 160 bits its collision resistance is only 80 bits against modern brute-force bounds, and it was not formally standardized (no FIPS part). It remains acceptable where a protocol — such as Bitcoin — already locks it in; it is not first choice for new designs.

How this tool works

RIPEMD-160 is not exposed by the Web Crypto API, so this page uses the hash-wasm WebAssembly build. The WASM module loads once and is reused for every digest via init(), making repeated hashing effectively instant. Input is decoded locally (UTF-8, hex, or Base64), hashed on-device, and never leaves your machine.

Worked examples you can verify right now

InputRIPEMD-160 digest
(empty string)9c1185a5c5e9fc54612808977ee8f548b2258d31
hello world98c615784ccb5fe5936fbc0cbe9dfdb408d92f0f
The quick brown fox jumps over the lazy dog37f332f68db77bd9d7edd4969571ad671cf9dd3b

Re-type any row above (matching the UTF-8 bytes exactly, including the period in the fox sentence) and this tool returns precisely these 40-character digests.

Frequently asked questions

Is RIPEMD-160 secure?

No practical full-round collision has been demonstrated, but its 160-bit output is small by modern standards and it offers nothing SHA-256 does not. It survives inside Bitcoin address derivation and legacy systems; it is not recommended for new work.

Where is RIPEMD-160 used today?

Most famously in Bitcoin: legacy and P2SH addresses are a hash of a public key (SHA-256 followed by RIPEMD-160). It also appears in legacy PGP fingerprints and some older protocols.

How does RIPEMD-160 differ from MD5 and SHA-1?

All three produce 160-bit-class Merkle–Damgård hashes from the 1990s, but RIPEMD-160 uses two parallel lines of computation (a 'left' and 'right' branch) that are combined at the end — a design that aged better than MD5 and independently of the NSA's SHA-1.

Other hash tools