Samprix

Passkey Readiness Checker

See whether password managers, browsers and your apps can find and share a domain’s passkeys, and what to fix in each file they read.

  • Public data only
  • Results in seconds
  • No sign-up
  • Free

What the passkey check looks at

Passkey endpoints

The pages password managers link to for creating and managing passkeys.

Related origins

The other domains allowed to use this domain’s passkeys, and the 5-name limit.

Apple and Android apps

Whether your apps are linked to share the website’s passkeys.

Change-password link

Where password managers send people to upgrade a weak password.

Advertisement

Publishing the passkey files

All of these live under /.well-known/ on the domain you use as the relying party ID (usually your main domain). Serve each one directly, with no redirect, over HTTPS, and the JSON files with Content-Type: application/json.

  1. passkey-endpoints: {"enroll": "https://example.com/account/passkeys/new", "manage": "https://example.com/account/passkeys"}
  2. webauthn, only if other domains share your sign-in: {"origins": ["https://example.co.uk", "https://example-app.com"]}
  3. apple-app-site-association, for Apple apps: {"webcredentials": {"apps": ["ABCDE12345.com.example.app"]}}, plus the webcredentials:example.com entitlement in the app.
  4. assetlinks.json, for Android apps: a statement with the relations delegate_permission/common.handle_all_urls and delegate_permission/common.get_login_creds, the package name and the SHA-256 fingerprint of the signing certificate.
  5. change-password: a redirect (302 or 303) from /.well-known/change-password to your change-password page.

Common problems

  • A redirect to www: the bare domain redirects every path to www, so the files never load from the relying party ID. Exempt /.well-known/ from the redirect.
  • Served as text/plain or octet-stream: files without an extension get the wrong type. Set it for each path in nginx, Apache or your CDN.
  • Blocked by a firewall or bot protection: browsers and Apple’s CDN fetch these files without cookies. A challenge page or a login wall in front of /.well-known/ breaks them.
  • More than five names in related origins: browsers ignore the rest. Country domains of the same name (example.com, example.de) count as one.

Did this tool do what you needed?

All tools