Inspect a JWT and spot the weak points
Paste a token to read its header and claims and see common security problems. Everything runs in your browser: the token is never uploaded or stored. We only count anonymous visits (no cookies, no IP).
Use test or expired tokens. A live access token is a credential: do not paste production tokens into any website, including this one.
This tool decodes only. It does not verify the signature, so a clean result does not mean the token is genuine. Verification needs the issuer's key and belongs on the server.
How to use this tool
- Copy the token from your test request. It can include the word "Bearer".
- Paste it in the box and press Inspect (or try the example).
- Read the findings first, then the decoded header and payload.
Example
Press "Try an example": the sample token uses HS256, has no issuer or audience and a long lifetime, so you see how each weakness is reported. In your own tokens look especially at alg, exp, iss and aud.
Limits
This tool only decodes. It does not verify the signature, so it cannot tell you whether a token is genuine. Verification needs the issuer's key and belongs on the server.
Privacy and security of what you enter
The token is decoded in your browser and is not sent to us or stored. A live access token is a credential, though: do not paste production tokens into any website. If you did, revoke the token or sign out of that session. See the privacy notice.
We review OAuth2/JWT setups, gateways and scopes. See the security review or WSO2 services.
Message us on LinkedIn