Skip to content

Pham

My feedback

1 result found

  1. 1,516 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Pham commented  · 

    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

Feedback and Knowledge Base