JWT ES256 调试器
粘贴令牌，即可实时看到解码结果——头部、载荷和签名在原始文本与解码结果中以相同的颜色对应标出。然后用颁发者的公钥验证 ES256/ES384/ES512 签名；出现问题时会给出清晰的解释。
100% 本地运行——所有操作都在你的浏览器中完成，不会向任何服务器发送数据
解码结果
头部
算法和令牌类型第一段——第一个点之前的全部内容——解码后是 JOSE 头部：算法、令牌类型和密钥 ID。
载荷
声明第二段解码后是声明：令牌由谁签发、签发给谁、有效期多长。
签名
原始字节第三段——第二个点之后的全部内容——是对 header.payload 计算的原始签名，可在下方验证。
验证签名
签名未验证
解码不需要密钥——输入时即会实时解码。上方的令牌解码后，在此粘贴颁发者的公钥即可检查签名。
How it works
Everything on this page runs locally in your browser — the token and key are never sent anywhere. The token is split on dots, and the header and payload are base64url-decoded and parsed as JSON as you type; the colors in the editor are purely presentational and mirror the decoded blocks on the right. For ES256/ES384/ES512 the tool rebuilds the exact signing input — the ASCII string header.payload — hashes it with SHA-256/SHA-384/SHA-512, and checks the raw r‖s signature against your public key on P-256/P-384/P-521 using the audited @noble/curves library. Time claims are compared against your machine's clock, so a token that looks expired here may still be accepted by a server with clock skew tolerance. Remember that a valid signature only authenticates the issuer — checking exp, iss and aud is still your job.