JWT contents are not necessarily encrypted
Typical JWT headers and payloads are Base64URL-encoded, which is an encoding rather than a secrecy mechanism. Treat the claims as readable by anyone who obtains the token.
FREE WEB TOOL
Decode JWT header and payload locally and optionally verify HMAC signatures for HS256, HS384, or HS512.
With a shared secret, HS256 / HS384 / HS512 HMAC signatures can be checked. Public-key algorithms are not verified here.
Decode the JWT header and payload locally. When needed, you can also check HS256 / HS384 / HS512 HMAC signatures with a shared secret.
For inspection work, prefer test tokens and test secrets rather than pasting a production shared secret into a web page.
admin: true, and this tool can show it. That alone does not prove that a trusted issuer signed the token or that it has not been modified.Authenticity requires separate verification of the signature, algorithm, key material and expected issuer/audience rules.
Typical JWT headers and payloads are Base64URL-encoded, which is an encoding rather than a secrecy mechanism. Treat the claims as readable by anyone who obtains the token.
When you provide a shared secret, this page can verify HS256 / HS384 / HS512 HMAC signatures. Public-key algorithms such as RS / ES / PS are not verified here.
exp commonly marks expiration and nbf the “not before” time. The helper can compare them with the current time, but the receiving application still decides how those claims are enforced.
iss identifies the issuer and aud the intended audience. Even a correctly signed token can be rejected when those values do not match what the application expects.