JWT Security 101: How to Decode, Inspect, and Verify Claims Client-Side

Fri, 04 Sep 2026 00:00:00 +0000

Free In-Browser Tool TOOLBOX UTILITY

JWT Token Inspector & Decoder

Analyze JWT expiration, token issuance, audience, and signature algorithms locally with real-time expiration count-downs.

Inspect JWT Token Safely →

What Is a JSON Web Token (JWT)?

Defined by RFC 7519, a JSON Web Token is an open, compact, URL-safe container for transferring claims between two parties. JWTs are the dominant authentication mechanism in modern single-page applications (SPAs), microservice architectures, and OAuth 2.0 / OpenID Connect (OIDC) workflows.

A JWT consists of three distinct parts separated by dots (.):

Header.Payload.Signature

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyLCJleHAiOjE3MDAwMDAwMDB9.4pz-KE...

The Three Components of a JWT

1. The Header

The header describes the cryptographic metadata and token type:

{
 "alg": "HS256",
 "typ": "JWT"
}

alg: The cryptographic signing algorithm (e.g., HS256, RS256, ES256).
typ: Token type, typically "JWT".

2. The Payload (Claims)

The payload contains statements about an entity (usually the authenticated user) and additional session metadata.

Standard Registered Claims:

iss (Issuer): Identifies the authority that issued the JWT.
sub (Subject): Identifies the principal subject of the token (e.g., user ID).
aud (Audience): Identifies the intended recipients or resource servers.
exp (Expiration Time): Unix epoch timestamp after which the token must not be accepted.
nbf (Not Before): Identifies the timestamp before which the token is invalid.
iat (Issued At): Timestamp recording when the token was generated.

3. The Signature

The signature validates that the token was neither tampered with nor forged in transit. For HMAC-SHA256:

HMACSHA256(
 base64UrlEncode(header) + "." + base64UrlEncode(payload),
 secret
)

Critical JWT Security Pitfalls

1. The “None” Algorithm Attack

In early implementations of RFC 7519, servers supported unsigned tokens where "alg": "none". Attackers bypassed authentication by altering the payload to grant admin privileges and setting "alg": "none" with an empty signature. Modern verification libraries strictly whitelist approved algorithms (algorithms: ['RS256']).

2. Key Confusion (Asymmetric to Symmetric)

When an API verifies tokens using an asymmetric algorithm (like RS256), the server uses a public key to verify and a private key to sign. In key confusion attacks, an adversary changes the header to "alg": "HS256" and signs the token using the server’s publicly accessible public key as the HMAC secret! Vulnerable servers verifying with jwt.verify(token, key) mistakenly treat the public key string as a shared symmetric secret.

3. Leaking Production Secrets to Web Tools

Never paste live customer session tokens or sensitive API tokens into third-party servers. Using our ensures parsing executes purely in local browser memory.

Interactive Workbench LIVE

JWT Security 101: How to Decode, Inspect, and Verify Claims Client-Side

Open Fullscreen ↗

Decode and inspect JWT headers, standard claims, and expiration timestamps securely in your browser.

Initializing Workbench...

100% Client-Side RAM Sandbox

🔒 Private Execution: Computations run in local browser memory. Zero server uploads. Zero server uploads.

Launch Fullscreen →

FAQ

Frequently Asked Questions

Is a JWT token encrypted? ▼

No. Standard JWTs (RFC 7519) are signed, not encrypted. The header and payload are simply Base64Url-encoded JSON strings. Anyone with access to the token string can decode and read the underlying claims in plaintext.

Why is it dangerous to paste production JWTs into random online debuggers? ▼

Many online token inspectors transmit tokens over HTTP to their backend servers for logging or telemetry. If your token contains confidential user IDs, role permissions, or OAuth access scopes, server-side log ingestion creates severe security liabilities. Always use client-side tools.

What is the 'algorithm none' vulnerability in JWT verification? ▼

The 'none' algorithm is an optional spec in RFC 7519 for unsigned tokens. If an insecure server verification library accepts alg: 'none', an attacker can strip the signature, modify the payload (e.g. set 'admin': true), and forge unauthorized authentication.

Jwt | Toolbox Guides & Articles

JWT Security 101: How to Decode, Inspect, and Verify Claims Client-Side

JWT Token Inspector & Decoder

What Is a JSON Web Token (JWT)?

The Three Components of a JWT

1. The Header

2. The Payload (Claims)

Standard Registered Claims:

3. The Signature

Critical JWT Security Pitfalls

1. The “None” Algorithm Attack

2. Key Confusion (Asymmetric to Symmetric)

3. Leaking Production Secrets to Web Tools

JWT Security 101: How to Decode, Inspect, and Verify Claims Client-Side

Frequently Asked Questions