ToolsDashboard

check jwt expiration

Check whether a JWT is expired or not yet valid

Inspect exp, nbf, and iat claims quickly so you can confirm whether auth failures come from token timing issues.

A token that looks structurally fine can still fail because its time claims do not line up with the current clock. This is one of the most common JWT debugging workflows.

Open the tool Expected result

How to use it

Step 1

Decode the token payload

Review the raw timestamp claims without assuming they are already valid.

Step 2

Convert the claim values

Use the parser and timestamp context to see when the token should start and stop working.

Step 3

Compare against the verifier clock

Check whether skew, timezone assumptions, or stale tokens explain the failure.

Sample input

eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE3MTEwMjcyMDB9.signature

Expected result

You can distinguish a timing problem from a key, issuer, or audience issue much faster.

Common mistakes

Reading exp as local time without converting it.
Ignoring nbf when a token is rejected immediately after issuance.
Forgetting that server clock skew can invalidate otherwise correct tokens.

Related workflows

Inspect custom JWT claims before changing auth rules

Guide

Debug a bearer token copied from a failed API request

Guide

Related tools

ToolsDashboard

check jwt expiration

Check whether a JWT is expired or not yet valid

Inspect exp, nbf, and iat claims quickly so you can confirm whether auth failures come from token timing issues.

A token that looks structurally fine can still fail because its time claims do not line up with the current clock. This is one of the most common JWT debugging workflows.

Open the tool Expected result

How to use it

Step 1

Decode the token payload

Review the raw timestamp claims without assuming they are already valid.

Step 2

Convert the claim values

Use the parser and timestamp context to see when the token should start and stop working.

Step 3

Compare against the verifier clock

Check whether skew, timezone assumptions, or stale tokens explain the failure.

Sample input

eyJhbGciOiJIUzI1NiJ9.eyJleHAiOjE3MTEwMjcyMDB9.signature

Expected result

You can distinguish a timing problem from a key, issuer, or audience issue much faster.

Common mistakes

Reading exp as local time without converting it.
Ignoring nbf when a token is rejected immediately after issuance.
Forgetting that server clock skew can invalidate otherwise correct tokens.

Related workflows

Inspect custom JWT claims before changing auth rules

Guide

Debug a bearer token copied from a failed API request

Guide

Related tools