Unix timestamp converter
By the HookWatcher team · Updated
Unix seconds, milliseconds or microseconds, or a date such as 2026-11-15T07:00:00Z.
Read as seconds UTC (ISO 8601) 2025-11-15T07:00:00.000Z Unix seconds 1763190000 Unix millis 1763190000000
Seconds, milliseconds or microseconds?
The tool decides by size: values below 10¹¹ are read as seconds, below 10¹⁴ as milliseconds, below 10¹⁷ as microseconds, larger as nanoseconds (Go's UnixNano). Webhook providers mostly use seconds (Stripe's created and t=, Slack's X-Slack-Request-Timestamp, Standard Webhooks' webhook-timestamp); JavaScript's Date.now() is milliseconds. GitHub payloads mostly use ISO 8601 strings, but push events carry the repository's created_at and pushed_at as Unix seconds. A date and time without Z or an offset is read in your browser's time zone.
Tolerance and replay protection
Providers that sign a timestamp expect you to reject requests whose timestamp is too far from your clock, so a captured request can't be replayed later. Stripe's official libraries use a default tolerance of 300 seconds; Slack recommends rejecting requests more than five minutes old. If valid requests fail this check, look at your server's clock (NTP) before your code.
const t = Number(req.get("X-Slack-Request-Timestamp"));
if (Math.abs(Date.now() / 1000 - t) > 300) return res.status(401).send("stale request");Check timestamps on real deliveries