I have similar issue with third level domains. For me I need only option for exact match for domain additional to current behaviour.

Agreed - this is critical for homelab users. Won't somebody think of the nerds!?

I love the product - plz plz add this feature, guys 🙏🙏🙏

Any updates on this? I have a lot of services running on subdomains and it makes Proton Pass useless for signing in to these when there's 30+ entries in the dropdown

It's annyoing and insecure to use the clipboard to enter credentials.
I'm on my way to leave Bitwarden but this one makes ist really hard.

Still no movement on this? This is pretty wild. I want so bad to leave Bitwarden for Proton Pass, but every time I try, I realize that it's simply impossible to manage my logins without having fine grain control over domain matching.

Similar features were requested and acknowledged by Protonpass support team TWO YEARS AGO (Source: https://www.reddit.com/r/ProtonPass/comments/14mhv21/comment/jqlz94k/?)

It still has not been implemented. This should be a fairly simple thing to modify or add; I don;t understand why it's been years and we are still waiting for ONE of these services to offer this.

I am leaving 1Password the minute this comes out.

I will leave Bitwarden when Proton Pass offers this feature.

This needs to be in ProtonPass ASAP, can't really imagine how many people rely on multiple services hosted on the same domain. Surely can't be few.

Very surprised that this feature is not implemented yet.
Proton pass is almost unusable for any selfhoster that use subdomaines for services.

After switching everything from bitwarden and paying for proton pass I have also encountered this missing core-feature.

Very dissappointing for me ofc, however a wildcard/regex url matching in any password manager extension for in the browser is a MUST!

Can't make the switch without this feature.

At least, subdomain matching like 1Password should be available, as it significantly improves the user experience.

For a homelab, sub-domain or full string matching is a must!

Can't believe this is still under review for 2 years now.

For local service this is a critical update.

I am a new user of Proton pass and got all the way in before I found this problem. I was very enthusiastic about Proton pass up until I saw what was happening with the sites that use multiple subdomains (such as Chase). This feature alone is going to stop me from recommending Proton Pass to others.

Some way to restrict autofill behavior to a more specific URL (exact match maybe).

Currently, on sites that use Shopify, Pass can’t tell which website you’re logging into and every Shopify site shows up as an option.

Will not buy proton until this is implemented . 80% of my passwords , are for internal / company / self hosted or otherwise strange services, where at least the starts with is essential

As a user managing multiple subdomains under my primary domain, I find this feature essential. Currently, Proton Pass suggests ALL saved logins whenever I visit any subdomain — even though I use different credentials for each subdomain.

In Bitwarden, I could elegantly solve this issue using the "Host" setting, which ensured that only credentials specifically matching the visited subdomain would be suggested.

This functionality is critical for both security and usability. Without proper URL matching rules, I'm forced to select the correct password manually from a cluttered list every time, which is inefficient and error-prone.

The current behaviour creates unnecessary friction in my workflow and potentially introduces security risks if I accidentally select the wrong credentials.

Please implement this feature — it's indispensable for anyone with a structured login system across multiple subdomains!