IAM tools that run in your browser
Decode tokens, inspect a HAR, and test an API with OAuth, all in your browser.
Runs in your browser. Nothing you paste leaves your device.
Runs in your browser. Nothing you paste is sent anywhere. Don't paste production private keys.
The page makes no network request while you work. The only exceptions are the buttons that say Fetch, which call the address you type. Keep real private keys out of any web page, including this one.
Tokens
-
JWT decoder and verifier
Decode header and payload, read exp and iat as dates, verify with a secret, PEM, JWK or JWKS, and get warned about weak setups.
-
ID-JAG inspector
Check an ID-JAG against the draft, understand each claim, and copy the RFC 8693 and RFC 7523 requests as curl.
-
DPoP proof builder and checker
Build a DPoP proof with a throwaway ES256 key, or check one: signature, jkt, htm, htu, ath, nonce and cnf.jkt.
-
PKCE generator
Generate a PKCE verifier and S256 challenge, or check that a pair matches.
Federation
-
SAML decoder and verifier
Decode POST and redirect messages, check XML signatures, decrypt EncryptedAssertion, and flag the usual problems.
-
OIDC discovery and JWKS viewer
Read discovery metadata and JWKS, with warnings for PKCE, weak keys and risky grants.
-
MCP auth discovery checker
Fetch an MCP server's resource and AS metadata, check PKCE S256, CIMD or DCR, iss and scopes against the spec.
Credentials, passkeys and signals
-
SD-JWT and VC decoder
Split an SD-JWT, check disclosure digests against _sd and ..., verify the KB-JWT and the issuer key.
-
Passkey and WebAuthn decoder
Decode clientDataJSON, attestationObject and authenticatorData: flags, AAGUID, COSE key as JWK, signatures.
-
Shared Signals SET decoder
Decode a Security Event Token: CAEP and RISC events, sub_id formats, txn, timestamps and the signature.
HTTP and traces
Certificates and encoding
No tool matches that.
How your data is handled
The code is bundled with the site: no CDN, no third-party script, no upload. Decoding, signature checks and decryption all happen on your device. The only network calls are the Fetch buttons and the HTTP client, and those go from your browser straight to the address you typed.
Even so, treat any web page with care. Use test keys. If you must look at a production token or assertion, check the expiry first and prefer the command line for private keys.
About the samples
The sample certificates, SAML messages and tokens are generated with throwaway keys. The private keys are published on purpose so you can try decryption. Do not trust anything signed with them.