At the very least proton pass should be able to differentiate between subdomains.

This is a must have - considering going back to bitwarden. But otherwise Protonpass is excellent!

Any news on this?

UP Please, i really need this for my business...

Why isn't this fixed yet? This should have been in version 0.001 alpha.

God, nearly 3 years later, still not there... I'm not a developer, but is this so complex to implement, I mean, filtering the passwords by the full URL instead of the main domain only should be basic no?

Agreeing with @Nick. I was close to pulling the trigger on purchasing a Proton Premium subscription, but the lack of this specific feature is holding me back and keeping me on Bitwarden for now.

Ready to purchase as soon as this is a feature. Even just a partial implementation of hostname matching would be huge. During my testing I get 40+ login options each time I visit something in my homelab :(

And do not forget to match per port as well!

I think that pattern matching (wildcards, regular expressions) would be very convenient.

One of the main reasons why I cannot switch from 1password.

We need absolutely this feature ! @Proton, come on please ! 🙏

I regret the move from Dashlane to Proton. This one is extremely annoying

This is actually a blocker for me to move from Bitwarden to ProtonPass

Comment for Proton Pass Feedback Thread (“Domain URL Matching Rules”)

As an active Proton ecosystem user running a self-hosted domain (e.g. example.net), I can confirm that the current substring-based URL matching in Proton Pass severely limits usability for anyone who uses their own domain for both email and internal services.

Example:
All of my logins use @example.net as the username, and I host services like
nextcloud.example.net, grafana.example.net, and truenas.example.net.
When I visit any of those sites, Proton Pass lists every vault item containing “example.net” anywhere in the record — dozens of unrelated logins — instead of only the one matching subdomain. This makes the extension nearly unusable for homelab or enterprise setups.

What’s needed:
Proton Pass should implement configurable domain-matching rules, just like Bitwarden and 1Password:

Exact host match (grafana.example.net)

Base domain match (*.example.net)

Starts-with / wildcard (service*.example.net)

Regex (for advanced users)

Multiple URLs per credential

This would allow Proton Pass to support professional and self-hosted use cases while maintaining strict security boundaries between services. It’s also essential for organizations that share a common apex domain across many logins.

Until Proton supports per-entry match modes, anyone with a homelab or corporate domain faces an autofill list so long it borders on unusable.

“Let all things be done decently and in order.” — 1 Corinthians 14:40, KJV
Precise domain matching is the digital equivalent of order. Please prioritize this improvement soon.

— A long-time Proton user and self-hoster

Baffled this isn't already a feature. I'm finding posts about this (and CS responses) from over 2 years ago.

I come from keepass and this is a must have. Without more flexible matching rules I see too many accounts for a given domain and picking the correct one is a pain.

Same as Justin below, I also have a home lab and tons of services, each with different logins. Having a way to match urls would be really useful

Adding my vote. This is a really important feature for professionals and home labbers. Without a "starts with" or similar rule, you can have dozens of accounts show up for everything under a domain.

Any update on this? It was marked as under review over a year ago and there hasn't been an update since then.

This is a critical feature for me and I can't switch to Proton Pass until it is implemented.

I really do love proton pass and migrated from dashlane (initially caused by pricing but I was already using proton mail so it only made sense). However the lack of this feature is really becoming a pain. I do a lot with my homelab and I use a specific domain for tons of internal services, and not being able to properly handle all of these logins for all of the subdomains is becoming a huge issue.