# JWT.io Debugger does validate at all. Considers ANY secret as valid. How is this possible?

**URL:** <https://community.auth0.com/t/jwt-io-debugger-does-validate-at-all-considers-any-secret-as-valid-how-is-this-possible/115215>\
**Category:** JWT.io\
**Tags:** jwt-debugger\
**Created:** [September 1, 2023, 1:40pm UTC](https://community.auth0.com/t/jwt-io-debugger-does-validate-at-all-considers-any-secret-as-valid-how-is-this-possible/115215 "2023-09-01T13:40:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![suchislife801](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/suchislife801/32/50280_2.png) [@suchislife801](https://community.auth0.com/u/suchislife801)\
**Post date:** [September 1, 2023, 1:40pm UTC](https://community.auth0.com/t/jwt-io-debugger-does-validate-at-all-considers-any-secret-as-valid-how-is-this-possible/115215/1 "2023-09-01T13:40:05Z")

</div>

1. Go to [JWT.io](http://JWT.io) right now and under Verify Signature which contains “your-256-bit-secret” go ahead and type anything in. I mean ANYTHING. What do you see?

Signature Verified.

1. Go to [JWT.io](http://JWT.io) again, then copy & paste your perfectly fine custom JWT in the Encoded Box. Now enter your custom Secret. What do you see?

Signature Verified.

1. Now go ahead modify your custom Secret under Verify Signature. Yep, go ahead and smash buttons on your keyboard. Type anything. Yes, really. What do you see?

Signature Verified.

How is this possible?

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [September 1, 2023, 6:23pm UTC](https://community.auth0.com/t/jwt-io-debugger-does-validate-at-all-considers-any-secret-as-valid-how-is-this-possible/115215/3 "2023-09-01T18:23:52Z")

</div>

Hey there @suchislife801 !

I believe this answers your question:

> [@Jwt.io debugger always returning signature verified with random using a random key](https://community.auth0.com/t/jwt-io-debugger-always-returning-signature-verified-with-random-using-a-random-key/36702/2):
>
> If you change an HS256 key value on [jwt.io](http://jwt.io) the signature component is updated automatically so the signature would be verified as it was just updated. If you want to check the signature of an existing token then first set the key value and only after paste the existing token.

---

<div class="post-metadata">

**Author:** ![suchislife801](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/suchislife801/32/50280_2.png) [@suchislife801](https://community.auth0.com/u/suchislife801)\
**Post date:** [September 11, 2023, 5:30pm UTC](https://community.auth0.com/t/jwt-io-debugger-does-validate-at-all-considers-any-secret-as-valid-how-is-this-possible/115215/4 "2023-09-11T17:30:30Z")

</div>

And you couldn’t just code it so it works both ways?

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [September 25, 2023, 5:31pm UTC](https://community.auth0.com/t/jwt-io-debugger-does-validate-at-all-considers-any-secret-as-valid-how-is-this-possible/115215/5 "2023-09-25T17:31:02Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
