How to use JWS Signature Verifier
- Paste the compact three-part JWS or select its UTF-8 token file. A selected file replaces the pasted token.
- Supply a public JWK or JWKS you trust independently and choose the expected RS256 or ES256 algorithm. A multi-key set needs an unambiguous matching kid.
- Set the review time and clock tolerance for exp/nbf observations. The example time is fixed in 2033; leave Review time blank to use this browser’s current time.
- Enter the expected issuer and audience, or leave each blank to skip that check. Run Verify JWS.
- Read signature validity separately from the claim observations. An invalid signature leaves the payload unauthenticated; a valid one still does not establish an identity or prevent replay.
Example: JWS Signature Verifier
Verify the supplied ES256 demo token and claims at the fixed example review time in May 2033.
Options
- Local UTF-8 token file (optional)
- Up to 256 KiB; selected file replaces the pasted token. Public data only.
- Compact JWS
- The three dot-separated parts: protected header, payload and signature. RS256 and ES256 are supported. A token that declares "none", an HMAC algorithm, "crit" or "b64":false is refused.
- Trusted public JWK (supplied separately)
- Paste the public key you already trust, as a JWK or a JWKS. The key is never taken from the token, and embedded keys (jwk, jku, x5u) are refused.
- Expected algorithm
- The algorithm you require. It must match the token header and, when the key declares one, the key "alg". A mismatch is refused rather than tried.
- Review time (UTC)
- The instant used for exp and nbf checks, written as YYYY-MM-DDTHH:MM:SSZ. Leave it blank to use the current time in this browser.
- Clock tolerance (seconds)
- A whole number of seconds added to both sides of exp and nbf checks, for tokens issued or read by a clock that is slightly off. From 0 to 300 seconds. Zero means an exact comparison.
- Expected issuer (optional)
- The exact "iss" value you require. Leave it blank to skip the issuer check.
- Expected audience (optional)
- The exact "aud" value or a value inside an "aud" array. Leave it blank to skip the audience check.
Supported inputs and limits
- Compact JWS with supported RS256/ES256 public keys only.
- A selected UTF-8 token file, up to 256 KiB, replaces pasted text.
- Unsigned tokens, HMAC algorithms, crit, b64:false and embedded-key trust are refused.
- No signing, remote key lookup, complete JWT policy validation, replay prevention or identity-provider trust check is provided.
- Issuer, audience and time observations follow the supplied policy and remain separate from signature validity.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Signature and claims answer different questions
A matching signature shows that the exact signing bytes verify against the supplied key. You must establish why that key is trusted. Issuer, audience and time observations are separate checks under your entered policy; a signature alone does not authenticate a person or prevent token replay.
Questions about JWS Signature Verifier
Does a matching signature prove identity?
Only the cryptographic match against your supplied key is checked. Identity and application authorization require independently established trust and policy.
Can it verify an unsigned or HMAC token?
No. This verifier accepts only its supported public-key signature algorithms and refuses unsigned or shared-secret modes.
Are token URLs fetched?
No. The page does not discover keys or contact an issuer. Supply the public key separately.