HMAC
RIPEMD-160 HMAC generator
Try it
HMAC-RIPEMD160 hex.
Loading…
How to use this tool, examples, and related tips.
Enter your message in the message field.
Enter your secret key.
The HMAC-RIPEMD160 tag is computed instantly and displayed as a 40-character hexadecimal string.
Copy the output for your application or verification workflow.
HMAC-RIPEMD160 is the HMAC construction applied using RIPEMD-160 as the underlying hash function. It produces a 160-bit (40-character hex) authentication tag. RIPEMD-160 was developed independently of NSA-designed hash functions, making HMAC-RIPEMD160 a useful choice in systems that require algorithm diversity or prefer non-NSA cryptographic primitives. It sees use in blockchain tooling — particularly Bitcoin-adjacent protocols — and in PGP/OpenPGP implementations where RIPEMD-160 is a supported digest algorithm.
Blockchain and cryptocurrency tooling — RIPEMD-160 is used in Bitcoin's address derivation pipeline; HMAC-RIPEMD160 appears in related protocol and wallet implementations.
PGP and OpenPGP workflows — OpenPGP supports RIPEMD-160 as a message digest algorithm; use this tool to generate or verify HMAC tags in PGP-adjacent tooling.
Algorithm diversity requirements — When a system requires an HMAC constructed from a non-SHA, non-NSA-designed hash function.
Debugging and verification — Reproduce HMAC-RIPEMD160 values manually when diagnosing signature mismatches in systems that use it.
Answers about this tool and how your data is handled.
RIPEMD-160 has no known practical attacks, and the HMAC construction adds key-based authentication on top. It is considered sound for current use cases, though HMAC-SHA256 is more widely supported and audited for general-purpose authentication.
Primarily for algorithm diversity or legacy compatibility. RIPEMD-160 was designed independently of the NSA-developed SHA family, which is relevant in systems with specific cryptographic diversity requirements or in blockchain protocols that use it by convention.
No. HMAC computation runs entirely in your browser. Your message and key never leave your machine.
Always 40 hexadecimal characters, representing 160 bits — matching RIPEMD-160's output length.
Bitcoin address generation (SHA-256 followed by RIPEMD-160), OpenPGP key fingerprints, and some legacy TLS and S/MIME implementations.
Même catégorie d’abord, puis d’autres utilitaires.
HMAC
HMAC-RIPEMD160 hex.