Webhook signature checker

Check a GitHub or Stripe webhook signature with the signing secret, without contacting either.

Runs in your browser. Your input is not uploaded.

Correctness last checked 2026-11-13. How we verify

Loading the tool…

What it does, how to use it, and questions

What it does

GitHub and Stripe sign webhook bodies with HMAC-SHA256 and a secret only you and they know. GitHub sends X-Hub-Signature-256: sha256= plus the hex of the raw body. Stripe sends Stripe-Signature with a timestamp and signs timestamp.body.

This page repeats that calculation. A match means this secret and this body produce that header. It does not contact GitHub or Stripe, and it does not prove the request arrived from them.

How to use it

  1. Choose GitHub, Stripe, or a plain HMAC-SHA256.
  2. Paste the signing secret and the raw request body. Do not reformat the JSON.
  3. Paste the signature header and check.

Example: GitHub, secret topsecret

Input
{"id":1}
Output
sha256=da3557bb01e9adb585273452a18d40553fcd71fd1aeeae35eb30c81a7b082850

Things to watch for

  • Pretty-printing the body changes the bytes and the signature will not match.
  • Stripe signs the timestamp, a dot, then the body. Checking the body alone will fail.
  • A matching signature with an old timestamp can be a replay. The tool reports the age; your server should reject timestamps outside a few minutes.

Questions

Does a match mean GitHub sent it?
It means this secret and this body produce that header. Anyone with the secret could have made it. The check does not call GitHub or Stripe.
Which GitHub header do I paste?
X-Hub-Signature-256. The older X-Hub-Signature is SHA-1 and this tool tells you to use the SHA-256 header instead.
Why does my Stripe signature fail?
The signed text is the t= value, a dot, then the raw body. A mismatch usually means the body was parsed and serialised again.
Is the secret uploaded?
No. The HMAC is computed in this page.