About this tool
Signed webhooks include a timestamp so receivers can reject old, replayed requests. When you craft test requests or debug a “timestamp outside the tolerance zone” error, you need the current time in exactly the right format. This page shows it live in each common header format, and checks any timestamp you paste against a tolerance window.
Formats
- Unix seconds (10 digits): Stripe’s
t=, Slack’sX-Slack-Request-Timestampand Standard Webhooks’webhook-timestamp. - Unix milliseconds (13 digits): JavaScript’s
Date.now(); some APIs use it. - ISO 8601: event bodies such as GitHub’s
timestampfields.
Replay protection
A receiver should reject a webhook if its signed timestamp is more than a few minutes from the server’s clock, even when the signature is valid. Otherwise an attacker who captures one request can resend it forever. Five minutes is the usual window. If valid events are rejected, check that your server syncs its clock with NTP.
// Node.js
const age = Math.abs(Date.now() / 1000 - Number(timestamp));
if (age > 300) return res.status(400).send('Timestamp outside tolerance');
FAQ
What timestamp format do webhook signatures use?
Usually Unix time in seconds, such as 1731744000. Stripe puts it in the Stripe-Signature header as t=…; Slack and Standard Webhooks send it in its own header.
What tolerance should my webhook handler allow?
Five minutes (300 seconds) is the common default. Use a shorter window only if your servers’ clocks are reliably synchronised.
Why does my webhook say the timestamp is too old?
The event was delayed or replayed, or your server’s clock is wrong. Compare your server time with the current time shown here.