emailprovider.com

Bank account created with my email... do I need to worry? Hello, I'm hoping I can get some insight on if you think this might be actual identity theft or just someone who is really not tech savvy and maybe some advice on what to do next. For some context: I do have a SSN but I don't think I've ever used it in anything other than my passport application. I've never lived, worked or owned any bank accounts in the US. For the last several years I've been dealing with random people who share my name using my email address (which happens to firstname.lastname@emailprovider.com) to sign up for different accounts or as their contact info for service providers. I know they are different people since I end up getting varying degrees of personal information so I can end up seeing they are from a different state, have different middle names and such. Since they've all been from the country I'm currently living in and have used their actual full names when signing up for whatever I've chalked them using my email address as them being tech challenged, trying to look more professional on paper or a mistake from the person transcribing the info. Annoying for me but not necessarily harmful. And yes, I've taken steps to secure my email account (regularly change password, complex password, 2FA, regularly check for open sessions). This was all well and good since these random accounts so far have been from people who are in the same country that I currently live in... however yesterday I received an email notification that a US online bank account had been opened by someone with my name and who had used my email address as their login. I've suspected one of the fake me was living in the US since one time I got an invite to join a Nextdoor App group and the address listed for the neighbor group was RandomName Drive. Now... I don't know if this person really doesn't care or doesn't understand that you should actually own the email address you use as your bank logging or are the

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.

Email account mobility, privacy and risk mitigation I'm posting this here as I can't think of a better suib. r/email have already deleted a thread I posted so I'm not sure, please feel free to redirect if needed. Here's my threadt model: \- I have a paid account with an email provider; \- I purchased / rented my own custom domain (xxx.org); \- my email address is [first.last@emailprovider.com](mailto:first.last@emailprovider.com); \- I've been using [first.last@emailprovider.com](mailto:first.last@emailprovider.com) for 4 years as my email contact and login for well over 150 various services; \- I've created TEXT and MX recods at [emailprovider.com](https://emailprovider.com) to point to my customer domain so I receive both emails sent to [emailprovider.com](https://emailprovider.com) and xxx.org; \- I want to mitigate the risk of my email provider going bust and me having to find a new provider / and changing the email address linked to my 150+ logins across the Internet; \- I want to mitigate vendor lock-in and be free to move to a different email provider with as little fuss as possible. \- Do I need to modify my credendials on all services where [first.last@emailprovider.com](mailto:first.last@emailprovider.com) is present to reflect [xxx.org](https://xxx.org) instead? \- By giving away [xxx.org](https://xxx.org), does it not defeat the purpose of being privacy-conscious in the first place? \- I also create a few aliases on SimpleLogin.