SHA-224 is a truncated variant of SHA-256 producing a 224-bit (56 hex character) hash. It is part of the SHA-2 family and is used in some TLS and certificate applications. This tool uses the browser's built-in Web Crypto API — nothing is sent to a server.
SHA-224 is part of the SHA-2 family defined in FIPS 180-4. Internally it uses the same 32-bit compression function as SHA-256 but with a different set of initial hash values, then truncates the result to 224 bits. The smaller digest size matched the 112-bit security of 3DES, which is why SHA-224 was originally introduced.
In practice you'll see SHA-224 in some TLS cipher suites and a few NIST-driven government contexts. The output here is generated by the browser's Web Crypto API and matches openssl dgst -sha224 byte-for-byte.
SHA-224 was added to FIPS 180-2 to provide a digest size matching the security strength of 3DES (112 bits of collision resistance). Today it's mostly used in legacy systems and certain TLS cipher suites; SHA-256 is the more common choice.
SHA-224 uses the same compression function as SHA-256 but with different initial hash values, then truncates the final state to 224 bits. So you can't derive a SHA-224 digest by simply truncating a SHA-256 digest.
Yes — there are no practical collision or preimage attacks. Its 112-bit collision resistance is lower than SHA-256's 128-bit, but still well beyond brute-force range.
UTF-8. The text is converted via TextEncoder before being passed to the Web Crypto API, matching the behaviour of openssl, Node's crypto module and Python's hashlib.
Explore the full suite of Hash & Crypto tools and 290+ other free utilities at Chunky Munster.