HMAC-SHA-256
256 bitsThe primary authentication standard: underlying JWT (HS256), AWS Signature V4, Telegram initData, and Stripe / GitHub webhooks.
Generate Hash-based Message Authentication Codes (HMAC) in your browser. Supports JWT standards (HS256/HS512), AWS SigV4, GOST R 34.11-2012 Streebog, Chinese SM3, BLAKE2, and SHA-3. Zero server transmission.
The key is handled as UTF-8 text. We recommend using a cryptographically strong secret of at least the hash block length.
— — — — — — — — — — — — — — — — — — HMAC (Keyed-Hash Message Authentication Code) is a specific type of message authentication code involving a cryptographic hash function in combination with a secret key. It guarantees both data integrity and authenticity: an attacker without the secret key cannot forge a valid tag.
HMAC(K, m) = H( (K ⊕ opad) ‖ H( (K ⊕ ipad) ‖ m ) )The primary authentication standard: underlying JWT (HS256), AWS Signature V4, Telegram initData, and Stripe / GitHub webhooks.
High-security 512-bit MAC. Best suited for high-value financial APIs, JWT HS512, and post-quantum security requirements.
Truncated intermediate SHA-2 digest mandated by US Federal Suite B and TLS 1.3 cipher suites.
Compact 224-bit SHA-2 variant tailored for constrained communication channels and legacy interoperability.
NIST Keccak standard featuring inherent resistance to length-extension attacks, ideal for cutting-edge smart contract architectures.
512-bit maximum-security HMAC for long-term document and ledger verification.
Intermediate 384-bit SHA-3 authentication tag aligned with AES-192 encryption suites.
Compact 224-bit SHA-3 digest engineered to replace legacy 224-bit hashes.
64-bit optimized BLAKE2b HMAC: faster than MD5 while matching the security level of SHA-3.
256-bit BLAKE2b: maximum throughput on modern 64-bit CPUs with a compact output length.
32-bit architecture variant optimized for microcontrollers, embedded IoT hardware, and WireGuard.
HMAC-MD5 (RFC 2104). While standalone MD5 is vulnerable to collision attacks, HMAC-MD5 remains theoretically secure but is discouraged for modern architectures.
HMAC-SHA-1 remains active in legacy systems: OAuth 1.0a, TOTP/HOTP 2FA tokens, and AWS SigV2.
160-bit European cryptographic standard. Essential to Bitcoin address derivation (HASH160).
HMAC based on Russian standard GOST R 34.11-2012 (Streebog 256-bit). Standardized for national digital signature verification.
512-bit GOST R 34.11-2012 Streebog MAC for high-compliance government cryptographic data integrity.
Chinese cryptographic standard GB/T 32918. Mandatory for commercial cryptography and banking in China.
512-bit MAC built on the W block cipher (modified AES MDS matrix) by Vincent Rijmen and Paulo Barreto.
HMAC verifies that a received message is authentic and has not been altered in transit. Unlike a raw hash, computing an HMAC requires a shared secret key.
SHA-256 is an unkeyed hash that anyone can compute for any text. HMAC-SHA256 uses nested hashing with inner (ipad) and outer (opad) key paddings, making it mathematically impossible to forge without knowing the secret key.
HMAC-SHA-256 is the standard choice for modern software (JWT HS256, API webhooks). For higher security requirements, choose HMAC-SHA-512 or HMAC-SHA3-256. Use HMAC-SHA-1 or HMAC-MD5 only when required for backward compatibility.
The secret key should be at least as long as the output size of the chosen hash function. For HMAC-SHA256, use at least 32 cryptographically random bytes (256 bits). Keys longer than the hash block size are pre-hashed automatically.
Yes. Naive construction H(key || message) is vulnerable to length extension attacks in Merkle-Damgård hashes. HMAC's double-hash formula H(K ⊕ opad || H(K ⊕ ipad || message)) completely neutralizes this vector.
JSON Web Tokens (JWT HS256/HS384/HS512), AWS Signature V4, Stripe and GitHub webhook signatures, TOTP/HOTP 2-factor authentication, IPsec, and TLS 1.3 PRF.
An authentication code built on top of the Russian national cryptographic hash standard GOST R 34.11-2012 (Streebog). Widely required in government IT systems across Russia and the EAEU.
SM3 is the official national standard of China (GB/T 32918), mandatory for commercial cryptography, UnionPay financial transactions, and compliance in China.
No. All computations are executed 100% locally in your browser using JavaScript and WebAssembly. No sensitive credentials or payloads ever leave your device.
All operations run locally in your browser.