🔐 RIPEMD Hash Generator

🔐 RIPEMD Algorithms

🎨 Output Format

📝 Input Text

{{ inputText.length }} characters

📊 RIPEMD Hash Results

{{ hashes.ripemd128 }}
{{ hashes.ripemd160 }}
{{ hashes.ripemd256 }}
{{ hashes.ripemd320 }}

ℹ️ Hash Information

Bitcoin Address: RIPEMD-160 is used in Bitcoin public key hashing
Parallel Design: RIPEMD-256/320 use parallel computation for speed
European Standard: RIPEMD is an open European alternative to NSA hash functions

📊 RIPEMD Hash Results

Select algorithms and enter text to generate RIPEMD hashes...

Generating hashes...
⚠️ {{ error }}

ℹ️ About RIPEMD Hash Generation

RIPEMD (RACE Integrity Primitives Evaluation Message Digest) is a family of message digest algorithms developed by Hans Dobbertin, Antoon Bosselaers, and Bart Preneel as a strengthened European alternative to the MD4/MD5 design line. The original RIPEMD-160 specification page, the FSE paper RIPEMD-160: A Strengthened Version of RIPEMD, and ISO/IEC 10118-3 document the dedicated hash-function family and its published test vectors.

Use this RIPEMD hash generator when you need deterministic RIPEMD-128, RIPEMD-160, RIPEMD-256, or RIPEMD-320 digests for compatibility checks, historical protocol analysis, blockchain tooling, test fixtures, or comparing hexadecimal, Base64, and Base64URL encodings of the same digest. For example, the RIPEMD-160 digest of an empty byte string is 9c1185a5c5e9fc54612808977ee8f548b2258d31. Bitcoin-related workflows often use HASH160, which means SHA-256 followed by RIPEMD-160; the Bitcoin developer reference describes OP_HASH160 as that SHA-256 plus RIPEMD-160 construction.

Common use cases:

  • Generate RIPEMD-160 hashes for Bitcoin address derivation experiments, wallet education, and HASH160 test data.
  • Verify legacy RIPEMD digests from older archives, certificate systems, or interoperability test suites.
  • Compare RIPEMD output lengths against SHA-1, SHA-256, SHA-3, BLAKE2, or checksum algorithms.
  • Create repeatable RIPEMD test vectors for scripts, unit tests, and forensic notes.
  • Convert the same digest to lowercase hex, uppercase hex, Base64, or Base64URL for transport-specific formats.

Algorithm strength ratings:

  • RIPEMD-128: legacy only. Its 128-bit output gives about 64-bit generic collision resistance, so prefer modern hashes for new security-sensitive designs.
  • RIPEMD-160: legacy/interoperability. It has a 160-bit output and remains the best-known RIPEMD variant, but modern new systems normally choose SHA-256, SHA-3, or BLAKE2 instead.
  • RIPEMD-256: compatibility/niche use. The longer output is useful for formats that expect 256 bits, but it is not a simple security upgrade over RIPEMD-128.
  • RIPEMD-320: compatibility/niche use. The longer output is useful where a 320-bit digest is required, but it should not be treated as a current replacement for SHA-512-class designs.

Limitations and safe use: RIPEMD hashes are deterministic fingerprints, not encryption, authentication, or password storage by themselves. Do not hash passwords with plain RIPEMD; use a password-hashing tool such as bcrypt, Argon2, scrypt, or PBKDF2 with a salt and work factor. A digest proves that the same input was hashed, but it does not prove who created it unless it is used inside a keyed construction such as HMAC or a digital signature protocol.

API Usage Example:

POST /api/tools/crypto/ripemd
Content-Type: application/json

{
    "text": "Hello World",
    "algorithms": [
        "ripemd160",
        "ripemd256"
    ],
    "outputFormat": "hex"
}
Ready