Skip to content

Webhook signature checker

Compute an HMAC over a payload, or check a request's signature the way its provider signs it. Everything is computed in your browser.

A plain HMAC of the payload. Pick a provider to check a request the way it signs.

The request body exactly as it was received. Every space and line break is signed.

optional

Paste the signature a request carried to see whether it matches. A label such as sha256= in front is fine.

Computed in your browser. Nothing is sent.

A signing secret is a credential. This tool makes no request with it: the signature is computed on this page, and nothing you type reaches webhooks.cc or is stored.

How webhook signatures work

A provider and your server share a secret. When the provider sends a webhook, it computes an HMAC, a keyed hash, over the request body (some add a timestamp or a message id) and puts the result in a header. Your server computes the same HMAC over the body it received and compares the two. If they are equal, the request came from someone who holds the secret and the body was not changed on the way.

The comparison is over exact bytes. One added space or a re-ordered key gives a different signature, which is why the check must run on the raw body, before any JSON parsing. Compare in constant time in your own code, and where the scheme signs a timestamp, refuse requests that are too old.

Provider presets

Each preset checks a request the way that provider signs it: what goes into the signed text, how the secret is decoded, and how the header is written. They are the same checks the webhooks.cc SDK and dashboard run. Sign this payload does the reverse and shows the headers the provider would send.

ProviderSignature headerAlgorithm
Bitbucketx-hub-signatureHMAC-SHA256
Cal.comx-cal-signature-256HMAC-SHA256
Calendlycalendly-webhook-signatureHMAC-SHA256
Clerkwebhook-signatureHMAC-SHA256
Coinbase Commercex-cc-webhook-signatureHMAC-SHA256
DocuSignx-docusign-signature-1HMAC-SHA256
GitHubx-hub-signature-256HMAC-SHA256
Intercomx-hub-signatureHMAC-SHA1
Lemon Squeezyx-signatureHMAC-SHA256
Linearlinear-signatureHMAC-SHA256
Metax-hub-signature-256HMAC-SHA256
Muxmux-signatureHMAC-SHA256
Paddlepaddle-signatureHMAC-SHA256
Razorpayx-razorpay-signatureHMAC-SHA256
Resendsvix-signatureHMAC-SHA256
Sentrysentry-hook-signatureHMAC-SHA256
Shopifyx-shopify-hmac-sha256HMAC-SHA256
Slackx-slack-signatureHMAC-SHA256
Squarex-square-hmacsha256-signatureHMAC-SHA256, over the URL and the body
Standard Webhookswebhook-signatureHMAC-SHA256
Stripestripe-signatureHMAC-SHA256
Twiliox-twilio-signatureHMAC-SHA1, over the URL and the body
Typeformtypeform-signatureHMAC-SHA256
Vercelx-vercel-signatureHMAC-SHA1
WorkOSworkos-signatureHMAC-SHA256

Custom HMAC

For a provider without a preset, Custom HMAC computes a plain HMAC of the payload with SHA-256, SHA-1, SHA-384 or SHA-512 and writes it as hex, Base64 or Base64url. Most secrets are text; choose Hex or Base64 under Secret is written as when the provider hands the key out in that form and its documentation says to decode it first.

Paste a signature under Signature to compare and the tool says whether it is the one computed. A label in front of the value, such as sha256=, is ignored, and hex is compared without regard to case.

Webhook signature questions

Check every delivery, not one by hand

Add the signing secret to a webhooks.cc endpoint and every request it captures is marked valid or invalid as it arrives, with the headers and raw body beside it. The same checks are in the TypeScript, Python and Go SDKs for your handler and your tests.

More free tools