What the result means
A JWT has three Base64URL parts separated by dots: header, payload, and signature. The header says how the token is signed (for example HS256 or RS256). The payload holds claims such as who issued the token, who it is for, and when it expires.
| Claim | Meaning |
|---|---|
| iss | Issuer: who created the token |
| sub | Subject: who the token is about |
| aud | Audience: who should accept it |
| exp | Expiry time, in Unix seconds |
| nbf | Not valid before this time |
| iat | Issued at |
| jti | Unique token ID |
Time claims are shown as readable dates and compared with your device clock to tell you whether the token has expired.
Example
A decoded payload:
{ "sub": "1234567890", "name": "Jane Doe", "iat": 1516239022, "exp": 1516242622 }
Here exp is one hour after iat, and the tool will report that this old token expired long ago.
Limits
- The signature is not verified. Only a server that holds the right key can verify it. Never trust decoded data just because it looks right.
- A token with the algorithm
noneis unsigned and must never be trusted. The tool warns about it. - Encrypted tokens (JWE, five parts) cannot be read, because their content is not Base64URL JSON.
- Expiry is judged by your device clock, which may be wrong.
FAQ
Is it safe to paste a real token here?
The token stays in your browser, but a live token is still a credential. Prefer a test or expired token, and never share real tokens in screenshots or chats.
Why can I read the payload without a key?
A signed JWT is encoded, not encrypted. Anyone holding the token can read it, so never put secrets in the payload.
What does Not verified mean?
It means the tool did not check that the token is authentic or unchanged. That check belongs on your server.