Practical Picks PP-278: earlier hands-on check record, October 3, 2026 Historical record. This check ran on October 3, 2026, before Practical Picks adopted its research-only method (no product tests). It is kept as dated history, is not current testing, and did not decide the October 19, 2026 recommendation, which rests on public sources. Tools named below were checked as served on that day only. Tested 2026-10-03 UTC, Chromium on Linux x86-64, anonymous fresh browser context for each input. An independent Node.js crypto script generated HS256 JWTs with an invented issuer, audience, subject and key. Six inputs were tried in each site: valid, payload tampered after signing, correctly signed expired, correctly signed wrong audience, valid token with wrong HMAC key, and malformed two-segment text. The script and complete per-run UI/HTTP/request log are retained privately in research/PP-278. No live credential, real service account or production key was used. For each run, the browser captured request URLs and request bodies and searched for exact token and key strings. There were zero exact matches in those fields across 18 runs. This is a bounded observation, not a privacy audit or security guarantee. It does not cover scripts, extensions, other user actions, server logging of other values, or future changes. Do not paste active credentials into a browser tool based on this test. Results: all three marked correct HS256 signatures valid and tampered/wrong-key signatures invalid. All three still marked correctly signed expired and wrong-audience tokens as having valid signatures. Only TokenPrism gave a separate visible expired-token advisory. None had a supplied expected issuer/audience policy; each displayed the audience without judging a mismatch. jwt.io and TokenPrism gave explicit malformed-format feedback; WorkOS said it could not decode the token. TokenPrism required choosing UTF-8 secret encoding. WorkOS actual tool URL was /docs/tools/jwt-debugger. Passing a signature check does not mean an application should accept a token. An application verifier must check the signature, allowed algorithm, issuer, audience, expiry, not-before and any applicable policy. This comparison covers initial synthetic-token diagnosis, not authentication design or live-token handling.