JWT Verifier (HS256/384/512)

Paste a JWT and its secret to find out whether the signature is valid. The tool also checks the exp and nbf claims and lists all token times.

Use the tool

Why this tool exists

The classic debugging question is "is my secret wrong, or is the token wrong?". A 401 gives no detail. Verifying the signature by hand means recomputing an HMAC over the first two parts and comparing it with the third, which is tedious and easy to get slightly wrong.

This verifier does exactly that. It reads the algorithm from the header, recomputes the signature with your secret, compares it in a way that looks at every character, and reports valid or invalid. It also flags an expired or not-yet-valid token. It runs in your browser, so the secret is not uploaded. Use test secrets when you can.

How to use it

  1. Paste the JWT into the first box.
  2. Enter the shared secret in the second box.
  3. Run the check and read the verdict: valid or invalid signature.
  4. Review the notes on expiry and not-before, and the list of token times.

Frequently asked questions

Which algorithms can it verify?

HS256, HS384 and HS512 only. A token declaring "none" is never accepted, and RS256, ES256 and other asymmetric algorithms are reported as unsupported, since they require a public key.

What does an invalid signature mean?

Either the secret is wrong, or the token was changed after signing, or it was signed with a different algorithm or key. Check for whitespace around the secret and whether the secret is Base64 encoded in your system.

Does a valid signature mean I should trust the token?

It means the token was signed with that secret and not altered. Your server must also check the issuer, audience and expiry. This page checks exp and nbf only.

Is it safe to enter my secret?

The check runs in your browser and nothing is sent anywhere. Still, treat real signing secrets carefully, use test values while debugging, and rotate any secret you pasted into an untrusted page.