RIPEMD-160 Generator — Hash Text & Files Online
Generate RIPEMD-160 cryptographic hashes instantly in your browser: paste text, drop a file, or hash a whole list at once. Hex & Base64 output, a verify box, the official test vectors with a live self-test, and a HASH160 (SHA-256 → RIPEMD-160) demo for Bitcoin address derivation. Nothing is ever uploaded to a server.
Generate RIPEMD-160 Hash
RIPEMD-160 is not part of the Web Crypto API, so this tool ships a hand-written JavaScript implementation of the official specification — validated against the spec test vectors and three independent reference implementations.
Hashed locally in 4 MB chunks — never uploaded
Batch Mode — Hash Multiple Inputs
One input per line. Each line is hashed independently as UTF-8 text — handy for checksums lists, test fixtures, or address batches.
Official RIPEMD-160 Test Vectors
The 8 test vectors published in the RIPEMD-160 specification. Load any of them into the generator above, or run the self-test to re-hash every vector through this page's live engine.
| Input | Expected RIPEMD-160 | Status |
|---|
HASH160 Demo — RIPEMD160(SHA256(x))
Bitcoin derives legacy addresses as RIPEMD160(SHA256(public key)). Enter any text to see both steps: SHA-256 runs via your browser's Web Crypto, then this tool's RIPEMD-160 engine compresses the 32-byte result to 20 bytes.
About RIPEMD-160
What is RIPEMD-160?
RIPEMD-160 — RACE Integrity Primitives Evaluation Message Digest — is a 160-bit cryptographic hash function published in 1996 by Hans Dobbertin, Antoon Bosselaers, and Bart Preneel as part of the European RIPE project. It maps arbitrary input to a fixed 20-byte fingerprint, conventionally written as 40 hexadecimal characters. The design is a Merkle–Damgård construction: the message is padded, split into 512-bit blocks, and each block updates five 32-bit chaining words through 80 rounds arranged in two parallel lines with different constants, rotations, and message orderings — deliberately unlike the SHA family, so a weakness in one design is unlikely to affect the other.
RIPEMD-160 vs MD5, SHA-1, SHA-256
| Algorithm | Digest | Hex chars | Collision resistance | Typical use today |
|---|---|---|---|---|
| RIPEMD-160 | 160-bit | 40 | No practical attack known | Bitcoin address derivation |
| MD5 | 128-bit | 32 | Broken (2004) | Legacy checksums only |
| SHA-1 | 160-bit | 40 | Broken (SHAttered, 2017) | Git (being phased out) |
| SHA-256 | 256-bit | 64 | Secure | General-purpose hashing |
Where is RIPEMD-160 actually used?
Its most prominent home is Bitcoin: legacy P2PKH addresses embed HASH160 = RIPEMD160(SHA256(public key)), and many derived cryptocurrencies reuse the construction. It also appears in some PGP key fingerprints and older X.509 certificate fingerprints. For new designs, SHA-256 or SHA-3 is the safer default — RIPEMD-160 survives on compatibility, not on margin.
Why a hand-written JavaScript implementation?
Browsers expose MD5 nowhere and SHA-1/SHA-2/SHA-3 through the Web Crypto API — but RIPEMD-160 is not in Web Crypto. This tool therefore carries a from-scratch implementation of the official specification. It was validated against the 8 official test vectors plus padding-boundary, all-byte-value, and million-character inputs, cross-checked with three independent reference implementations (OpenSSL, PHP, and pycryptodome — all agreeing), and the vectors panel above lets you re-verify the live engine yourself at any time.
Frequently Asked Questions
What is RIPEMD-160?
How do I generate a RIPEMD-160 hash of my text?
Can I hash a file with RIPEMD-160?
What does a RIPEMD-160 hash look like?
What are the official RIPEMD-160 test vectors?
Is RIPEMD-160 secure?
Why does Bitcoin use RIPEMD-160?
Is my data sent to a server when I use this tool?
Free tool by NRTechStudio