5 ms·
As mentioned somewhere in this thread, using a custom domain poses other risks, in some cases more significant. All your aliases will be forever tied to your id
by dinglestepup 2y ago
As mentioned somewhere in this thread, using a custom domain poses other risks, in some cases more significant. All your aliases will be forever tied to your identity (and potentially de-anonymized by a single leak).
- tamimio 2y ago> All your aliases will be forever tied to your identity A separate domain can be used if really needed. But even with using my own domain, I don’t see it as a problem. After all, emails are not anonymous, and a leak with an alias with a custom domain is still meaningless and doesn’t affect other services.
- dinglestepup 2y agoMost domain registrars require providing identity details. Even if these details are private, a single leak or a config mistake on this domain will expose your real identity, tied to all aliases. With an alias service or a shared email provider you don't have this risk as you don't have to provide your real-life identity. So while it's tempting to use one random alias (h3hj4gjh234@yourdomain.com) for a high-risk service and another alias for a critical service (github@yourdomain.com), these aliases are easily identifiable as belonging to the same person.