Post by @taco_shale032@lemmy.ml

2026-10-25 01:17 UTC

I actually used to use service@domain.tld but decided to switch because of a few reasons. Using the name of the service as username can make it obvious it’s an email aliases and also that the domain is (probably) used by a single person. In addition to that, from a security standpoint it may make it easier for bad actors to get access to your accounts because the email address reveals which service it belongs to. Depending on your threat model, it’s worth considering something-random@domain.tld instead.

Replies (3)

@rollin@piefed.social 2026-10-25 04:47

Don’t you think you’re overthinking it? Or did any of your reasons ever come true, so to speak? When would it be a problem if someone deduces that your email domain is your own personal one? For your other point, do you mean that someone gets access to your email - they actually break into your inbox. If they see you have a mailbox called service@domain.tld, they’ll know that’s going to be the signup you used for service.com. Is that what you’re referring to? Doesn’t seem like a big cause for concern to me, so am I missing something?

Open ##5234616
@davidagain@lemmy.world 2026-10-25 08:13

Most spammers aren’t reading the list of emails and thinking about it, they’re buying a huge list of emails and spamming them unthinkingly.

Open ##5236492
@user224@lemmy.sdf.org 2026-10-25 11:48

and also that the domain is (probably) used by a single person Currently I am just going with namesurname.tld. If they already know who I am, it doesn’t show anything extra. If it’s something I don’t want linked to me that easily, I can just give it e-mail on some shared domain, and change it later if needed. Though that removes the easy portability. I’ll probably have more domains eventually.

Open ##5238845