Webhook HMAC Signer
Sign and verify GitHub, Stripe, and Slack webhook signatures locally.
OpenAnswer "is this token still good?" in seconds, with the exact time remaining.
Drop in the full JWT string.
iat, nbf and exp appear with UTC timestamps.
See seconds left or seconds since expiry.
Copy or download the lines for a ticket.
A user reports being logged out every few minutes, and support forwards one of their tokens. The quickest first check is whether the token's lifetime is what the configuration says it should be, and whether it had already expired when the request failed.
Paste a token and the checker decodes the payload and lists the time claims it finds. Each of iat, nbf and exp is shown as the raw Unix value and as an ISO 8601 timestamp in UTC. If there is an exp claim, a final line says how many seconds remain or how many seconds ago it expired, measured against your computer's clock. If there is none, it says so, which is worth raising on its own. The report updates as you type and can be copied or downloaded.
Read the times together. The gap between iat and exp is the lifetime the issuer configured, so an exp 300 seconds after iat means five-minute tokens. If a token looks expired to you but works on the server, or the reverse, compare the two clocks, since a skew of even a minute matters for short-lived tokens. The checker does not judge nbf, so look at it yourself when a brand-new token is rejected. For the full header and claim set, open the JWT claims viewer, and to translate other epoch values, use the Unix timestamp converter.
The token is decoded inside your browser and never sent to a server.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The exp value was probably written in milliseconds instead of seconds. JWT time claims are defined in seconds, so the issuer needs fixing; verifiers will treat that token as practically never expiring.
Your device clock. If your computer is a few minutes off, the countdown is too, so compare against a reliable time source when the margin is small.
No. It reads the payload only. A forged token with a generous exp looks healthy here, so check the signature separately.