YoSin Tools

SHA384 Hash Generator

Calculate SHA-384 hashes instantly online. Supports UTF-8, UTF-16, Hex, and Base64 input encodings. Enable HMAC-SHA384 for high-security message authentication paired with P-384 curves.

Input
Output
Share Link
Settings
Hash

Related Hash Tools

SHA384 FileHash from file SHA512512-bit SHA-2 SHA256256-bit SHA-2 SHA512/256Truncated 256-bit SHA1Legacy 160-bit

Frequently Asked Questions

What is SHA-384?
SHA-384 is a 384-bit truncation of SHA-512 from the SHA-2 family. It uses the same 64-bit SHA-512 core with different initialization values and discards the last 128 bits of the 512-bit state. Output is a 96-character hexadecimal string.
When should I use SHA-384 vs SHA-256?
SHA-256 is preferred for most applications. SHA-384 is used when you need to match the security level of P-384 elliptic curve cryptography, or when government/defense standards (such as NSA Suite B) require it. It offers 192 bits of collision resistance vs SHA-256's 128 bits.
What TLS cipher suites use SHA-384?
TLS 1.2 cipher suites like TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 use SHA-384 for the PRF. These suites are chosen when maximizing security, particularly in environments complying with NSA Suite B or NIST SP 800-57 recommendations at the 192-bit security level.
Is SHA-384 faster than SHA-256?
On 64-bit CPUs, SHA-384 is typically faster than SHA-256 because it uses native 64-bit operations. On 32-bit systems SHA-256 wins. SHA-384 and SHA-512 have nearly identical throughput since they share the same core — SHA-384 just truncates the output.

About SHA384 Hash Generator

SHA-384 is a member of the SHA-2 family that produces a 384-bit (96 hex character) digest. It is computed using the SHA-512 algorithm with different initialization constants and by discarding the last 128 bits of the 512-bit output state. This gives SHA-384 the performance advantages of the 64-bit SHA-512 core while producing a shorter, fixed-length digest suitable for protocols that require 384-bit outputs.

SHA-384 in TLS and Suite B

SHA-384 is used in TLS 1.2 cipher suites paired with 256-bit AES-GCM to provide a consistent 192-bit security level. NSA Suite B cryptography — used in classified and sensitive government communications — specifies SHA-384 alongside P-384 elliptic curves. Servers configured for Suite B compliance will negotiate these cipher suites preferentially. TLS 1.3 replaced cipher-suite-based PRF selection with a unified HKDF construction, reducing the operational importance of SHA-384 selection in newer deployments.

SHA-384 vs SHA-512

SHA-384 and SHA-512 are computed identically except for initialization constants and output truncation. The full 512-bit state is computed, then SHA-384 discards the last 128 bits. As a result, SHA-384 does not leak any information about the truncated bits. Performance is essentially identical between the two on the same platform. SHA-512 is preferred when the full 512-bit output is needed; SHA-384 is preferred when the protocol requires a 384-bit output.

HMAC-SHA384

HMAC-SHA384 is defined in RFC 4231 and produces a 384-bit authentication tag. It is used in JWT HS384 tokens and in TLS PRF computations for SHA-384 cipher suites. Enable the HMAC toggle in Settings and enter your secret key to compute HMAC-SHA384 values with any input encoding.

Security Level

SHA-384 provides 192 bits of collision resistance and 384 bits of preimage resistance. This exceeds the 128-bit collision resistance of SHA-256 and provides a matching security level for P-384 (ECDH/ECDSA) and RSA-7680 key pairs. For most applications, SHA-256's 128-bit collision resistance is considered more than sufficient. SHA-384 is relevant primarily when high-assurance standards mandate the higher security level.