Confusing SHA-3 with Keccak
Pre-FIPS Keccak libraries use different padding than FIPS 202 SHA-3.
Fix: Match the variant your peer requires, specifically checking for the FIPS 202 padding byte.
header • up to 320x100 / 728x90
Generate an HMAC-SHA3 keyed-hash authentication code using the Keccak family for modern cryptographic workflows.
Output will appear here...
content bottom • up to 300x250
sidebar • 160x600
Last reviewed:
HMAC (Hash-based Message Authentication Code) combines a cryptographic hash with a secret key to verify both the integrity and authenticity of a message.
HMAC-SHA3 Generator produces an HMAC using the FIPS 202 SHA-3 hash function and a shared secret key, returning the keyed digest in hexadecimal.
It is useful when you need algorithm diversity from SHA-2 or when a protocol specifies HMAC-SHA3 explicitly — for example, some post-quantum migration plans pair SHA-3 constructions alongside SHA-2 HMACs.
message: sha3-migration-vector key: sha3-rollover-key
b7e4a2ad76c8f6b1920c1c0f7b4ffa5f6ddf6aeccf94e02d4a3cd8bc25c1f1ad
Pre-FIPS Keccak libraries use different padding than FIPS 202 SHA-3.
Fix: Match the variant your peer requires, specifically checking for the FIPS 202 padding byte.
Passing a hex key as UTF-8 changes the effective bytes and therefore the HMAC.
Fix: Decode the key to bytes first, or agree on an encoding with your peer.
This tool uses FIPS 202 SHA-3, not legacy Keccak.
Fix: Use a dedicated Keccak tool when targeting pre-standard implementations.
By default it uses SHA3-256, so 256 bits (64 hex characters).
This tool focuses on SHA3-256. Use the dedicated tools for SHA3-224/384/512 HMAC variants when needed.
Yes, under FIPS 198-1 used with SHA-3 (FIPS 202).
Both provide strong authentication. HMAC-SHA3 offers structural diversity from SHA-2.
No. HMAC-SHA3 is computed on your device.
For algorithm diversity, regulatory requirements, or when implementing post-quantum migration plans.
Combine HMAC-SHA3 with plain SHA-3 hashes and matched HMAC-SHA2 variants. You can also browse the full Cryptography & Hashing category for more options.
Generate HMAC authentication codes
Generate MD5, SHA-1, SHA-256, SHA-384, SHA-512, or SHA3 checksums from pasted text, perfect for quick integrity checks and deduplication.
Generate an HMAC-MD5 message authentication code from a plaintext message and shared secret key.
Generate an HMAC-SHA1 code to sign webhook payloads, AWS-style requests, or legacy API authentication schemes.
Generate a keyed SHA-224 HMAC fingerprint for compact message authentication in embedded and IoT systems.
Generate an HMAC-SHA256 code for signing JWTs, webhook payloads, API requests, and OAuth tokens.
Generate an HMAC-SHA384 code for enterprise-grade message authentication and PCI-friendly signatures.
Generate an HMAC-SHA512 code for high-entropy signatures on large payloads and long-lived tokens.
Generate SHA-3 cryptographic hash
Generate a SHA3-224 (Keccak) hash from any text string for secure fingerprinting and message authentication.
Generate a SHA3-256 hash from any text string to match Ethereum, Keccak-family, and NIST FIPS 202 checksums.
Generate a SHA3-384 hash from any text for long-collision-resistant digests and certificate fingerprints.