Tools that never phone home
Paste tokens and messages without worrying where they go: everything runs in this page. All tools →
Start here
Four pages that change how most teams handle identity.
Privileged access
The accounts that can change everything deserve the most care. These pages cover who should hold privilege, for how long, how it is granted and watched, and how machines get credentials without leaving secrets lying around.
Authentication
Proving who someone is, and how much that proof is worth. Written from NIST SP 800-63B-4, CISA guidance and the W3C WebAuthn specification.
Protocols
The protocols that carry identity between systems, explained from the specifications with real HTTP messages: what each step does, what each token means, and where implementations go wrong.
- OAuth 2.0→
- Authorization code flow with PKCE→
- Client credentials grant→
- Device authorization grant→
- Access, refresh and ID tokens→
- Scopes and consent→
- JSON Web Tokens (JWT)→
- OpenID Connect→
- SAML 2.0→
- OAuth security mistakes (RFC 9700)→
- Sender-constrained tokens: DPoP and mTLS→
- OAuth, OpenID Connect and SAML compared→
How this site is made
Primary sources only
Requirements come from NIST, IETF, OpenID Foundation, OASIS and W3C documents, with the exact strength (SHALL, SHOULD, MAY) the text uses. Every page lists its sources and the date it was last checked.
Tested tools
The JWT verifier, PKCE generator, SAML decoder and password checker are tested against the RFCs' own example tokens and keys on every build: 37 of 37 checks pass. See the results.
No vendor in the room
No sponsors, no affiliate links, no product recommendations. Where a choice depends on your environment, the page says what it depends on.