01
What it looks at
What each part of the answer means, and what to do when one is not right.
Press the button and your browser answers four questions about passkeys on this device – from the WebAuthn calls themselves, not from guessing at the browser’s name.
What this check looks at
Whether the browser supports WebAuthn at all, whether the device has a built-in authenticator that checks it is you (Face ID, Touch ID, Windows Hello or an Android screen lock), whether passkeys can appear in the sign-in box as you type, and whether the browser can use a phone nearby as your passkey.
What a failing result means
Without a built-in authenticator you can still use a passkey on your phone or a security key. A browser with no WebAuthn at all is too old for passkeys and probably for other security fixes too.
How to fix it
Update the browser, switch on a screen lock or Windows Hello in the device’s settings, and on a computer without one, use your phone: sites that offer passkeys show a QR code to scan.
02
What people ask about it
Straight answers, from what the check itself does.
- What is a passkey?
- A sign-in that replaces a password: your device keeps a key that only works on the real site and only after you unlock it, so it cannot be phished, guessed or leaked in a breach.
- Does this create a passkey or send anything?
- No. It only asks your browser what it supports. Nothing is created, stored or sent to Xovris.
Connect your computers to Xovris (in beta) and the software on each is matched against open advisories and ranked by real risk.
Watch my devices