RIPEMD-160 Hash Calculator

Calculate the RIPEMD-160 hash of any text and get the 40-character hexadecimal digest, the European-designed hash function best known today for its role inside Bitcoin address generation. A free online tool from Staaarter, right in your browser.

Runs locallyUpdated 2026-07-22

Overview

Introduction

RIPEMD-160 is a 1990s European hash function that never became a mainstream general-purpose default, but survives today embedded in one very high-stakes place: Bitcoin address generation.

This tool computes RIPEMD-160's 160-bit digest of any text you provide, entirely in your browser, for reproducing part of an address derivation, checking legacy checksums, or matching known test vectors.

What Is RIPEMD-160 Hash Calculator?

RIPEMD-160 is a cryptographic hash function developed by the EU-funded RIPE project and published in 1996, producing a 160-bit digest shown as 40 hexadecimal characters.

It uses a distinctive dual-line design: two separate, parallel sequences of compression operate on the same input with different constants and functions, and their results are combined at the end, giving it more structural redundancy than single-line designs like MD5 or SHA-1.

How RIPEMD-160 Hash Calculator Works

Input text is UTF-8 encoded, padded to a multiple of 512 bits per the Merkle–Damgård construction, and processed in 64-byte blocks through two parallel lines of 80 rounds each, using different round functions and constants per line.

The two lines' final states are combined via modular addition into five 32-bit words, forming the 160-bit digest that gets hex-encoded into the 40-character output.

When To Use RIPEMD-160 Hash Calculator

Use RIPEMD-160 when reproducing or verifying part of a Bitcoin (or similar cryptocurrency) address derivation, which chains SHA-256 and RIPEMD-160 together, or when matching a legacy system that specifically requires it.

For new general-purpose hashing needs without that specific requirement, SHA-256 or BLAKE3 are more common, better-supported defaults.

Features

Advantages

  • No known practical collision attack, unlike MD5, SHA-1, or the shorter RIPEMD variants.
  • Structurally distinct dual-line design offers different failure characteristics than Merkle–Damgård-only hashes.
  • Still actively relevant via its embedded role in Bitcoin and similar cryptocurrency address formats.

Limitations

  • Shorter 160-bit output than modern defaults like SHA-256, giving a smaller security margin against brute-force search.
  • Far less commonly implemented and battle-tested outside of its specific cryptocurrency niche compared to SHA-2 or SHA-3.
  • Not the right choice for new general-purpose designs without a specific compatibility requirement.

Examples

Hashing a short greeting

Input

Hello, world!

Output

58262d1fbdbe4530d8865d3518c6d6e41002610f

13 bytes of UTF-8 text produce the standard 40-character RIPEMD-160 hex digest.

Hashing the classic pangram

Input

The quick brown fox jumps over the lazy dog

Output

37f332f68db77bd9d7edd4969571ad671cf9dd3b

A widely published RIPEMD-160 test vector, useful for confirming any implementation matches the standard.

Best Practices & Notes

Best Practices

  • Use RIPEMD-160 specifically to match Bitcoin-style address derivation or another system that already requires it, not as a general-purpose default.
  • Remember that a Bitcoin address hashes the SHA-256 digest of a public key through RIPEMD-160, not the raw key directly, if you're trying to reproduce one by hand.
  • For new designs without a legacy or cryptocurrency compatibility need, prefer SHA-256 or BLAKE3.

Developer Notes

This tool uses @noble/hashes' audited RIPEMD-160 implementation, computing the digest synchronously in the browser from the UTF-8 byte encoding of your input via TextEncoder.

RIPEMD-160 Hash Calculator Use Cases

  • Reproducing part of a Bitcoin or similar cryptocurrency address derivation by hand
  • Verifying a legacy checksum published using RIPEMD-160
  • Reproducing a known RIPEMD-160 test vector while debugging another implementation
  • Working with older PGP or cryptographic tooling that offered RIPEMD-160 as a digest option

Common Mistakes

  • Hashing a raw public key with RIPEMD-160 directly instead of first hashing it with SHA-256, when trying to reproduce a Bitcoin address.
  • Assuming RIPEMD-160 is broken like MD5 or SHA-1 just because it's from the same era; it has held up better than either.
  • Choosing RIPEMD-160 for a brand-new design without a specific compatibility reason.

Tips

  • Reproducing a Bitcoin address? You'll need this tool chained after a SHA-256 hash of the public key, not run on the raw key.
  • For a modern general-purpose alternative with a similar output length, SHA-1 is comparably sized but RIPEMD-160 has the better collision-resistance track record of the two.

References

Frequently Asked Questions