Skip to content
yutils
Example

Input

yutils

Output (MD5 hex)

5b9c8d3e2a1f4b7d6e8c3a5b9d2f1c4e

Note

MD5 emits 32 hex characters. Broken for security, but still useful for checksums, ETags, and cache keys.

Usage / FAQ

When to use

  • File checksums for download integrity (not security)
  • Gravatar lookups, ETags, and cache keys
  • Compatibility with legacy systems or APIs that still emit MD5
  • Consistent short hashes for change detection on DB rows
  • Study why MD5 is broken — try producing two inputs with the same hash

FAQ

Q.Is MD5 really broken?
A.Yes. Theoretical weaknesses (1996), practical collisions (2004), forged signatures (2008). Never use for security — no passwords, TLS, or digital signatures.
Q.Why is it still around?
A.Speed and brevity (16 bytes, 32 hex chars). For non-security uses like ETags, cache keys, and checksums it's still fine. AWS S3 uses MD5 as the default ETag, for example.
Q.Is Gravatar safe to use with MD5?
A.Gravatar uses MD5 only as a stable identifier mapping email to avatar — not for security. But anyone with the email can reproduce the hash and de-anonymize users.
Fun facts
  • MD5 was designed by Ronald Rivest in 1991 to patch MD4's weaknesses, and standardized as RFC 1321. 'MD' stands for 'Message-Digest' — Rivest's hash series ran MD2/MD4/MD5 before branching into the RC ciphers.

    RFC 1321 (1992)
  • In 2004, Wang Xiaoyun's Shandong University team published a differential attack that produced MD5 collisions in minutes. That was 13 years before SHA-1's SHAttered, and the moment MD5 was retired from security use — it survives today only for non-adversarial integrity checks.

    Wang et al. 2004 (IACR ePrint)
  • In 2012 the Flame malware used a chosen-prefix MD5 collision to forge a Microsoft Terminal Services certificate and hijack the Windows Update channel. The first time MD5 collisions left academia and powered a nation-state attack — which is why 'don't use MD5 for passwords' isn't future-tense advice.

    Wikipedia — Flame malware