90 chars · 1 line
118 chars · 10 lines
Algorithm: HS256Signature not verifiedTime status: Not active yetNot before: 2033-05-18T03:33:20.000Z
90 chars · 1 line
118 chars · 10 lines
JWT not-before troubleshooting
The decoder preserves a numeric nbf claim, formats it as an ISO timestamp, and reports Not active yet when nbf is later than the current browser time. That local time-window inspection is still not signature, issuer, audience, or authorization verification. This tool is free to use. No account or payment is required.
Last updated
The decoder compares a numeric nbf value with the current browser time and can report Not active yet, but it does not verify the signature or apply issuer, audience, server-clock, or application-specific clock-skew policy.
The numeric claim is shown with an ISO timestamp and local time-window status.
"nbf":2000000000Time status: Not active yetCommon questions
Yes. For a numeric future nbf claim it reports Not active yet using the current browser time, but it does not reject or verify the token.
If your token profile uses nbf, enforce it according to your trusted validation policy.
Yes. This local status does not apply a configurable skew allowance; production verification libraries commonly do.
Debugging a specific JWT issue? Browse JWT troubleshooting.