Advertisements

headerup to 320x100 / 728x90

HMAC-SHA224 Generator

Generate a keyed SHA-224 HMAC fingerprint for compact message authentication in embedded and IoT systems.

Secret:
Input
Loading editor...
Output

Output will appear here...

Advertisements

content bottomup to 300x250

What is HMAC-SHA224 Generator

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-SHA224 Generator produces an HMAC using the SHA-224 hash function and returns the 56-character hexadecimal signature.

HMAC-SHA224 fits workflows where a 224-bit output is required but SHA-3 is not mandated, which is common in embedded protocols and some enterprise stacks.

Why use it

  • Sign payloads for APIs that mandate a 224-bit keyed hash.
  • Match spec vectors from embedded or IoT systems using SHA-224.
  • Generate stable, compact MACs for bandwidth-sensitive protocols.
  • Test interoperability between Node.js, Go, and Python HMAC-SHA224 implementations.
  • Produce fingerprints shorter than HMAC-SHA256 without moving to SHA-1.

Features

  • 56-character HMAC-SHA224 hex output
  • RFC 2104 HMAC construction
  • Runs entirely in the browser
  • Matches OpenSSL output
  • Great for bandwidth-sensitive MACs

How to use HMAC-SHA224 Generator

  1. Paste the message. Place the canonical payload you are signing into the input panel.
  2. Enter your key. Paste the shared secret into the Secret field.
  3. Copy the digest. Use the copy button to put the 56-character HMAC-SHA224 hex output into your request header.

Example (before/after)

Message + key

message: audit-event
key: sha224-audit-key

HMAC-SHA224 hex digest

e97b9d90a25fa7c4b6d2178a5e36d24fbd65c9a55a5ef4e9a8b1723a

Common errors

Mixing SHA-224 with SHA3-224

The two use completely different constructions and produce different digests.

Fix: Pick the variant your spec names — HMAC-SHA224 or HMAC-SHA3-224.

Signing the wrong canonical string

Subtle differences in headers, timestamps, or body encoding change the signature.

Fix: Reproduce the server's canonicalization exactly before signing.

Incorrect hex vs. base64 output

Some APIs expect base64 HMACs, not hex.

Fix: Convert the hex signature to base64 with a matching tool if needed.

FAQ

Is HMAC-SHA224 widely supported?

Most modern crypto libraries expose it, although it is less common than HMAC-SHA256.

What is the output length?

224 bits or 56 hex characters.

Is it stronger than HMAC-SHA1?

Yes. It offers 112-bit collision resistance and benefits from SHA-2 design.

Does it match OpenSSL?

Yes. `openssl dgst -sha224 -hmac <key>` produces the same output.

Is signing done in the browser?

Yes. Your key and payload stay on your device.

Can I combine it with base64 URL encoding?

Yes, pass the hex output through a base64 encoder to match URL-safe schemes.

Related tools

Compare HMAC-SHA224 with stronger SHA-2 and SHA-3 keyed variants. You can also browse the full Cryptography & Hashing category for more options.