Skip to Content
Platform.Ontology

WebAuthn Related Origin Requests

Lets one passkey work across several of a company's domains.

Works without askingSign in and identityWebAuthnWeb browsersWhile you use it

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

BrowserStatusFirst versionReleasedNote
ChromeSupported672018-05-29None
EdgeSupported182018-10-02None
FirefoxNot supportedNot availableNot listedNone
SafariSupported132019-09-19None
Safari on iPhoneSupported132019-09-19None
Chrome on AndroidSupported702018-10-17None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APIhttps://{RPID}/.well-known/webauthn {"origins":[...]}
Browser compat keysapi.PublicKeyCredential
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsPer origin
How to take it backSite settings
Inside an iframeSame as top level; cross-origin iframes need a permissions policy where listed

Typical flow

  1. Call the API
  2. Browser applies its access rules
  3. 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

FieldTypeUnitRangePrecision
originslistNoneup to 5 labels (eTLD+1 groups) in ChromeNot 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

TypeExampleApps
gamesA game publisher with separate stores and regional sites lets a player's passkey work on all of them.Epic Games
shoppingA retailer with country sites for each market keeps a shopper's passkey working when they travel.Amazon, IKEA
mediaA streaming company with brand domains for each service lets one passkey open all of them.Disney
travelA travel group with several booking brands sees fewer sign in drop offs.None named
bankingA bank with separate login and mobile domains shares passkeys between them.None named
securityA 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

Good uses and abuse

Legitimate uses

  • Brand sites sharing passkeys

Known abuse

  • None notable

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough 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.

On this page