Do not compare strings naively
Verification here delegates the cryptographic tag comparison to Web Crypto's HMAC verify operation after strict decoding and length checks.
Verify HMAC tags without sending secrets anywhere. Decode common signature formats, use the browser's cryptographic verify primitive, inspect exact message/key bytes, parse webhook-style signature headers, check timestamp freshness, and batch-check known message/signature pairs with one shared secret.
Paste a comma-separated header such as t=1710000000,v1=.... This lab does not assume any vendor's protocol; you choose which component is the signature and how the signed string is assembled.
One pair per line, separated by a TAB. Uses the selected algorithm, secret and signature encoding from the main verifier. Maximum 1,000 rows.
Verification here delegates the cryptographic tag comparison to Web Crypto's HMAC verify operation after strict decoding and length checks.
Webhook systems frequently sign the exact received bytes. Re-serializing JSON can change whitespace or key ordering and invalidate the signature.
A valid HMAC can still be replayed. If your protocol includes a timestamp, enforce the provider's allowed age and idempotency rules.
Use unique secrets per integration, rotate them safely, and never paste production secrets into third-party web tools. This tool runs locally in your browser.