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

This idea is along the same lines as:

https://protonmail.uservoice.com/forums/953584-proton-pass-authenticator/suggestions/47012971-domain-url-matching-rules?page=1&per_page=20

I would like to request a feature enhancement related to autofill rules:

✅ Request

Enable login/item identifiers that can match:

Something other than a full URL beginning with https://

URL fragments or patterns using regular expressions (regex)

Elements targeted through custom selectors

📌 Practical example

I frequently have to enter license/API keys on various websites.
Even though the domains differ, they share the same URL structure — for example:
setting-api.php

I would love Proton Pass to detect this and automatically fill in a custom field such as:

<input name="api-key" value="xxxxxx">

it would be possible by setting a value like input[name="api-key"]

🔎 Reference

Bitwarden has provided a similar feature for a long time, allowing regex-based matching and CSS-like selectors for field mapping.
This is genuinely the only feature I miss after migrating to Proton Pass.

Thank you for considering this improvement. It would greatly streamline workflows for users managing license and API keys across multiple sites.

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.

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

still nothig?? is really pretty annoying

Why has this not been implemented yet? Over 1400 votes

I still cannot leave bitwarden until this is implemented.

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.