HMAC-SHA256 Generator
About
HMAC turns a hash into a message authentication code: the key is mixed into the hashing in a specific two-pad construction (RFC 2104) that resists the length-extension attacks plain hash(key + message) suffers. HMAC-SHA256 is how webhooks prove they came from Stripe/GitHub, how AWS Signature Version 4 authenticates API calls, and how JWTs are signed with HS256. Verification means recomputing the MAC over the received message with the shared secret and comparing in constant time — if you are verifying in code, use a timing-safe comparison, never ==, and never this web page with a production secret you would not type into your own browser anyway.
Frequently Asked Questions
HMAC vs a plain SHA-256 of key + message?
Plain prefix hashing is vulnerable to length extension; HMAC's construction is provably secure as a MAC assuming the hash is a PRF — that is why protocols standardized it.
Is the output a signature?
It is a MAC: anyone with the key can produce it, so it proves authenticity between key-holders but not non-repudiation like a public-key signature.