Passkey Tester

Passkey Tester: Check your browser's passkey support

Want to know whether your browser offers passkeys, or why a sign-in page shows no suggestion? Click “Start test”. The Passkey Tester checks the interfaces of this browser on this device. It distinguishes available features, missing APIs and rejected checks. The standard test opens no sign-in dialog. You need neither an account nor a saved passkey, and you do not enter any personal information.

What a passkey does

A passkey is a cryptographic sign-in credential based on FIDO2 and WebAuthn. The private key stays with your authenticator or passkey provider, while the website receives the public key. Many providers sync passkeys between your devices using encryption. Others keep them on one device or a security key. A passkey can replace a password and a separate second factor: you approve its use with a fingerprint, facial recognition or device PIN. Each website still decides how to structure its sign-in process. The FIDO Alliance explains the underlying standards.

Understand the capability checks

The secure context check comes first. WebAuthn needs HTTPS or a trusted local environment such as localhost. The HTTPS row and secure context result are separate for that reason. The tool then checks the WebAuthn interface and asks your browser whether a platform authenticator is available. Examples include Windows Hello, Touch ID and passkey management on Android with Google Password Manager. A negative result does not rule out an external security key.

Conditional mediation means a passkey can appear in the username field autofill. The website must implement that feature itself. Without it, a dedicated passkey button may still work. The tester also reports the presence of navigator.credentials.create, get and store, without calling them during the standard run. Their presence alone does not prove that a login will succeed. The summary identifies your browser and platform from the user agent, which can be modified or inaccurate.

Optional live request and browser support

Only the second button starts a local WebAuthn request to your browser. It uses a random challenge for this website, a ten-second timeout and does not request user verification. A dialog can still appear. The tester does not register a passkey, sign you in anywhere or inspect response data. A “NotAllowedError” is normal: you may have cancelled, no authenticator may be available, or a blocker such as Passkey Shield may have intervened. The error does not identify which explanation applies.

As of October 2026, Chrome, Edge, Brave and Opera generally offer the usual passkey features. Firefox 140 and later on desktop and Safari 16 and later also support passkeys. Details depend on the operating system, provider and browser build. The actual test results therefore tell you more than a browser name alone. Extensions, managed-device policies and embedded browsers can restrict features.

Limits and privacy

This tool cannot look inside your operating system authenticator or enumerate saved passkeys. The live request result also depends on what you do with the dialog. The test runs entirely in your browser. No data is transmitted. The tool code sends no results, challenge or responses to a server. For conventional credentials, try the Password Checker, Password Generator and Passphrase Generator.

Frequently asked questions