Why doesn't LastPass recognize my equivalent domain as a valid domain?
If you have a single account shared across multiple domains, you can use LastPass to set those sites up as equivalent domains so that you do not have independent site entries for each stored in your vault.
- Both domains and subdomains can be entered by a LastPass user (e.g., sample.com and services.sample.com, respectively)
- All subdomains and paths are considered equivalent automatically by default (e.g., services.sample.com where "services" is the subdomain)
- To mark subdomains as having the same login credentials in LastPass, specific syntax is required. You must enter "=" directly before the subdomain, then enter a space after the domain, then enter a comma, then enter another space (e.g., =services.sample.com , login.lastpass.com)
- Top-level domains (TLDs) are not accepted and will be considered as invalid (e.g., *.com)
Please note that certain domains function both as a regular domain and as a TLD for other domains. Even though those other domains may look like subdomains, they are in fact different services and websites. In those cases, the service's domain will be considered a TLD, which is an invalid domain.
|Domain Examples||Equivalent or Invalid||Reason|
|askubuntu.com, mathoverflow.net, serverfault.com, stackapps.com, stackexchange.com, stackoverflow.com, superuser.com||Equivalent||You use the same account for logging in to those domains|
Top-level domains (*.com) are not accepted as you would not want LastPass to offer using your Google credentials for all domains ending in ".com"
|fabrikam.com, services.fabrikam.com||Invalid||services.fabrikam.com is already considered equivalent because it is a subdomain of *fabrikam.com|
|tesla.com, teslamotors.com||Equivalent||You use the same account to log in to both domains|