JWT Signature Validator (RS / PS / ES / EdDSA / HS)
Verifies a JWT signature against a public key (PEM, certificate), JWK, JWKS selected by kid, or an HMAC secret. It supports RS, PS, ES, EdDSA and HS algorithms, decodes the token and checks exp, nbf and iat.
Use the tool
Why this tool exists
When a service rejects a token, the question is always the same: is the signature wrong, the key wrong, the algorithm wrong, or has the token simply expired? Decoding a JWT only shows the claims, which anyone can read, and says nothing about whether it is genuine. This tool checks the signature itself against the key you provide, for RS256, PS256, ES256, EdDSA, HS256 and their relatives, and picks the right key from a JWKS by kid. It also checks time claims, rejects algorithm "none" and blocks the classic trick of verifying an HS256 token with a public key. Use test tokens and public keys where you can. Verification runs in your browser.
How to use it
- Paste the JWT into the first box.
- Paste the public key (PEM, certificate, JWK or JWKS) or the HMAC secret into the second box.
- Leave the algorithm on "from token header" or force one, then read the verification result and the time-claim checks.
Frequently asked questions
What key formats are accepted?
PEM public keys (SPKI or PKCS1), X.509 certificates, a single JWK, a JWKS (matched by kid) or an HMAC secret for HS algorithms.
Why does it block some algorithm combinations?
To prevent algorithm confusion: verifying an HS256 token with an RSA public key as the secret would accept forged tokens. The tool refuses it, and flags alg "none".
What claims are checked?
exp, nbf and iat are compared with the current time, or with the Unix time you enter. Other claims such as issuer and audience are shown but not enforced.
Is it safe to paste a real token?
Verification is local and nothing is uploaded. Still, tokens and secrets are sensitive: prefer test tokens, and never share an HMAC secret from production.