52 chars · 1 line
77 chars · 8 lines
52 chars · 1 line
77 chars · 8 lines
JWT header troubleshooting
The typ header parameter is metadata and is not required for this decoder to parse the protected header JSON. The token still remains unverified, and application-specific token typing should follow the profile your verifier expects. This tool is free to use. No account or payment is required.
Last updated
The decoder only requires the header segment to contain a JSON object. Token profiles can impose stricter rules when the JWT is consumed.
Algorithm metadata is readable even though typ is not present.
{"alg":"HS256"}Algorithm: HS256Common questions
Yes, if the header is otherwise a valid JSON object.
No. Requirements depend on the JWT profile and application.
No. This page only decodes local token data.
Debugging a specific JWT issue? Browse JWT troubleshooting.