Algorithms

SHA-384

SHA-512 with other start values cut to 48 bytes. With HMAC and common in TLS cipher suites
IDsha38402 / 24cryptographic · 384-bit
Hash / Cryptographic

SHA-384

SHA-512 with other start values, cut to 48 bytes.

Digest
384-bit · 48 bytes
HMAC
takes a key
Security
192-bit collision resistance
Family
16 in cryptographic
2 options, 0 required

Sample

hex
fdbd8e75a67f29f701a4e040385e2e23986303ea10239211af907fcbb83578b3e417cb71ce646efd0819dd8c088de1bd
base64
/b2OdaZ/KfcBpOBAOF4uI5hjA+oQI5IRr5B/y7g1eLPkF8txzmRu/QgZ3YwIjeG9

Options

encodingstring
default hex
Output encoding: hex, base64, base64url, binary
keystring
optional
HMAC key; enables HMAC mode

Access

Createcreate("sha384")
CLIhashes sha384 'hello world'
Tryplayground with the sample above
Kinsha256, sha512, sha512-half, sha3-256 +11

SHA-512 running on its own initial values, with the output cut to 48 bytes. That cut is also why it doesn't suffer the length extension trick plain SHA-256 and SHA-512 do. TLS suites with SHA384 in the name use it.

ts
create("sha384").hash("abc").digest;
// "cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7"

It isn't the first 48 bytes of SHA-512. Different start values, different digest.