About the SHA-384 Hash Generator
SHA-384 is SHA-512 with a different initial value and its output truncated to 384 bits, giving 96 hexadecimal characters. It is common in TLS cipher suites and code-signing, where a digest between SHA-256 and SHA-512 in length is wanted. The truncation also makes it resistant to length-extension attacks, unlike SHA-256 and SHA-512.
The reason truncation blocks length extension is that the attacker never gets to see the full internal state. SHA-512 hands back its entire chaining value, which is all anyone needs in order to carry on hashing from where it stopped, while SHA-384 throws away 128 bits of that state before printing. There is nothing left to resume from. SHA-512/256 exists for the same reason at a shorter output length.
In the wild you meet it in TLS suites such as ECDHE-RSA-AES256-GCM-SHA384, in code-signing manifests, and in Subresource Integrity attributes where a sha384- prefix sits in front of a Base64 digest. That last case is the one where the Base64 option here matters more than hex, because an SRI attribute will not accept a hexadecimal digest at all. It is a secure SHA-2 member and, being fast, not for passwords. This tool computes it locally from the UTF-8 bytes of your text and offers hex or Base64 output. To see the whole SHA-2 family side by side, use the All Hash Generator.
How to use
- Paste text.
- Choose hex or Base64.
- Copy the SHA-384 hash.
Common questions
- How is SHA-384 related to SHA-512?
- It is SHA-512 with a different starting value, truncated to 384 bits, which also blocks length-extension attacks.
- Where is SHA-384 used?
- In TLS cipher suites, code-signing and some government standards.
- Is it secure?
- Yes, with no known practical attacks. It is fast, so not for password storage.