JWT Verify & Build
Check signatures against an expected algorithm, inspect selected claims, and build tokens
- Confirm the algorithm matches the header.
- Verify you selected the correct key source.
- Make sure the key is the public key for RS256/ES256.
JWT verification checks whether a supplied key validates the token signature under the expected algorithm. This validator supports HS256, RS256, and ES256; checks numeric exp, nbf, and iat claims when present; and compares iss and aud when you provide expected values. Get the verification key from the expected issuer and set the issuer and audience your application accepts.
- Paste your token and select the correct algorithm.
- Provide a shared secret or public key (PEM/JWK/JWKS).
- Optionally set issuer and audience checks.
- Click Verify JWT to validate the signature and claims.
Use a known test token and secret to confirm your signing flow. If the signature fails, compare the algorithm, key source, and claims to the expected values from your identity provider.
- Algorithm mismatch between the header and the selected algorithm.
- Selecting an algorithm from untrusted token data instead of trusted application or issuer configuration.
- Using a shared secret for RS256/ES256 (these require a public key).
- Clock skew too strict for
expornbfvalidation.
# Verify HS256 with jsonwebtoken
npm install jsonwebtoken
node -e "const jwt=require('jsonwebtoken'); console.log(jwt.verify(process.env.TOKEN, process.env.SECRET));"Does this tool verify signatures?
Yes. It validates the signature and optional claims.
Can I use JWKS?
Yes. Enter an HTTPS JWKS URL and select the key by kid. Fetching makes a direct request from your browser to that host.
What does a passing result mean?
The signature matches the supplied key and algorithm, and the displayed claim checks passed. You still need a key from the expected issuer and application rules that decide what access the token allows.