# Decode a WebAuthn attestationObject online

> Free WebAuthn decoder: read clientDataJSON, attestationObject and authenticatorData, flags, AAGUID, COSE key as JWK, and check signatures in your browser.

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

Paste what navigator.credentials returned. I decode the CBOR, name the authenticator when I can and check the attestation and sign-in signatures.

## What can I paste here

A WebAuthn registration or authentication JSON (the credential from navigator.credentials), or the fields separately: clientDataJSON and attestationObject for a registration, or clientDataJSON, authenticatorData, signature and the public key for an assertion.

## What it does

- Decodes clientDataJSON, the attestationObject (CBOR) and authenticatorData, including rpIdHash, the UP, UV, BE, BS, AT and ED flags and signCount.
- Names the AAGUID from a bundled list and turns the COSE public key into a JWK with its thumbprint.
- Verifies packed attestation and the sign-in signature, and checks the RP ID and origin you expect.

## Example use

On webauthn.io or in the Chrome WebAuthn panel, copy the attestation response, paste it here, and read the AAGUID, flags and public key.

## How to read the result

- BE means the passkey may be synced, BS means it is synced right now. A device-bound key has neither.
- UP means someone touched the authenticator, UV means it also checked a PIN or biometric. Ask for UV when the passkey replaces a password and a second factor.
- The AAGUID names the authenticator model. Without verified attestation it is a claim, so use it for display, not for policy.
- The sign-in signature covers authenticatorData followed by the SHA-256 of clientDataJSON. I verify it with the key from the registration or a JWK you paste.

## What it does not do

- Only packed attestation is verified, and only up to the leaf certificate. tpm, android-key, apple and fido-u2f are decoded, not verified, and no chain is checked against a root.
- The AAGUID list is bundled and small: security keys from the Microsoft Entra docs, Windows Hello, Microsoft Authenticator and Google Password Manager. Many synced providers are missing.
- It does not know your challenge. Compare the challenge shown here with the one your server stored.

## Questions people ask

### What can I paste here

A WebAuthn registration or authentication JSON (the credential from navigator.credentials), or the fields separately: clientDataJSON and attestationObject for a registration, or clientDataJSON, authenticatorData, signature and the public key for an assertion.

### What do the BE and BS flags mean?

BE (backup eligible) says the credential can be synced to other devices. BS (backup state) says it is synced now. Both are set for most passkeys in Apple, Google and password manager apps.

### Why is the AAGUID all zeros?

Some providers send a zero AAGUID on purpose, usually with none attestation. The relying party then cannot tell the model, and this tool shows it as not disclosed.

## 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.

- [Decode an attestationObject (registration)](https://iamops.dev/tools/webauthn/#mode=attestation): `#mode=attestation`
- [Decode an assertion (authentication)](https://iamops.dev/tools/webauthn/#mode=assertion): `#mode=assertion`

## 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/)
- [DPoP proof builder and checker](https://iamops.dev/tools/dpop.md): Build a DPoP proof with a fresh ES256 key, or check typ, htm, htu, iat, ath, nonce and the cnf.jkt thumbprint. Paste a DPoP JWT and the method and URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/dpop/)
- [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/)
- [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/)
