JWT Signature Verifier

Verify JSON Web Token signatures using HMAC secret keys or RSA public keys.

Key type:
0 chars

Enter a JWT and key, then click Verify

About JWT Signature Verifier — Detailed Guide

The JSON Web Token signature verifier helps developers diagnose authentication anomalies and prevent token forgery. It dissects the three-part JWT structure (Header, Payload, and Signature), clearly displays all contained claims, and validates the mathematical authenticity of the cryptographic signature using either a shared symmetric secret or an asymmetric public key.

The tool supports HMAC verification for HS256, HS384, and HS512, as well as RSA public-key verification for RS256, RS384, and RS512. It automatically validates exp (expiration time) and nbf (not before) claims, clearly distinguishing between invalid signatures, expired tokens, and prematurely presented tokens to accelerate API debugging.

#jwt #verify #signature #hmac #rsa #token

Key Features & Capabilities

  • Supports signature verification for HS256/384/512 (symmetric HMAC) and RS256/384/512 (asymmetric RSA)
  • Three-part visual decomposition clearly rendering Header JSON and Payload Claims
  • Automated timestamp validation for exp (expiration) and nbf (not-before) claims with live status badges
  • Purely client-side cryptographic verification keeping production tokens and secrets offline

How to Use

  1. 1

    Paste your full dot-separated three-part JWT string into the input area.

  2. 2

    Enter your HMAC shared secret or paste your RSA public key PEM matching the token algorithm.

  3. 3

    Click Verify to evaluate the signature authenticity and inspect decoded claims and validity dates.

Common Use Cases

  • → Debugging 401 Unauthorized API responses to determine whether tokens are expired or improperly signed
  • → Verifying that microservices have configured the correct RSA public key to validate auth server tokens
  • → Inspecting OpenID Connect ID Tokens returned by identity providers (Google, Okta, Auth0)

Related Tools

Frequently Asked Questions & Privacy

Why can I read the token payload even without supplying a secret key?

JWT headers and payloads are only Base64URL-encoded, not encrypted. Anyone can decode and read them; the secret key is strictly required to verify the signature and prove that the claims have not been tampered with.

What are the most common causes of signature verification failure?

Typical culprits include trailing whitespace in the secret key, mismatched algorithms (e.g., verifying an RS256 token as HS256), incomplete token copying, or using an outdated public key.