How to use WebAuthn Public Response Inspector
- Paste the base64url clientDataJSON and authenticatorData members, or select their separate UTF-8 encoded-member files. Files replace the corresponding text; they are not whole response JSON documents.
- Optionally supply the supported attestationObject as base64url text or its file. The inspector reads a definite-length CBOR subset.
- Choose decoded detail output if needed. Raw challenge and credential ID have a separate opt-in and remain omitted unless requested.
- Run Inspect response. Read claimed type/origin, relying-party hash, flags, counter and optional attestation metadata as supplied fields, not authentication evidence.
Example: WebAuthn Public Response Inspector
Decode minimal example client and authenticator members with one flag and no attestation object.
Options
- clientDataJSON (base64url)
- The clientDataJSON member, base64url encoded. Up to 60,000 UTF-8 bytes. A selected text file takes priority over this value.
- authenticatorData (base64url)
- The authenticatorData member, base64url encoded. Up to 60,000 UTF-8 bytes. Its selected text file takes priority. The first 37 decoded bytes carry the relying-party hash, flags and counter.
- clientDataJSON base64url text file (optional)
- One UTF-8 file containing the encoded member, not a whole response JSON document.
- authenticatorData base64url text file (optional)
- One UTF-8 file containing the encoded member.
- attestationObject base64url text file (optional)
- One UTF-8 file containing the encoded member. It takes priority over the optional text.
- Include decoded flags and binary metadata in the text report
- The summary table stays visible. Raw credential ID and challenge need their separate opt-in below.
- attestationObject (base64url, optional)
- Optional. Only the definite-length CBOR subset used by public attestation objects is read. Indefinite lengths, tags, duplicate keys and trailing bytes are refused.
- Include the raw credential ID and challenge in the result
- Off by default. Credential IDs and challenges can identify a person or a session, so they stay out of the table, text and download unless you ask for them.
Supported inputs and limits
- Encoded member text/files are bounded at 60,000 UTF-8 bytes each and must use the supported base64url/JSON/CBOR/COSE subset.
- Recorded origins must be HTTP(S) origins without path, query, credentials or fragment.
- Duplicate JSON/CBOR keys, unsupported lengths/tags and trailing bytes are refused.
- Raw challenge and credential identifiers remain opt-in.
- No expected-challenge/origin/RP-hash comparison, signature check, attestation-provenance validation, enrollment or authenticator prompt is performed.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Decoded flags are not an authentication decision
A flag or claimed origin describes the supplied bytes. This inspector does not establish that they came from a trusted authenticator, match an expected challenge or satisfy a relying party’s policy. Attestation metadata is decoded without verifying provenance or its signature.
Questions about WebAuthn Public Response Inspector
Does the result authenticate anyone?
No. It decodes supplied fields without a relying party’s expected challenge or trust checks.
Does a flag prove user verification?
It reports a flag in supplied bytes; authenticity of those bytes is not verified.
Will the browser prompt my authenticator?
No. This inspector does not call registration or authentication APIs.