Decoding is not verifying
A JWT’s header and payload are only base64url-encoded, not encrypted, so anyone holding the token can read them; never put secret data in the payload. What guarantees authenticity is the signature: the server must verify it with the correct key and reject the none algorithm. The valid or expired status in this tool is based only on the time claims, and is not proof that the token is genuine.
The time claims iat (issued at), nbf (not before) and exp (expiry) are Unix seconds; this tool shows them in WIB (UTC+7) and UTC, plus relative time. Values in milliseconds are flagged because JWT uses seconds.