WebAuthn Related Origin Requests
Lets one passkey work across several of a company's domains.
In one line
Can let one passkey work across a company's own listed websites
Lets one passkey work across several of a company's domains.
Allows an RP ID to be shared by listed sites so passkeys follow brand domains. Limited labels prevent abuse.
What it can and can't do
What the user does: Nothing extra. It happens when you use a passkey on any of that company's sites
It can
- Share one passkey across a short list of the company's own domains
- Let you sign in on a brand's country sites with the same passkey
It cannot
- Share your passkey with sites not on the company's list
- Add more than a small number of site names
- Work in older browsers that lack the feature
How it differs between platforms: Chrome, Safari and Edge support it. Firefox does not yet.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 67 | 2018-05-29 | None |
| Edge | Supported | 18 | 2018-10-02 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Supported | 13 | 2019-09-19 | None |
| Safari on iPhone | Supported | 13 | 2019-09-19 | None |
| Chrome on Android | Supported | 70 | 2018-10-17 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | https://{RPID}/.well-known/webauthn {"origins":[...]} |
| Browser compat keys | api.PublicKeyCredential |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Lets one passkey work across several of a company's domains.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
origins | list | None | up to 5 labels (eTLD+1 groups) in Chrome | Not listed |
Technical limits
- Chrome allows at most 5 labels
- Firefox still considering it
- Needs the file served on the RP ID domain
The story
What it is
One passkey can work across several websites owned by the same company.
For you
You create a passkey on one site and later sign in with it on the same company's other web addresses. You never notice anything except that it just works.
For makers
Large brands own many domains for different countries and products. This lets them use one passkey across them all and avoids making customers sign up again.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A game publisher with separate stores and regional sites lets a player's passkey work on all of them. | Epic Games |
| shopping | A retailer with country sites for each market keeps a shopper's passkey working when they travel. | Amazon, IKEA |
| media | A streaming company with brand domains for each service lets one passkey open all of them. | Disney |
| travel | A travel group with several booking brands sees fewer sign in drop offs. | None named |
| banking | A bank with separate login and mobile domains shares passkeys between them. | None named |
| security | A security team grows passkey use faster since customers do not need a new one for each domain. | None named |
Risks
- More domains in one trust circle
- Complex to set up safely
What the platform says
- web.dev (Google): Related Origin Requests. Google describes a way for one passkey to be used on several of a company's domains, such as country sites.
Good uses and abuse
Legitimate uses
- Brand sites sharing passkeys
Known abuse
- None notable
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025, Chrome 128: Related origins ships
- 2025, Safari 18: Safari supports it
Sources
How well checked: Based on official documentation.