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
Results for github.com
- Passkey endpoints · Not set up
- Related origins · Not set up
- iPhone, iPad and Mac apps · Not set up
- Android apps · Not set up
- Change-password link · Valid
Passkey endpoints
/.well-known/passkey-endpointsLets password managers offer to create a passkey for your site and link to your passkey pages.
-
Warning:No passkey-endpoints file
Password managers (1Password, Bitwarden, Google and Apple) use /.well-known/passkey-endpoints to offer “Create a passkey for this site” and link straight to your page. Without it they can’t tell people your site supports passkeys.
Related origins
/.well-known/webauthnLets one passkey work across your other domains (up to 5 distinct names).
-
Note:No related origins file
Passkeys made on this domain only work on it and its subdomains. That’s fine unless you run the same sign-in on other domains (example.co.uk, example-app.com): list those in /.well-known/webauthn so one passkey works on all of them.
iPhone, iPad and Mac apps
/.well-known/apple-app-site-associationLets your Apple apps use the same passkeys as the website.
-
Note:No "webcredentials" section
The file sets up universal links, but no app is allowed to use this domain’s passkeys. If your iOS app signs in, add {"webcredentials": {"apps": ["TEAMID.com.example.app"]}}.
File as served
{
"applinks": {
"defaults": {
"caseSensitive": false
},
"substitutionVariables": {
"excludedProducts": [
"_graphql",
"about",
"accelerator",
"account",
"actions-beta",
"addons",
"admin",
"advisories",
"advisory-database",
"advisory-db",
"advisorydatabase",
"advisorydb",
"all-in-open-source",
"anonymous",
"any",
"api",
"apple-app-site-association",
"apps",
"assets-cdn",
"assets",
"attributes",
"auth",
"avatars",
"baitshop",
"billing",
"blob",
"blog",
"bounty",
"branches",
"brand",
"buildingthefuture",
"business",
"businesses",
"c",
"cache",
"callbacks",
"camo",
"careers",
"categories",
"central",
"certification",
"certifications",
"changelog",
"chat",
"cla",
"cloud",
"codeload",
"codeql",
"codereview",
"codesearch",
"codespaces",
"collection",
"collections",
"collector-cdn",
"comments",
"commit",
"commits",
"companies",
"compare",
"contact-sales",
"contact",
"contributing",
"cookbook",
"copilot",
"coupons",
"ctags",
"customer-stories",
"customer",
"customers",
"dashboard",
"dashboards",
"de",
"dependency-insights",
"design-blog",
"design-system",
"design-team",
"design",
"designs-system",
"designs-systems",
"develop",
"developer-stories",
"developer",
"devtools",
"diff",
"difftool",
"discover",
"discussion_messages",
"discussions",
"downloads",
"downtime",
"earlyaccess",
"edit_repositories",
"editor",
"editors",
"edu",
"education",
"email",
"enterprise-cloud",
"enterprise-docs",
"enterprise-legal",
"enterprise-server",
"enterprise",
"enterprises",
"error_pages",
"events",
"experience",
"explore",
"featured",
"features",
"file-servers",
"files",
"fixtures",
"forked",
"fr",
"frequently-asked-questions",
"g1thub",
"game-off",
"gameoff",
"garage",
"generated_pages",
"geocities",
"getting-started",
"gist-assets",
"gist-raw",
"gist",
"gists",
"github_spark_waitlist_signup",
"github-and-vscode",
"github-apps",
"github-copilot",
"github-design-systems",
"github-outreach",
"gitlfs",
"glthub",
"graphs",
"guide",
"guides",
"halp",
"help-wanted",
"help",
"home",
"hooks",
"hosting",
"identicons",
"identity",
"images",
"inbox",
"individual",
"info",
"integration",
"interfaces",
"introduction",
"investors",
"javascripts",
"jobs",
"join",
"journal",
"journals",
"jump-to",
"lab",
"labs",
"languages",
"launch",
"layouts",
"learn",
"legal",
"libgit2-ci",
"library",
"linux",
"listings",
"lists",
"login",
"logos",
"logout",
"mac",
"machine-room",
"mailers",
"maintenance",
"malware",
"man",
"marketplace",
"mcp",
"media",
"mention",
"mentioned",
"mentioning",
…Android apps
/.well-known/assetlinks.jsonLets your Android apps use the same passkeys as the website.
-
Note:com.github.android.dev, com.github.android.staff, com.github.android can’t use this domain’s passkeys
The statement doesn’t include "delegate_permission/common.get_login_creds". Add it to the relation list so Credential Manager lets the app use the website’s passkeys.
- com.github.android.dev app links only · 2 fingerprints
- com.github.android.staff app links only · 1 fingerprint
- com.github.android app links only · 1 fingerprint
File as served
[
{
"relation": [
"delegate_permission/common.handle_all_urls"
],
"target": {
"namespace": "android_app",
"package_name": "com.github.android.dev",
"sha256_cert_fingerprints": [
"94:53:53:34:54:66:B1:30:4B:3C:67:9D:E7:9C:C2:AA:77:E4:4E:FF:1B:1A:F8:D9:64:C8:79:82:16:CC:88:68",
"3C:B3:96:8D:FD:F5:17:27:EC:DD:C2:EB:08:D8:27:BF:45:63:43:59:35:1F:FA:DD:6B:FD:2D:8A:E0:D0:68:6B"
]
}
},
{
"relation": [
"delegate_permission/common.handle_all_urls"
],
"target": {
"namespace": "android_app",
"package_name": "com.github.android.staff",
"sha256_cert_fingerprints": [
"F6:50:1D:96:30:92:5A:AF:2E:AF:B0:CE:51:F5:43:C6:BE:89:D8:68:C8:3F:92:05:06:A4:6F:E5:DA:49:AA:2E"
]
}
},
{
"relation": [
"delegate_permission/common.handle_all_urls"
],
"target": {
"namespace": "android_app",
"package_name": "com.github.android",
"sha256_cert_fingerprints": [
"DF:08:C9:F2:D8:09:18:9D:9D:50:64:97:C1:57:45:A7:39:5A:41:53:6E:FB:43:3E:3A:EE:1A:ED:BE:11:B2:61"
]
}
}
]Change-password link
/.well-known/change-passwordWhere password managers send people to replace a weak password, or switch to a passkey.
-
OK:Change-password link works
It redirects to https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fsettings%2Fsecurity.
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.
- passkey-endpoints:
{"enroll": "https://example.com/account/passkeys/new", "manage": "https://example.com/account/passkeys"} - webauthn, only if other domains share your sign-in:
{"origins": ["https://example.co.uk", "https://example-app.com"]} - apple-app-site-association, for Apple apps:
{"webcredentials": {"apps": ["ABCDE12345.com.example.app"]}}, plus thewebcredentials:example.comentitlement in the app. - assetlinks.json, for Android apps: a statement with the relations
delegate_permission/common.handle_all_urlsanddelegate_permission/common.get_login_creds, the package name and the SHA-256 fingerprint of the signing certificate. - change-password: a redirect (302 or 303) from
/.well-known/change-passwordto 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.
Frequently asked questions
What does this passkey checker test?
It fetches the public files that browsers, password managers and phones read before they use passkeys with your domain: /.well-known/passkey-endpoints, /.well-known/webauthn (related origins), apple-app-site-association, assetlinks.json and /.well-known/change-password. It checks each one is where it should be, served the right way, and says what it should.
Can it tell whether my site supports passkeys?
Not directly: passkey sign-in happens in JavaScript on your login page, which nobody can see from outside. What it can see is whether the domain publishes the files that make passkeys easy to find and that let them work across your domains and apps. Big passkey sites often have some of these and not others.
What is /.well-known/passkey-endpoints?
A small JSON file, {"enroll": "…", "manage": "…"}, with the addresses of the pages where people create and manage passkeys. Password managers such as 1Password, Bitwarden and Google Password Manager read it to suggest upgrading an account to a passkey and to link straight there. It’s a W3C draft that browsers and password managers already use.
What are related origins (/.well-known/webauthn)?
A passkey belongs to one domain, its relying party ID. If the same accounts sign in on other domains (example.co.uk, example.de, example-app.com), the main domain can list them in /.well-known/webauthn and browsers let those sites use its passkeys. Chrome and Safari support it; browsers count up to five distinct names, and country domains of the same name count once.
Why must these files not redirect?
Browsers fetch the webauthn file without following redirects, and Apple and Android don’t follow them for their association files either. A redirect from example.com to www.example.com, which many sites have, quietly breaks them. Serve the files directly on the domain you use as the relying party ID.
Do I need assetlinks.json and apple-app-site-association?
Only if you have mobile apps that sign in to the same accounts. With them, a passkey made on the website works in the app and the other way round. On Apple, list the app under "webcredentials"; on Android, add the "delegate_permission/common.get_login_creds" relation.
Did this tool do what you needed?
Related tools
All toolsWHOIS Domain Lookup
Who registered a domain, when, and when it expires: check a suspicious sender or your own renewal.
Email Domain Health Check
Can someone spoof your domain? SPF, DKIM, DMARC, MX and blocklists checked together, with a score and fixes.
DMARC Record Checker
See whether a domain’s DMARC policy actually stops spoofed mail, and what to change before tightening it.