Webhook Replay Diff Lab
Compare webhook payload timelines, re-check HMAC digests, and spot idempotency gaps locally.
OpenReproduce a provider's webhook signature locally and find out exactly why yours does not match.
Add the raw request body exactly as your provider sent it.
Use your GitHub, Stripe, Slack, or generic HMAC secret.
Compute the signature locally with Web Crypto - nothing is uploaded.
Copy the signed header or confirm a pasted signature matches.
Your Stripe endpoint returns 400 on every event, the logs say no signature matched, and the secret looks right. The fastest way forward is to take one captured body, sign it yourself the way Stripe does, and compare the result with the header you received.
Choose a provider and the tool applies its signing rule. GitHub signs the raw body and sends sha256= plus a hex digest in X-Hub-Signature-256. Stripe signs the timestamp, a dot and the body, then sends t=…,v1=… in Stripe-Signature. Slack signs v0:timestamp:body and sends v0= in X-Slack-Signature, and Generic is plain HMAC-SHA256 over the body. In Sign mode you get the exact signed string, hex and base64 digests and the finished header value. Leave the timestamp empty for Stripe or Slack and the current Unix time is filled in, or press Now.
Verify mode is where the tool earns its keep. Paste the signature you received, and if it does not match, the body is re-signed in several variants: with and without a trailing newline, trimmed, with CRLF and LF swapped, as minified or pretty-printed JSON, and under the other providers' rules. When a variant matches, the tool names it, which nearly always points at middleware that parsed and re-serialized the body. The step-by-step guide to verifying webhook signatures covers the receiving code, checking signatures without a cloud service explains the workflow, and for a plain keyed hash of any text the HMAC generator is simpler.
Signing runs through the Web Crypto API in this tab, and the secret field stays masked unless you tick Show secret.
Keyboard shortcut
Reproduce X-Hub-Signature-256 style checks offline.
Sign t=…,v1=… style payloads while building handlers.
Verify v0 signatures with timestamp + body locally.
Answers for this tool. For site-wide help, open the FAQ hub.
The t value from the Stripe-Signature header you received, not the current time. Paste the whole header into the signature box and copy the number after t= into the timestamp field before verifying.
No. Only HMAC-SHA256 is computed. GitHub still sends a legacy SHA-1 header for compatibility, but the SHA-256 header is the one you should verify.
Your digest matched the base64 form rather than hex. Some in-house senders encode that way. The signature is genuine, but confirm which encoding your receiver expects so production code compares like with like.