# Build or check a DPoP proof online

> Free DPoP proof builder and validator for RFC 9449. Make a test proof with a fresh ES256 key or check one: signature, jkt, htm, htu, ath, nonce and cnf.jkt.

- URL: https://iamops.dev/tools/dpop/
- Markdown: https://iamops.dev/tools/dpop.md
- Language: en
- Runs in your browser, nothing is uploaded.

Build a DPoP proof with a key that lives only in this page, or paste one to check. I verify the signature against the embedded key and compare method, URL, nonce and token hash.

## What can I paste here

To check a proof, paste a DPoP JWT (typ dpop+jwt), plus the HTTP method and URL it was built for. You can also paste an access token to check ath, and a nonce. The builder needs no pasted key: it creates one in the page.

## What it does

- Decodes a DPoP proof and shows its header, payload and public key.
- Verifies the signature with the key in the header and computes the jkt thumbprint you will see in cnf.jkt.
- Optionally compares the HTTP method, URL and access token hash with what the request used.

## Example use

Build a proof for POST and your token endpoint, or paste a proof from a failing call and see whether the method, URL or token hash is wrong.

## How to read the result

- A DPoP proof is signed with the key it carries. A valid signature proves possession of that key, nothing more.
- The jkt is the SHA-256 thumbprint of the public key (RFC 7638). An access token bound to this key carries the same value in cnf.jkt.
- htm and htu must match the request the proof was sent with. The query string and fragment are ignored for htu.
- ath is the hash of the access token. It is required when the proof goes to a resource server, and absent at the token endpoint.

## What it does not do

- It does not track jti, so it cannot tell you about replay. A server has to remember jti values for the proof lifetime.
- It does not know the server nonce. If the server sent a DPoP-Nonce, the proof must carry it.
- It checks the time with your clock and flags more than 5 minutes of difference.

## Questions people ask

### What can I paste here

To check a proof, paste a DPoP JWT (typ dpop+jwt), plus the HTTP method and URL it was built for. You can also paste an access token to check ath, and a nonce. The builder needs no pasted key: it creates one in the page.

### What does a DPoP proof contain?

A JWT with typ dpop+jwt, the public key in the header, and claims for the HTTP method, the URL, the time and, for resource calls, a hash of the access token.

### What is the jkt thumbprint?

It is the SHA-256 thumbprint of the proof key. The authorization server binds the access token to it in the cnf claim, so a stolen token is useless without the key.

### How do I create a DPoP proof for testing?

Enter the method and URL in Build a proof and press Build proof. The page generates a P-256 key in your browser, signs the proof and shows the jkt you would see in cnf.jkt.

## Open a mode directly

You can open this tool with a mode already selected by adding a #mode= fragment to the address. Never put secrets in the URL. The fragment only names a mode.

- [Build a proof](https://iamops.dev/tools/dpop/#mode=build): `#mode=build`
- [Check a proof](https://iamops.dev/tools/dpop/#mode=check): `#mode=check`

## Related

- [Certificate decoder](https://iamops.dev/tools/certificate-decoder.md): Decode an X.509 certificate, chain or CSR and read SANs, expiry, key size, fingerprints and chain order. Paste PEM, base64 DER or hex. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/certificate-decoder/)
- [SAML decoder and verifier](https://iamops.dev/tools/saml.md): Decode a SAMLRequest or SAMLResponse, check the XML signature and decrypt an EncryptedAssertion. Paste base64, raw XML or a redirect URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/saml/)
- [JWT decoder and verifier](https://iamops.dev/tools/jwt.md): Decode a JSON Web Token, show claims and expiry as dates, and verify the signature. Paste a compact JWT, then an HMAC secret, PEM key, JWK or JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/jwt/)
- [ID-JAG inspector](https://iamops.dev/tools/id-jag.md): Inspect an Identity Assertion JWT Authorization Grant against the IETF draft and get the curl requests. Paste a compact ID-JAG token. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/id-jag/)
- [PKCE generator](https://iamops.dev/tools/pkce.md): Generate a PKCE code verifier and S256 challenge, or check that a pair matches, with authorize and token snippets. Paste a verifier and optional challenge, or generate them here. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/pkce/)
- [OIDC discovery and JWKS viewer](https://iamops.dev/tools/oidc-discovery.md): Read an OpenID Provider discovery document and JWKS, and flag missing PKCE, weak keys or risky grants. Type the issuer, or paste the JSON if CORS blocks the fetch. Runs in your browser. Nothing is uploaded to this site; the fetch goes from your browser to the issuer. (https://iamops.dev/tools/oidc-discovery/)
- [Encoder and decoder](https://iamops.dev/tools/encoder-decoder.md): Encode or decode Base64, URL, hex, HTML entities, Unicode, gzip, deflate and the SAML redirect chain, with auto-detect. Paste the text. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/encoder-decoder/)
- [HAR inspector](https://iamops.dev/tools/har-inspector.md): Inspect a HAR file: filter requests, follow the OAuth or SAML flow, decode JWTs, and copy as curl with secrets redacted. Drop a HAR export from DevTools. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/har-inspector/)
- [HTTP client](https://iamops.dev/tools/http-client.md): Call an API from your browser with Basic, Bearer, an API key, or OAuth 2.0 (client credentials, authorization code with PKCE, device code, refresh, token exchange) and optional DPoP. Enter the URL and auth details, or paste a curl command, HAR or OpenAPI definition. The request goes from your browser, not through this site. If CORS blocks the call, the page offers curl instead. (https://iamops.dev/tools/http-client/)
- [SD-JWT and VC decoder](https://iamops.dev/tools/sd-jwt.md): Decode an SD-JWT or SD-JWT VC: split disclosures, recompute digests against _sd, and check the Key Binding JWT. Paste the compact string with ~ separators, and optionally the issuer JWK. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/sd-jwt/)
- [Passkey and WebAuthn decoder](https://iamops.dev/tools/webauthn.md): Decode a WebAuthn or passkey response: attestationObject, clientDataJSON and authenticator data, including flags, AAGUID, sign count and the COSE public key. Paste the credential JSON or the individual fields. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/webauthn/)
- [MCP auth discovery checker](https://iamops.dev/tools/mcp-auth.md): Check MCP authorization discovery: Protected Resource Metadata (RFC 9728) and the authorization server metadata, and flag missing PKCE S256, CIMD/DCR or resource indicators. Enter the server URL, or paste the JSON if CORS blocks the fetch. Requests go from your browser, nothing is uploaded to this site. (https://iamops.dev/tools/mcp-auth/)
- [Shared Signals SET decoder](https://iamops.dev/tools/shared-signals.md): Decode a Shared Signals Security Event Token (CAEP or RISC), explain the event type and the sub_id formats, and optionally verify the signature. Paste the SET JWT and optionally the transmitter JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/shared-signals/)
