Download a dual well-known pack for multi-brand passkeys.
For teams shipping Related Origin Requests across brands or ccTLDs. Enter your RP ID and origins once — get both JSON files and a Pages Content-Type recipe. Everything stays in your browser.
Two files, one form
webauthn related origins + optional passkey-endpoints enroll/manage URLs.
Deploy recipe included
Pages _headers so extensionless JSON is served as application/json.
Validate elsewhere
We build the pack; passkeys.dev can validate after you publish.
Open the generator
RP ID, related origins, optional enroll/manage → download both files + headers.
How to deploy
Placement, Content-Type, Pages headers, Nginx note, optional validation.
Use cases
Five-label multi-brand limits and related-origins-first rollout.
FAQ
Who ships first, localhost, label warnings vs hard rejects, privacy.
Wedge vs passkeys.dev (for implementers)
Multi-brand and ccTLD sites often need two well-known documents on the same RP ID domain: /.well-known/webauthn for Related Origin Requests, and /.well-known/passkey-endpoints so password managers can deep-link into enroll/manage flows. Both must be extensionless application/json. passkeys.dev documents ROR and offers a validator. This site focuses on generating a deployable dual-file pack plus a Cloudflare Pages _headers recipe — then you can optionally validate elsewhere. Hand-authoring is where Content-Type and label-count mistakes sneak in.