toolqik

45 · Keys & Auth

JWT Signature Verifier

Verify any JWT signature: HS, RS, PS, ES and EdDSA, with keys, certificates or a JWKS.

Runs in your browser
Clock tolerance
Header

  
Payload

  

About this tool

Decoding a JWT shows what it claims; verifying its signature proves who issued it and that nobody changed it. This verifier checks signatures for every standard algorithm, with the key in whatever form you have: a shared secret, a PEM public key, an X.509 certificate, a single JWK or a whole JWKS from an identity provider. It also checks the exp, nbf and iat times.

Verification uses your browser’s Web Crypto API. Tokens and keys are never sent anywhere.

Supported algorithms

algAlgorithmVerify with
HS256, HS384, HS512HMAC with SHA-2The shared secret
RS256, RS384, RS512RSA PKCS#1 v1.5RSA public key, certificate or JWK
PS256, PS384, PS512RSA-PSSRSA public key, certificate or JWK
ES256, ES384, ES512ECDSA on P-256, P-384, P-521EC public key, certificate or JWK
EdDSAEd25519Ed25519 public key or JWK

Verifying tokens from Auth0, Okta, Cognito, Google or Microsoft

  1. Open the provider’s JWKS URL, usually https://your-issuer/.well-known/jwks.json (listed as jwks_uri in /.well-known/openid-configuration).
  2. Paste the whole JWKS into the key box. The key whose kid matches the token header is used automatically.

Mistakes to avoid in your own code

  • Pin the algorithm. Tell your library which algorithms to accept. Trusting the token’s own alg header allows “alg: none” and RS256-to-HS256 confusion attacks.
  • Check the claims too: a valid signature doesn’t mean the token is for you. Verify iss, aud and exp.
  • Cache JWKS and refresh on unknown kid, so key rotation works without downtime.

To create signed tokens, use the JWT Generator; to inspect one, the JWT Decoder.

FAQ

How do I verify a JWT signature?

Paste the token and the key: the secret for HS algorithms, or the issuer’s public key, certificate, JWK or JWKS for RS, PS, ES and EdDSA. The result appears instantly.

Where do I find the public key for a JWT?

Most identity providers publish a JWKS at /.well-known/jwks.json. Paste the whole JWKS and the key matching the token’s kid is used.

Why does my RS256 token fail with the right key?

Common causes: the token was modified (even whitespace), you pasted a different environment’s key, or the key is in an unexpected format. Paste the issuer’s JWKS to rule out key mismatches.

Does it check expiry?

Yes. exp, nbf and iat are checked against your clock with the tolerance you choose, and shown below the result.

Can I paste a private key?

You don’t need to: verification only uses the public key. The tool refuses private keys to remind you not to share them.

esc
↑↓ navigate↵ open