Hash Generator

SHA256 digest of 3 UTF-8 byte(s): ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad.

How it works

• Encoded the input as 3 UTF-8 byte(s).
• Applied the SHA256 compression function defined by the cited standard.
• Formatted the 256-bit digest as 64 lower-case hex characters.

SHA256(message) = ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

• Computed with the bundled implementation, which matches the published known-answer vectors.

Methodology

1. Encode the input text as UTF-8 bytes, so the digest is locale-independent and matches the standard test vectors.
2. Apply the FIPS 180-4 SHA family or the RFC 1321 MD5 compression function with the algorithm's initial state, padding and 32/64-bit message schedule.
3. Format the digest as lower-case hexadecimal; the page reports the bit length and the UTF-8 byte length of the input.
4. When the browser exposes the Web Crypto API, the SHA-family digest is computed with crypto.subtle and cross-checked in tests against the bundled engine.

Usage

1. Type or paste the text to hash.
2. Choose SHA-1, SHA-256, SHA-384, SHA-512 or MD5.
3. Read the hexadecimal digest; use Copy result to reuse it.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

SHA-256 of "abc"

{
  "text": "abc",
  "algorithm": "sha256"
}

SHA-1 of "abc"

{
  "text": "abc",
  "algorithm": "sha1"
}

MD5 of "abc"

{
  "text": "abc",
  "algorithm": "md5"
}

SHA-512 of the empty string

{
  "text": "",
  "algorithm": "sha512"
}

Limitations

What a digest does and does not prove

A cryptographic digest maps any input to a fixed-size value. In practice it is used to detect content changes (compare the digest before and after) and as a building block inside HMAC, signatures and key-derivation functions.

It does not prove who sent a message, and a raw digest cannot withstand a determined attacker who can also modify the expected value. For authenticity, use a keyed construction such as HMAC over a shared secret, or a signature over a public key.

Where Web Crypto is used

Web Crypto provides SHA-1, SHA-256, SHA-384 and SHA-512 through crypto.subtle.digest, and this tool uses that implementation when the browser exposes it. It provides no MD5, so MD5 always uses the bundled implementation. Both paths are checked against the same known-answer vectors in the test suite.