Similar branding does not make passkeys interchangeable. Use requires the same relying party ID, a permitted domain rather than a display name. An allowed parent domain can serve that role; subdomains are not necessarily isolated.
Separate the address from the artwork
Imagine two fictional reading-library posters. Both show a blue book, the words “My reading shelf”, and a familiar-looking account button. One prints library.example; the other prints library-example.test. Neither address is a recommended service or a link to visit.
On paper, cover both logos and copy the addresses into separate rows. Circle the hyphen and underline each ending. This simple comparison produces a specific observation: the printed addresses differ. It does not identify either poster's owner or prove that either service is trustworthy.
Hypothetical library account comparison
| Screen shown | Passkey scope | Example interpretation |
|---|---|---|
| library.example | library.example | Matching ID; other checks still apply |
| library-example.test | library-example.test | Different ID from the first row |
| reader.library.example | Depends on the permitted ID | Not determinable from branding alone |
The table is a fictional comparison, not a browser diagnostic. Its third row deliberately leaves information unresolved. Keep that uncertainty visible instead of completing the cell from the appearance of the poster. Label each copied observation with its row number so a later discussion does not accidentally combine details from different posters.
What to do when the prompt does not match
Suppose the reader intended only to reopen saved notes. Write that purpose beside the comparison before responding to any new invitation. Do not create a replacement credential just to dismiss a mismatch or enter a device PIN into an ordinary webpage.
Return through an independently known bookmark. Keep a brief note of the unexpected wording, without passwords or codes, for a later explanation through an established support channel.
For the technical definition of the permitted relying party ID, see MDN’s PublicKeyCredential creation options reference.
Responsible entertainment note: This article is for screen reading and risk awareness only. It does not provide betting advice, account service, payment handling, outcome prediction or any guaranteed result.