JWT Time Claims
Inspect numeric exp, nbf, and iat claims against an explicit reference time, entirely in your browser.
This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.
Avoid live production secrets; use dummy or masked data where possible. Data handling details
| Claim | NumericDate (seconds) | UTC time | Status |
|---|
How it works
The supplied reference time makes the comparison reproducible. QuickKit defaults to a leeway of 0 seconds (exact comparison), which applies the RFC 7519 §4.1.4 and §4.1.5 rules as written: a token is expired once the reference time is equal to or later than exp, and valid once the reference time is equal to or later than nbf. RFC 7519 permits implementations to allow a small leeway for clock skew, usually no more than a few minutes; the optional leeway field models that and widens every comparison by the given number of seconds, including whether iat is judged to be in the future. The 3600-second maximum is QuickKit's own ceiling for diagnostic use, not a value RFC 7519 recommends. The result only compares decoded numeric claims; it does not verify the JWT signature, issuer, audience, or authenticity. Pasted JWTs are processed locally and never sent to a server.