06 tools
Developer
JSON, Base64, JWT, HTML entities and regex.
The debugging chores
Everything here exists because a developer needed to look inside something opaque: whether a JSON payload is actually valid, what a JWT really claims, what those percent signs in a URL decode to, which characters in a snippet are HTML entities rather than text. Each one takes a copy-paste and returns an answer in under a second.
Order of operations when something breaks
Start with the data, not the code. Validate the JSON first — a payload that fails to parse never reaches your handler, so any logging you added there will stay silent. Then decode the token and compare exp against the clock, because an expired credential produces the same 401 as a wrong one. Only then look at encoding: a value that arrives truncated or double-escaped usually passed through one too many encode/decode steps.
What none of these do
They do not verify signatures, they do not fetch URLs, and they do not execute the code you paste. Decoding a token proves only that it is well-formed — whether it should be trusted is a question for the server holding the key.