JWT Expiry Checker is designed for the exact search intent behind “jwt expiration checker”. Inspect a JWT's expiration claim and determine whether the exp time has passed, based on the decoded payload supported by the tool. Inspect a JWT's expiration claim and determine whether the exp time has passed, based on the decoded payload supported by the tool. What the exp claim means JWT exp is a NumericDate: the number of seconds since the Unix epoch. A token should not be accepted on or after its expiration time, subject to small implementation-specific clock-skew allowances. Decoding is not verification Reading a JWT payload does not prove its signature is valid or that the token came from a trusted issuer. Expiry is only one validation check. Other claims matter Real token validation can also involve nbf , iat , issuer, audience, algorithm and signature verification. Worked example: If exp represents an instant earlier than the current validation time, the token is expired even if its header and payload can still be decoded. Common practical uses include Debug authentication tokens; Translate exp to a readable time; Check whether a token is already expired; Inspect expiry during API development. Important limitations: The checker must not be treated as signature verification unless it explicitly verifies a trusted signature. Clock skew can affect boundary cases. Sensitive production tokens should be handled according to your security policy. Key questions this page should answer include: What is exp in a JWT? It is the expiration-time claim expressed as a NumericDate in seconds since the Unix epoch. Can an expired JWT still be decoded? Yes. Expiration affects acceptance, not whether the base64url-encoded payload can be read. Does checking exp verify the JWT signature? No. Decoding and expiry checking are separate from cryptographic signature verification. What happens exactly at the exp time? A conforming validator should not accept the token on or after its expiration time, subject to allowed clock skew. What is the difference between exp and nbf? exp sets the expiration boundary; nbf indicates a time before which the token should not be accepted. The page should stay focused on this differentiator: Make the security boundary explicit: expiry inspection is not JWT trust/signature verification.
How to use this tool
What the exp claim means
JWT exp is a NumericDate: the number of seconds since the Unix epoch. A token should not be accepted on or after its expiration time, subject to small implementation-specific clock-skew allowances.
Decoding is not verification
Reading a JWT payload does not prove its signature is valid or that the token came from a trusted issuer. Expiry is only one validation check.
Other claims matter
Real token validation can also involve nbf, iat, issuer, audience, algorithm and signature verification.
Examples
Expiration concept
If exp represents an instant earlier than the current validation time, the token is expired even if its header and payload can still be decoded.
Common use cases
- Debug authentication tokens
- Translate exp to a readable time
- Check whether a token is already expired
- Inspect expiry during API development
Frequently asked questions
What is exp in a JWT?
It is the expiration-time claim expressed as a NumericDate in seconds since the Unix epoch.
Can an expired JWT still be decoded?
Yes. Expiration affects acceptance, not whether the base64url-encoded payload can be read.
Does checking exp verify the JWT signature?
No. Decoding and expiry checking are separate from cryptographic signature verification.
What happens exactly at the exp time?
A conforming validator should not accept the token on or after its expiration time, subject to allowed clock skew.
What is the difference between exp and nbf?
exp sets the expiration boundary; nbf indicates a time before which the token should not be accepted.