Guide

THE TOOLBOX / SECURITY & PASSKEYS

WebAuthn & Passkey Debugger —
Inspect clientDataJSON, authenticatorData Flags (UP/UV/BE/BS) & signCount.

Decode Base64URL or Hex WebAuthn `clientDataJSON` and `authenticatorData` payloads locally to inspect RP ID hashes, passkey sync flags (BE/BS), user verification (UV), signCount, and AAGUID.

Decoded Passkey / WebAuthn Inspection
clientDataJSON
{
  "type": "webauthn.get",
  "challenge": "dGhpcy1pcy1hLXNhbXBsZS1jaGFsbGVuZ2UtMTIzNDU",
  "origin": "https://app.example.com",
  "crossOrigin": false
}
authenticatorData Flags & CountersignCount: 7 · 0x1d
UP
1
UV
1
BE
1
BS
1
AT
0
ED
0
rpIdHash (SHA-256): 49960de5880e8c687434170f6476605b8fe4aeb9a28632c7995cf3ba831d9763

WEBAUTHN DEBUGGING

Frequently Asked Questions

What do the BE and BS flags in WebAuthn authenticatorData mean?

BE (Backup Eligibility, bit 3) indicates whether the credential can be backed up/synced (like iCloud Keychain or Google Password Manager). BS (Backup State, bit 4) indicates whether the passkey is currently synced. Device-bound hardware keys like YubiKeys report BE=0, BS=0.

What is the rpIdHash in WebAuthn authenticatorData?

The first 32 bytes of authenticatorData are the raw SHA-256 hash of the Relying Party ID (typically your domain name like `example.com`). Servers verify this hash to prevent phishing and cross-domain replay attacks.

Is my passkey assertion or credential payload sent to any server?

Never. All Base64URL/Hex decoding and flag bitmask inspection execute 100% locally in your browser.