JWT iat in the Future – Inspect a Future Issued-At Timestamp

Local only

Inspect a numeric iat value that points to a future time without treating decoding as claim validation.

90 chars · 1 line

118 chars · 10 lines

Algorithm: HS256Signature not verifiedTime status: Not evaluated (no numeric exp/nbf)Issued in future: 2033-05-18T03:33:20.000Z

JWT time-claim troubleshooting

What a JWT issued-at time in the future means

A future iat value is still a finite NumericDate, so the decoder formats and displays it instead of returning a parsing error. Whether the token should be rejected for clock skew or inconsistent issuance time belongs to the verifier policy. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • Browser-local JWT decoding
  • Strict three-segment validation
  • Canonical Base64URL checks
  • Header and payload JSON validation
  • Expiration status details
  • No signature verification claims

Steps

  1. Read the numeric iat claim and its ISO Issued detail.
  2. Compare the timestamp with the issuer and verifier clocks.
  3. Check for milliseconds-versus-seconds mistakes before changing clock-skew policy.

The decoder displays iat but does not enforce clock policy

Local decoding can show the timestamp encoded in the token. It cannot decide how much future skew your authentication system permits because that rule belongs to the trusted verifier.

Future iat example

The claim is a valid number and therefore produces an Issued in future timestamp.

Payload claim

"iat":2000000000

Decoder detail

Issued in future: 2033-05-18T03:33:20.000Z

Common questions

Frequently asked questions

Will this decoder reject a future iat?

No. It displays valid NumericDate values but does not enforce application clock-skew policy.

Can clock skew cause a small future iat?

Yes. Compare trusted system clocks before assuming the token generator is broken.

Can a unit bug cause a much larger future date?

Yes. Milliseconds placed into a seconds-based NumericDate are a common cause of extremely distant dates.

Recommended next steps

JWT exp in MillisecondsSpot an exp timestamp that used milliseconds where JWT NumericDate expects seconds.JWT exp Before iatTroubleshoot contradictory NumericDate claims where expiration precedes issuance.Unix Timestamp Converter OnlineConvert iat and exp NumericDate values to readable UTC timestamps.

Debugging a specific JWT issue? Browse JWT troubleshooting.