93 chars · 1 line
120 chars · 10 lines
Algorithm: HS256Signature not verifiedTime status: Not evaluated (invalid exp/nbf)nbf claim: Invalid NumericDate (expected number)
93 chars · 1 line
120 chars · 10 lines
JWT NumericDate troubleshooting
A quoted nbf value is valid JSON, so the token can decode, but NumericDate semantics expect a number. The decoder preserves the string instead of silently converting claim types. This tool is free to use. No account or payment is required.
Last updated
A decoder that coerced numeric-looking strings would hide issuer mistakes. Preserving the original JSON type makes the mismatch visible.
The quoted form remains text in the decoded payload.
"nbf":"2000000000""nbf":2000000000Common questions
No. It is a valid JSON string, which is why decoding succeeds.
No. It preserves the issuer's claim type.
In the token issuer or claim-generation code.
Debugging a specific JWT issue? Browse JWT troubleshooting.