Hashing
SHA-384 hash generator
SHA-384 hash generator computes the 96-character SHA-384 digest of text you paste, entirely in your browser. SHA-384 is the 384-bit SHA-2 variant behind TLS 1.2 cipher suites and many certificate signature algorithms, so developers typically use it to verify digests published alongside those artifacts. Output is lowercase hex, always 96 characters, with an "Iterations" option for chained hashing.
How to use SHA-384
- Open SHA-384 in the Toolbox101 app.
- Paste the text whose digest you need into the
Inputbox. - Leave
Iterationsat1for a plain SHA-384; a higher number hashes the previous digest again that many times. - The 96-character result appears in the
Outputbox as you type. - Click
Copyto put the digest on your clipboard.
Worked example
SHA-384 returns the output below for this input.
Input
The quick brown fox jumps over the lazy dogOutput
ca737f1014a48f4c0b6dd43cb177b0afd9e5169367544c494011e3317dbf9a509cb1e5dc1e85a941bbee3d7f2afbc9b1Check it yourself: open SHA-384 and enter the same input.
Frequently asked questions
What is the difference between SHA-384 and SHA-512?
SHA-384 is the SHA-512 algorithm truncated to 384 bits with its own initial state, so its output is not a prefix of the SHA-512 digest for the same input. The shorter output fits 48-byte fields and is what several TLS 1.2 cipher suites standardize on when they name SHA384.
Why is a SHA-384 hash 96 characters?
A SHA-384 digest is 384 bits, or 48 bytes, and two hex characters encode each byte, so output is always 96 characters of lowercase hex regardless of input length, and the size never hints at the message. Even the empty string maps to a fixed digest: 38b060a751ac96384cd9327eb1b1e36a21fdb71114be07434c0cc7bf63f6e1da274edebfe76f65fbd51ad2f14898b95b.
Where is SHA-384 actually used today?
Commonly in TLS 1.2 cipher suites whose names end in SHA384, in ECDSA and RSA signature algorithms over SHA-384, and in some code-signing and certificate chains. If you are reproducing a published digest from one of those contexts, this tool matches openssl dgst -sha384.
Is SHA-384 more secure than SHA-256?
Not meaningfully in practice: both belong to the SHA-2 family, and collision resistance is bounded by half the digest size, so SHA-384 resists collisions up to 192 bits and SHA-256 to 128 bits, far beyond feasible attacks either way. The choice is usually set by protocol or interop requirements, not raw security.