MD5 of `exemplo1`
- Input
- exemplo1
- Expected output
- 1803c39c605b289b1a034d073a09b095 (32 caracteres hex, 128 bits)
The output is always 32 characters, whether the input is one word or a gigabyte-sized file.
Carregando ferramenta… / Loading tool…
file integrity checksum
A checksum keeps no secret at all, it proves a file arrived exactly the way it left. The whole idea rests on one property: changing a single input bit has to scramble the entire output, and that is what separates a usable hash algorithm from one that is already broken.
The output is always 32 characters, whether the input is one word or a gigabyte-sized file.
1 character of input difference, and the hash shares no visible chunk with `exemplo1`, the avalanche effect at work.
Twice the MD5 output size, the practical standard today for verifying downloads and for digital signatures.
Yes. Text, files and HMAC secrets are processed directly in the browser without any upload.
No, a hash alone only proves the file has not changed since the hash was generated; anyone holding the file can recompute the same hash, so authorship and origin need a separate digital signature, which involves a private key, not just the checksum value.
Because the algorithm processes the raw bytes, not what shows on screen: an extra space, a different line break (CRLF versus LF), or metadata embedded in the file already change the byte sequence enough to trigger the avalanche effect and produce a completely different hash.
Yes, for catching accidental file corruption, like an interrupted download, MD5 is still fast and good enough, because nobody in that scenario is deliberately forging a collision; the problem only shows up when the hash has to resist an active attacker, and then SHA-256 is required.
CRC32 is a 32-bit checksum built to catch accidental transmission errors on a network or disk, not to resist an adversary; it is much faster to compute than a cryptographic hash, but forging a deliberate collision against it is trivial, so it should never replace MD5, SHA-1 or SHA-256 in a security context.
—Hash moderno e amplamente suportado para integridade.
Text, files and secrets are processed locally. Nothing is sent to the server.