How to use it
Use a digest to compare bytes and HMAC when two parties already share a secret authentication key.
- Choose Digest or HMAC, then select SHA-256, SHA-384, or SHA-512.
- Enter the message and, for HMAC only, a non-empty secret key.
- Generate the result and copy the exact hexadecimal or Base64 value.
Worked example
- Input
SHA-256 message: abc
- Output
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
The example is the standard SHA-256 digest of the UTF-8 bytes for “abc”.
Method and definitions
- The Web Crypto API processes UTF-8 message and key bytes using the selected secure-hash family member.
- HMAC mixes a secret key into the hash construction; a plain digest has no secret.
Limits and edge cases
- A fast SHA digest is not suitable for storing passwords and HMAC is not a digital signature.
- A digest verifies integrity only when the expected value comes through a trusted channel.
Privacy
All input and output stays in this tab. Rigula does not upload, store, or include it in a share URL.
Sources