RIPEMD-160 Hash Generator

How to use this RIPEMD-160 hash generator

Enter any text, then select Generate hash. For example, entering abc returns its RIPEMD-160 digest.

Use Copy or Export to reuse the generated value. This tool processes text in your browser.

About RIPEMD-160

RIPEMD-160 creates a fixed 160-bit digest, written as 40 hexadecimal characters. It is a member of the RIPEMD hash-function family.

For new security-sensitive designs, choose an algorithm required by the relevant protocol or current security guidance.

What RIPEMD-160 produces

RIPEMD-160 maps any text to a fixed 160-bit digest shown here as 40 hexadecimal characters. The same UTF-8 text produces the same digest. A one-character change normally produces a very different value. Hashing is one-way transformation, not encryption, so no key exists that restores the original text.

How the calculation works

The browser encodes entered text and processes it in algorithm-sized blocks. Padding records the message boundary, then repeated compression steps update an internal state. The final state becomes the digest. Digest length stays fixed whether input is one character or many pages, so a digest is an identifier or integrity check rather than a compressed copy of the message.

Worked example

Enter abc. The complete RIPEMD-160 result is 8eb208f7e05d987a9b044a8e98c6b087f15a0bfc. This example uses the three lowercase ASCII characters with no spaces or line break. ABC, abc , and text ending with a newline are different byte sequences and therefore have different digests.

Assumptions, security, and limitations

RIPEMD-160 remains part of some established formats, but it is not in NIST's current approved SHA-2 or SHA-3 families. Use it only when a protocol explicitly requires it; prefer a current, reviewed algorithm for a new design.

A matching digest can help confirm that two byte sequences are identical, but it does not prove who created a file or message. An attacker who can replace content may also replace an untrusted checksum. Use a digital signature or keyed MAC when authenticity matters. This text tool does not hash uploaded files and does not interpret a hexadecimal digest as input bytes.

Calculation runs in this browser. Input is not submitted to Awesome Tools, but browser extensions, device monitoring, clipboard history, exported files, and shared-device access remain outside this page's control. Verify critical results with the exact algorithm and byte encoding required by your protocol.

Common mistakes

• Comparing text that differs by an invisible trailing newline, Unicode normalization, or character encoding
• Treating an unkeyed digest as proof of authenticity or using a fast general-purpose hash for password storage
• Choosing an algorithm because its output is longer without checking the protocol's required algorithm and security guidance

RIPEMD-160 FAQ

Can two inputs have the same result?

Yes in principle because unlimited inputs map to fixed-length output. Security depends on how hard it is to find useful collisions or preimages, not on collisions being mathematically impossible.

Why does another tool return a different value?

Check encoding, capitalization, spaces, line endings, algorithm name, and output format.

Authoritative sources and related tools

Read the algorithm authors' RIPEMD-160 specification and test vectors.

• SHA-256 Hash Generator
• SHA-512 Hash Generator
• HMAC-SHA-256 Hash Generator