Client-Side · Zero Telemetry · RFC 7519 Compliant
JSON Web Token Decoder
Inspect encoded JWT claims, algorithms, and expiration status safely. Your sensitive authorization tokens are never sent across the network.
|
Anatomy of a JSON Web Token (RFC 7519)
1. Header
Specifies the cryptographic signing algorithm (such as HMAC SHA256 or RSA) and token type (usually "JWT").
2. Payload
Contains the authentication claims (e.g. user ID sub, roles, issue timestamp iat, and expiry exp).
3. Signature
Generated by hashing the encoded header and payload with a secret or private key to ensure message integrity and tamper resistance.