Is this hash secure for passwords?

For passwords, use bcrypt or Argon2 instead. Simple hashes like MD5 and SHA are too fast and vulnerable to rainbow table attacks.

Can I decrypt a hash?

No, hashes are one-way functions. You cannot reverse a hash to get the original input. You can only compare hashes to verify if inputs match.

Why are there different hash algorithms?

Different algorithms offer varying levels of security, speed, and output length. Newer algorithms like SHA-256 are more secure than older ones like MD5.

SHA384 Hash Generator

Generate cryptographic hashes instantly with this sha384 hash generator. Verify data integrity and create secure checksums.

About SHA384 Hash

Hashing algorithms transform input data into fixed-length strings. They're one-way functions—you can create a hash from data, but you can't reverse it to get the original data back.

Technical Details

Deterministic: Same input always produces same output
Fixed Length: Output size is constant regardless of input
Collision Resistant: Extremely unlikely for two inputs to produce same hash
One-Way: Cannot reverse-engineer the original input

Common Use Cases

Password storage and verification
File integrity checking
Digital signatures
Data deduplication
Blockchain and cryptocurrency

Security Considerations

For password hashing, use bcrypt, scrypt, or Argon2 instead of MD5 or SHA. These are designed to be slow, making brute-force attacks impractical.

Where SHA-384 Fits

SHA-384 is SHA-512 truncated to 384 bits, with different initial values. That construction matters: because the output is shorter than the internal state, SHA-384 is **immune to length-extension attacks**, which SHA-256 is not.

Algorithm	Output	Length-extension resistant
SHA-256	256 bits	No
SHA-384	384 bits	Yes
SHA-512	512 bits	No
SHA-512/256	256 bits	Yes

On 64-bit hardware SHA-384 is often *faster* than SHA-256, because the SHA-512 family operates on 64-bit words.

It appears in TLS 1.3 cipher suites, in Suite B cryptography, and anywhere a 192-bit security level is specified. For general use SHA-256 remains the default — SHA-384 is the choice when a standard names it or when length-extension resistance is needed without HMAC.

The Avalanche Effect

A one-character change produces a completely different digest — not a similar one. That property is what makes a hash useful as a fingerprint:

Input	MD5	CRC32
`hello`	`5d41402abc4b2a76b9719d911017c592`	`3610a686`
`hello.`	`d94c10e437d18531e122ed0b45badd2a`	`0a39d4f1`
`Hello`	`8b1a9953c4611296a827abf8c47804d7`	`f7d18982`

hello and Hello differ by one bit of one byte, and share no part of their output. RIPEMD-160 of hello is 108f07b8382412612c048d07d13f814118445acd, and of Hello is d44426aca8ae0a69cdbc4021c64fa5ad68ca32fe — same story.

Digest Length and Collision Resistance

Algorithm	Output	Birthday bound	Status
CRC32	32 bits	~77,000 values	Checksum only
MD5	128 bits	2⁶⁴ in theory	Broken — collisions in seconds
SHA-1	160 bits	2⁸⁰ in theory	Broken — SHAttered, 2017
RIPEMD-160	160 bits	2⁸⁰	No practical attack
SHA-256	256 bits	2¹²⁸	Current standard
SHA-512	512 bits	2²⁵⁶	Standard, faster on 64-bit

The birthday bound is where a 50% chance of *some* collision appears among random inputs. MD5 and SHA-1 fall far short of theirs because both have practical collision attacks — you can construct two different files with the same digest, which is precisely what a signature must prevent.

Never Hash a Password With These

A general-purpose hash is designed to be fast, which is exactly wrong for passwords: speed helps the attacker. Use a deliberately slow KDF — bcrypt, scrypt or Argon2id — with a per-password salt. A GPU tries billions of SHA-256 guesses a second and a few thousand bcrypt guesses a second, and that gap is the entire defence.

SHA384 Hash Generator