2 ms·

You are not explaining how different email addresses can be cross-referenced with a custom domain or how spammers can guess additional emails to reach you. Use

You are not explaining how different email addresses can be cross-referenced with a custom domain or how spammers can guess additional emails to reach you. Use a subdomain then for your email aliases. The risk of leaking personal information via a domain is the same risk as giving your real name when you signup for a service, or use your real name when you send emails. Most registrar solutions have a proxy WHOIS and if someone serves a court order to get your real name they are just as likely to get it from your registrar as they are a third-party company. Losing a custom domain is about as risky as picking a shady registrar, doing illegal things which will get you banned from an alias service if they are getting subpoenaed about your illegal stuff, or not paying your bill. I still think it is inherently better than an regular alias domain which is much more likely to get blacklisted than a custom domain.

Vinnl 5y ago
> You are not explaining how different email addresses can be cross-referenced with a custom domain or how spammers can guess additional emails to reach you. Oh sure, I can do that! So for me, one reason to use aliases is to be able to trace who leaked my email. However, it's pretty obvious if my email address is news.ycombinator.com@mydomain.com, that everything @mydomain.com is going to me. (And possibly, but I'm not an expert on this, if you use a service that handles that for you, it might even be automatically detectable via my MX records?) And if you know that, you can both know that facebook.com@mydomain.com is also me, and that you can send me an email at whatever@mydomain.com to also reach me. Whereas if my email address is, say, sd4k23@mozmail.com, then you can't know my other random aliases, while I'm still able to see who I gave that email address to via the relay.firefox.com dashboard. > The risk of leaking personal information via a domain is the same risk as giving your real name when you signup for a service, or use your real name when you send emails. Yep! I'm just saying that minimising the opportunities for me to make a mistake is a benefit. Note that I'm not saying you should switch to a service like this; I'm just trying to show why I've started using both: my custom domain for sensitive services, and Relay for one-offs/few-offs (e.g. if I just want to get a coupon code or something).
- encryptluks2 5y ago
  > And if you know that, you can both know that facebook.com@mydomain.com is also me, and that you can send me an email at whatever@mydomain.com to also reach me. SimpleLogin for a custom domain uses MX, SPF, DKIM, and DMARC records to help protect you. Yes, if someone does a reverse lookup they can detect that you are using the service, but if you are using an email forwarding service they can more easily detect the provider. I find it very rare for anyone to actually check the records. With their custom domain service you can also use a subdomain, so instead of polluting your bare domain, you can create a unique subdomain for email addresses. You can also use random aliases, so the addresses are not easily guessable (at all). > Whereas if my email address is, say, sd4k23@mozmail.com, then you can't know my other random aliases, while I'm still able to see who I gave that email address to via the relay.firefox.com dashboard. No, but then I know the entire mozmail domain is shared and so spammers will target it more frequently. > Note that I'm not saying you should switch to a service like this; I'm just trying to show why I've started using both: my custom domain for sensitive services, and Relay for one-offs/few-offs (e.g. if I just want to get a coupon code or something). I can agree there, if you are just creating temporary emails that you don't care if you lose then an alias-provider domain is fine. However, like most people the risk is that they either don't use an alias for other services that are more important or that they do and then the provider shuts down and they can't verify their account.

Vinnl 5y ago

> You are not explaining how different email addresses can be cross-referenced with a custom domain or how spammers can guess additional emails to reach you. Oh sure, I can do that! So for me, one reason to use aliases is to be able to trace who leaked my email. However, it's pretty obvious if my email address is news.ycombinator.com@mydomain.com, that everything @mydomain.com is going to me. (And possibly, but I'm not an expert on this, if you use a service that handles that for you, it might even be automatically detectable via my MX records?) And if you know that, you can both know that facebook.com@mydomain.com is also me, and that you can send me an email at whatever@mydomain.com to also reach me. Whereas if my email address is, say, sd4k23@mozmail.com, then you can't know my other random aliases, while I'm still able to see who I gave that email address to via the relay.firefox.com dashboard. > The risk of leaking personal information via a domain is the same risk as giving your real name when you signup for a service, or use your real name when you send emails. Yep! I'm just saying that minimising the opportunities for me to make a mistake is a benefit. Note that I'm not saying you should switch to a service like this; I'm just trying to show why I've started using both: my custom domain for sensitive services, and Relay for one-offs/few-offs (e.g. if I just want to get a coupon code or something).

encryptluks2 5y ago
> And if you know that, you can both know that facebook.com@mydomain.com is also me, and that you can send me an email at whatever@mydomain.com to also reach me. SimpleLogin for a custom domain uses MX, SPF, DKIM, and DMARC records to help protect you. Yes, if someone does a reverse lookup they can detect that you are using the service, but if you are using an email forwarding service they can more easily detect the provider. I find it very rare for anyone to actually check the records. With their custom domain service you can also use a subdomain, so instead of polluting your bare domain, you can create a unique subdomain for email addresses. You can also use random aliases, so the addresses are not easily guessable (at all). > Whereas if my email address is, say, sd4k23@mozmail.com, then you can't know my other random aliases, while I'm still able to see who I gave that email address to via the relay.firefox.com dashboard. No, but then I know the entire mozmail domain is shared and so spammers will target it more frequently. > Note that I'm not saying you should switch to a service like this; I'm just trying to show why I've started using both: my custom domain for sensitive services, and Relay for one-offs/few-offs (e.g. if I just want to get a coupon code or something). I can agree there, if you are just creating temporary emails that you don't care if you lose then an alias-provider domain is fine. However, like most people the risk is that they either don't use an alias for other services that are more important or that they do and then the provider shuts down and they can't verify their account.