JWT decode versus verify
A JWT decoder can show the header and payload without proving that the token was signed by anyone you trust.
A JSON Web Token is three base64url parts separated by dots. Decoding the first two parts produces JSON. The third part is a signature or MAC, and reading the JSON does not check it.
The JWT decoder prints the header and payload and compares exp, nbf, and iat with a clock you can see. The notes always say the signature was not checked. There is no key field on that page, so a secret pasted beside the token is ignored. A token from the JWT generator can be opened there and the claims will show, and the MAC is still unverified.
The HMAC generator is a different tool. It can compare a message authentication code you already have. That comparison is not a JWT check, and it does not decide that an issuer is trustworthy. Trust in the issuer has to come from a verifier that holds the key.
Do not paste a production token into a site you do not trust. This page keeps the token in the browser while you use the tool.

