JWT decoder
Paste a JSON Web Token to read its header, its claims and its expiry. The decoding is base64url to JSON and runs in your browser; the token is never sent anywhere. The signature is not verified, because verifying it needs the issuer's key, and a tool that claimed to verify without one would be guessing.
What a JWT is, in one paragraph
A JSON Web Token (RFC 7519) is three base64url strings joined by dots: a header that names the signing algorithm, a payload of claims, and a signature over the first two. Anyone can read the first two parts; only the holder of the key can produce the third. So a token is a statement that can be checked, not a secret: pasting one into a page that sends it to a server would leak a credential, which is why this tool keeps the token in your browser.
The checks a reviewer makes by eye
- alg:
nonemeans unsigned; a verifier must reject it.HS256is symmetric, so every verifier holds the signing secret;RS256andES256let verifiers hold only the public key. - exp, nbf and iat are seconds since 1970; this page converts them and says how far away each is. A token with no
expcan only be ended by revocation. - aud says which API may accept the token. Without it, any service that trusts the issuer accepts it.
- jku or x5u in the header names a URL to fetch keys from. A verifier that follows it blindly can be told to fetch the attacker's key.
- A token's claims say what the issuer asserted, not what the server will do with it. An API test still has to send the token and read the response.