Empty string
- Input
- ∅
- Expected output
- d41d8cd98f00b204e9800998ecf8427e
This value comes straight from RFC 1321: any correct MD5 implementation has to return exactly this digest for an empty input.
Carregando ferramenta… / Loading tool…
md5 generator
MD5 returns a 128-bit digest as 32 hexadecimal characters, defined by RFC 1321 in 1992. It still shows up in download checksums and file-deduplication scripts, but it lost every security use after the first practical collision, published in 2004.
This value comes straight from RFC 1321: any correct MD5 implementation has to return exactly this digest for an empty input.
The official test vector RFC 1321 cites for the string "abc", used for decades to confirm an implementation follows the standard.
Changing just the last letter to "jkit.toolz" flips the whole digest to 3803195eb34836da4d2fc6c03b8402d3: that avalanche effect is why MD5 still catches accidental corruption, even though it is unsafe against a deliberate attack.
Yes. Text, files and HMAC secrets are processed directly in the browser without any upload.
Only for checks with no adversary: comparing two files you generated yourself or confirming a download did not corrupt in transit. After the 2004 practical collision and the faster version demonstrated in 2005, it offers no protection against anyone deliberately trying to forge the result.
Because the 32-character hexadecimal format became standard in scripts, changelogs, and integrations published before 2005. Rewriting those references means touching legacy systems many teams would rather not touch, so the original MD5 value keeps getting cited decades later.
No. Without an adjustable computational cost or a built-in salt, an MD5 of a password falls quickly to a rainbow table or a GPU testing billions of combinations per second. The current standard for passwords is bcrypt, scrypt, or Argon2.
—Checksum legado rápido, não seguro para proteção moderna.
Text, files and secrets are processed locally. Nothing is sent to the server.