I recently was trying to create and add a passkey for a site that I had an existing entry in EnPass. Normally when I do this, it offers to add the key to the existing entry. However, recently I had a site where this wasn't occurring. It kept offering to create a new entry instead of offering to add to the existing entry. It turns out that the URL I had in the existing entry was just example.com instead of www.example.com. Once I added the www to the front of the URL, then it finally offered to add the passkey to the existing entry. In my opinion, if only the domain is in the URL field, it should offer to add a passkey to that entry even if it's from a subdomain. I imagine detection to offer a passkey to a site might also be based on this logic, although I have not tested and confirmed.

Also, there should be a way to merge two entries. For example, once or twice (including this time) I accidentally created a new entry for a site when adding a passkey instead of adding to the existing entry. I should be able to merge the two entries so that the passkey is added to the entry that already existed.

Sorry forgot to mention I am on the Windows Store Enpass version 6.11.1 (1700) running in Windows 11 23H2 and using the Enpass extension in Microsoft Edge.

You're correct that the URL matching logic in Enpass currently distinguishes between different subdomains, such as example.com and www.example.com. This can sometimes lead to the creation of a new entry instead of adding the passkey to an existing one. Your feedback about treating subdomains as part of the same domain for passkey assignment is valuable, and I'll pass it along to our development team for consideration.

SI-3947

Thank you.

It is now March 2026 and I am still experiencing the same issue.

OS: macOS Tahoe 26.4
Enpass: 6.11.19 (from the Mac App Store)

An example site would be ebay.com

A new passkey is generated every time. It’s not down to the website either; it works perfectly with Apple Passwords / the Keychain. So it’s definitely down to Enpass.

My overall conclusion: Unfortunately, you can’t use passkeys properly with Enpass! A real disappointment.

1 hour ago, JayDoubleYou said:

It is now March 2026 and I am still experiencing the same issue.

OS: macOS Tahoe 26.4
Enpass: 6.11.19 (from the Mac App Store)

An example site would be ebay.com

A new passkey is generated every time. It’s not down to the website either; it works perfectly with Apple Passwords / the Keychain. So it’s definitely down to Enpass.

My overall conclusion: Unfortunately, you can’t use passkeys properly with Enpass! A real disappointment.

The same thing happened to me, so I created a passkey by scanning the QR code for nearby devices and finished the process using the Enpass iPhone app.

Perhaps the latest version 6.11.20 has fixed this behavior?

Thanks for pointing out the newer version. It didn’t appear for me. I had to open Enpass in the App Store specifically for the ‘Update’ option to show up. There was nothing under the ‘Update’ menu.

I have now installed version 6.11.20.

The behaviour remains the same. The password dialogue box appears where Enpass inserts the password and does not offer a passkey. After logging in, the dialogue box appears stating that a passkey can be created.

So no change. Logging in with a passkey is not possible and a passkey has to be created every time.

Oh, that's a shame. Apparently, the "Sign in with passkeys across related domains" in the update notes refers to a completely different context.

Thanks for the update.

On 3/28/2026 at 11:39 AM, JayDoubleYou said:

The password dialogue box appears where Enpass inserts the password and does not offer a passkey. After logging in, the dialogue box appears stating that a passkey can be created.

Passkey login has to be requested by the site. Enpass can't just offer it. If the website only shows a password login form and then wants to create a new passkey, that's the websites fault.