A JSON Web Token (JWT) is a compact, signed token that apps use to prove who you are, for example after you log in. It has three Base64URL parts separated by dots: a header, a payload of claims, and a signature.
Decoding vs verifying
Decoding only reads the header and payload, which are not encrypted. Anyone holding the token can read them, so a JWT payload must never hold passwords or other secrets.
Verifying checks the signature with the right key. Only verification proves the token is genuine and unchanged. This tool decodes. Your server must always verify.
What we flag
alg: none: an unsigned token. Servers that accept these can be fooled by anyone.- No signature: the third part is empty.
- Expired or not yet valid: based on the
expandnbfclaims. - No expiry: a token without
expworks forever if stolen. - Long lifetime: more than 30 days between
iatandexp. - Sensitive-looking fields: claim names like password, secret or card.
Standard claims
| Claim | Meaning |
|---|---|
iss | Who issued the token |
sub | Who it is about, usually a user ID |
aud | Who it is meant for |
exp | Expiry time (Unix seconds) |
nbf | Not valid before |
iat | Issued at |
jti | Unique token ID |
JWT security checklist for developers
- Pin the algorithms your server accepts. Never let the token's header choose freely.
- Always check
exp,issandaud. - Keep access tokens short-lived (minutes, not days) and use refresh tokens.
- Use strong keys: at least 256 random bits for HS256, or RS256/ES256 key pairs.
Each JWT part is Base64URL. To decode a single part on its own, use the Base64 decoder.
Frequently asked questions
Can anyone read a JWT?
Yes. The header and payload are only Base64URL-encoded. Do not put secrets in them. Use JWE if the contents must be encrypted.
Does this tool verify the signature?
No. It decodes and flags risky settings. Verify signatures on your server with the correct key.
What does alg none mean?
It marks an unsigned token. A server that accepts it will trust any claims an attacker writes.
Is my token sent to a server?
No. Decoding happens in your browser.