[{"data":1,"prerenderedAt":270},["ShallowReactive",2],{"content:en:sha384-generator":3},{"id":4,"title":5,"body":6,"description":246,"extension":247,"faq":248,"kind":261,"locale":262,"meta":263,"navigation":264,"path":265,"seo":266,"seoTitle":267,"stem":268,"__hash__":269},"pages\u002Fen\u002Fsha384-generator.md","SHA-384 Hash Generator",{"type":7,"value":8,"toc":235},"minimark",[9,14,18,21,24,28,39,49,53,86,96,111,115,118,122,125,128,132,135,141,145,201,205,227],[10,11,13],"h2",{"id":12},"what-this-tool-calculates","What this tool calculates",[15,16,17],"p",{},"SHA-384 belongs to SHA-2 and outputs 384 bits, represented by 96 hexadecimal characters. It uses a distinct initialization from SHA-512; it is not correct to calculate SHA-512 and simply keep the first 96 characters. This tool calculates the SHA-384 algorithm itself.",[15,19,20],{},"Use this page when a specification, signature workflow or integration explicitly identifies SHA-384. Keeping the algorithm name next to an exported digest helps avoid mixing it with a truncated value from another function. Hexadecimal letter case is only a display convention; it does not change the digest bytes.",[15,22,23],{},"A digest alone is neither encryption nor a digital signature. To reproduce a known value, check message encoding, all whitespace and the exact file bytes. If a protocol calls for HMAC-SHA384, use the separate HMAC tool: appending a key to a message is not an equivalent construction.",[10,25,27],{"id":26},"worked-example","Worked example",[15,29,30,34,35,38],{},[31,32,33],"code",{},"UTF-8"," · ",[31,36,37],{},"abc"," · SHA-384",[40,41,47],"pre",{"className":42,"code":44,"language":45,"meta":46},[43],"language-text","cb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7\n","text","",[31,48,44],{"__ignoreMap":46},[10,50,52],{"id":51},"how-to-calculate-and-compare","How to calculate and compare",[54,55,56,72,79],"ol",{},[57,58,59,60,64,65,68,69,71],"li",{},"Enter the exact text in ",[61,62,63],"strong",{},"Input text",", or choose ",[61,66,67],{},"Example"," to load ",[31,70,37],{},". Text is encoded as UTF-8; spaces and line endings are preserved.",[57,73,74,75,78],{},"In single-text mode, non-empty input up to 64 KiB updates after a short pause. Click ",[61,76,77],{},"Generate hash"," for empty input or larger text. Changing the input clears the previous result.",[57,80,81,82,85],{},"To check a saved file instead, open ",[61,83,84],{},"File checksum",", confirm the algorithm, and choose or drop the file. File mode reads its original bytes and starts automatically.",[15,87,88,89,92,93,95],{},"For line-by-line results, enable ",[61,90,91],{},"One hash per line",", choose whether to include empty lines, then click ",[61,94,77],{},". Line mode does not calculate automatically. CRLF, LF and CR separate records and are not included in each line's digest. Duplicate lines retain their original line numbers.",[15,97,98,99,102,103,106,107,110],{},"Paste only the complete hexadecimal reference into ",[61,100,101],{},"Compare expected value (optional)"," and click ",[61,104,105],{},"Check",". Letter case and surrounding pasted whitespace are ignored; internal spaces and the wrong length are rejected. ",[61,108,109],{},"Copy"," retains the full result. TXT and CSV exports include identifiers, algorithm names and digests, not source text or secret keys.",[10,112,114],{"id":113},"limits-privacy-and-next-steps","Limits, privacy and next steps",[15,116,117],{},"Text is limited to 10 MiB and line mode to 10,000 records, including empty records before filtering. Files are limited to 50 queue entries and 1 GiB each, read sequentially in 2 MiB chunks. These limits protect browser resources; they do not guarantee fast processing on every phone. Cancel if needed. Calculation takes place in the browser, while normal page and asset requests still reach the hosting service.",[10,119,121],{"id":120},"using-the-exact-sha-384-variant-a-specification-requests","Using the exact SHA-384 variant a specification requests",[15,123,124],{},"A SHA-384 digest is 48 bytes. Hex represents each byte with two characters, producing the 96-character value returned here. A signature or integration may encode those same digest bytes as Base64 instead; a visible length difference is not enough to conclude that the hash algorithm is wrong.",[15,126,127],{},"SHA-384 shares a family with SHA-512 but has different initial values. Keeping the first 96 characters of a SHA-512 digest will not reproduce SHA-384. Select SHA-384 before processing the file, and preserve the full output. If a signed document or certificate mentions SHA-384, this calculator can reproduce a raw digest, but it does not create or validate the signature or parse that container's signed byte range.",[10,129,131],{"id":130},"a-direct-check-of-the-sha-384-truncation-mistake","A direct check of the SHA-384 truncation mistake",[15,133,134],{},"Use Example on this page and on SHA-512. Compare SHA-384 of abc with the first 96 characters of SHA-512 of abc. They differ even though the displayed lengths agree.",[40,136,139],{"className":137,"code":138,"language":45,"meta":46},[43],"SHA-384 \u002F abc:\ncb00753f45a35e8bb5a03d699ac65007272c32ab0eded1631a8b605a43ff5bed8086072ba1e7cc2358baeca134c825a7\nSHA-512 \u002F abc \u002F first 96 hex characters only (NOT SHA-384):\nddaf35a193617abacc417349ae20413112e6fa4e89a97ea20a9eeee64b55d39a2192992a274fc1a836ba3c23a3feebbd\n",[31,140,138],{"__ignoreMap":46},[10,142,144],{"id":143},"sha-384-format-and-construction-mistakes","SHA-384 format and construction mistakes",[146,147,148,164],"table",{},[149,150,151],"thead",{},[152,153,154,158,161],"tr",{},[155,156,157],"th",{},"Observed problem",[155,159,160],{},"Why it happens",[155,162,163],{},"What to do",[165,166,167,179,190],"tbody",{},[152,168,169,173,176],{},[170,171,172],"td",{},"A shortened SHA-512 does not match",[170,174,175],{},"SHA-384 is not a substring of ordinary SHA-512",[170,177,178],{},"Recalculate with SHA-384 selected.",[152,180,181,184,187],{},[170,182,183],{},"The expected value is Base64",[170,185,186],{},"The comparison field accepts hexadecimal",[170,188,189],{},"Decode and re-encode the digest correctly, or obtain a hex reference.",[152,191,192,195,198],{},[170,193,194],{},"The certificate's signature is much longer",[170,196,197],{},"A signature is not the raw digest",[170,199,200],{},"Use the relevant signature-verification tool and signed-byte rules.",[10,202,204],{"id":203},"related-tools-and-guides","Related tools and guides",[206,207,208,215,221],"ul",{},[57,209,210],{},[211,212,214],"a",{"href":213},"\u002Fsha512-generator","SHA-512",[57,216,217],{},[211,218,220],{"href":219},"\u002Fhmac-generator","HMAC message authentication",[57,222,223],{},[211,224,226],{"href":225},"\u002Ffile-md5","File checksum calculator",[15,228,229],{},[211,230,234],{"href":231,"rel":232},"https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F180-4\u002Fupd1\u002Ffinal",[233],"nofollow","FIPS 180-4",{"title":46,"searchDepth":236,"depth":236,"links":237},2,[238,239,240,241,242,243,244,245],{"id":12,"depth":236,"text":13},{"id":26,"depth":236,"text":27},{"id":51,"depth":236,"text":52},{"id":113,"depth":236,"text":114},{"id":120,"depth":236,"text":121},{"id":130,"depth":236,"text":131},{"id":143,"depth":236,"text":144},{"id":203,"depth":236,"text":204},"Calculate the full SHA-384 digest for text and files, with 96-character output and exact-byte comparison.","md",[249,252,255,258],{"question":250,"answer":251},"Can I obtain SHA-384 by cutting off SHA-512?","No. SHA-384 uses different initialization values. Select SHA-384 directly to reproduce the required algorithm.",{"question":253,"answer":254},"Why is SHA-384 shown as 96 characters rather than 48?","The digest contains 48 bytes. Hexadecimal uses two characters per byte, so the complete displayed result is 96 characters.",{"question":256,"answer":257},"Does HMAC-SHA384 equal SHA-384 of key plus message?","No. HMAC uses a defined keyed construction. Choose HMAC-SHA-384 on the HMAC page; concatenating a key and message is not equivalent.",{"question":259,"answer":260},"Can this page validate a SHA-384 certificate signature?","No. A certificate signature involves a signed structure, a public-key algorithm and verification rules. This page calculates a raw text or file digest only.","tool","en",{},true,"\u002Fen\u002Fsha384-generator",{"title":5,"description":246},"SHA-384 Hash Generator — md5hash.net","en\u002Fsha384-generator","cjLzyZEYBHCE0a_cGIhTe0GixR7bF0E4z-eDfctyUiE",1792048883697]