SHA-384 belongs to the SHA-2 family. It produces a 384-bit digest, written as 96 hexadecimal characters. It is closely related to SHA-512 but uses different initial values and a shorter output.
The generator calculates SHA-384 for your input. The lookup then searches for an already indexed matching plaintext, so a valid digest is not guaranteed to return a result.
SHA-384 is suitable for integrity and digital-signature protocols when used correctly. By itself it is not a password-storage function because it is intentionally fast; use a salted password KDF instead.
These examples hash exactly the text “hello” without a trailing newline. A space or line break would change the digest.
printf %s 'hello' | openssl dgst -sha384echo hash('sha384', 'hello');const bytes = new TextEncoder().encode('hello');
const digest = await crypto.subtle.digest('SHA-384', bytes);A SHA-384 digest contains 96 hexadecimal characters, representing 384 bits.
It uses the same broad construction as SHA-512, different initial values and a 384-bit output.
The database can only return previously indexed plaintexts. Salted, random or uncommon values are usually absent.
SHA-384 belongs to the SHA-2 family and produces a 384-bit digest. It is used by some TLS profiles and digital-signature systems.
It uses the SHA-512 structure with a distinct initial state and returns 384 bits.
No. A fast hash enables massive guessing; prefer Argon2id, scrypt or bcrypt.
Not for the value itself, but spaces and prefixes must be removed before comparison.
These commands hash the five UTF-8 bytes in “hello”, without adding a trailing newline.
printf %s "hello" | openssl dgst -sha384hash('sha384', 'hello');const bytes = new TextEncoder().encode('hello');
const digest = await crypto.subtle.digest('SHA-384', bytes);