Taprico
Developer Studio AUTH / OIDC 100% Client-Side

JWT Decoder, Claims Inspector & Signature Verifier

Decode JSON Web Tokens, audit RFC 7519 claims, track live expiration timers, and verify HMAC signatures via Web Crypto.

Encoded JWT InputWeb Crypto Local
Color-Coded Token Anatomy
Header·Payload·Signature

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL2F1dGgudGFwcmljby5jb20iLCJzdWIiOiJ1c3JfOTg0Ml91c19lYXN0IiwiYXVkIjoidGFwcmljby1hcGkiLCJlbWFpbCI6ImFsZXhAYWNtZS5kZXYiLCJyb2xlcyI6WyJkZXZlbG9wZXIiLCJiaWxsaW5nIl0sImlhdCI6MTc2MzI3MDQwMCwiZXhwIjoxODk0ODk2MDAwfQ.dummySignatureForInspectionOnly

HMAC Signature Verifier

Verified using native crypto.subtle inside your browser. Asymmetric RS256/ES256 tokens require your provider JWKS public key.

Active · Expires in 1522d 10h 40m 0s
Jan 17, 2030, 11:00 AM ET
HEADER · Algorithm & Token Type
{
  "alg": "HS256",
  "typ": "JWT"
}
PAYLOAD · Claims & Identity Data
{
  "iss": "https://auth.taprico.com",
  "sub": "usr_9842_us_east",
  "aud": "taprico-api",
  "email": "[email protected]",
  "roles": [
    "developer",
    "billing"
  ],
  "iat": 1763270400,
  "exp": 1894896000
}
Decoded Claim Annotations
iss
https://auth.taprico.com
Issuer — principal that issued the token
sub
usr_9842_us_east
Subject — unique user or service ID
aud
taprico-api
Audience — intended API/resource recipient
roles
["developer","billing"]
iat
1763270400 (Sun, 16 Nov 2025 05:20:00 GMT)
Issued At — when token was minted
exp
1894896000 (Thu, 17 Jan 2030 16:00:00 GMT)
Expiration Time — token invalid after this Unix timestamp

Live Expiration Countdown

Converts Unix epoch exp, iat, and nbf claims into US Eastern, Pacific, and UTC dates with real-time ticking status.

Client-Side HMAC Verification

Verify HS256, HS384, and HS512 signatures natively with your browser SubtleCrypto engine—no secret ever leaves your machine.

Automated Security Warnings

Flags missing exp claims, insecure alg: none headers, and overly long token lifetimes automatically.

How to Use JWT Decoder

  1. 1 Paste an encoded JWT (header.payload.signature) or select one of the sample tokens (Valid HS256, Auth0 RS256, or Expired Token).
  2. 2 Inspect the color-coded token anatomy bar and decoded Header & Payload JSON objects side by side.
  3. 3 Hover or read the Claims Table to translate standard fields like sub, aud, iss, iat, nbf, and exp into local timestamps.
  4. 4 For HMAC-signed tokens (HS256/384/512), enter your signing secret in the Signature Verifier panel to cryptographically validate authenticity.

Anatomy of a JSON Web Token (RFC 7519)

A standard JWS token consists of three Base64URL-encoded segments separated by dots: Header, Payload, and Signature. Because the header and payload are merely Base64URL-encoded—not encrypted—anyone holding a token can read its claims.

Never store passwords, Social Security numbers, credit card details, or confidential API keys inside unencrypted JWT claims. Treat JWT payloads as tamper-evident, not secret.

Production JWT Security Checklist

Most authentication vulnerabilities around JWTs stem from verification mistakes rather than broken cryptography.

  • Explicitly pin allowed signing algorithms on your server (reject "none" and reject HS256 when expecting RS256/ES256 public keys).
  • Always enforce short access token TTLs (5–15 minutes) paired with rotating refresh tokens.
  • Validate both `iss` (Issuer) and `aud` (Audience) claims so tokens minted for one microservice cannot be replayed on another.

Frequently Asked Questions

Is it safe to paste a production JWT or HMAC secret here? +

Yes. Taprico decodes Base64URL segments and verifies HMAC signatures exclusively via your browser Web Crypto API (crypto.subtle). Neither the token nor your secret is transmitted over the network.

Why can anyone decode a JWT without a secret key? +

Standard JWTs use JSON Web Signature (JWS), which signs data to prevent tampering rather than encrypting it. A secret or public key is only required to verify the signature, not to read the header and payload.

What is the difference between HS256 and RS256? +

HS256 is symmetric: the same secret signs and verifies the token. RS256 is asymmetric: the auth provider signs with a private RSA key, and microservices verify using a public JWKS endpoint.

Why does my token show "Missing exp claim"? +

RFC 7519 treats exp (Expiration Time) as optional at the spec level, but omitting it creates non-expiring bearer credentials. Production APIs should almost always include an exp timestamp.