Privacy Guides

Yes absolutely. It gives you a sense of ownership and nobody can shut you down.

You're also more flexible as in you can email providers very easily by simply pointing your domain DNS to a new one. With an @gmail for example, you're stuck with Gmail. If I'm @example.com and want to swap to Tutanota from Protonmail, I can just change my DNS settings to the new provider and people can still email the same domain.

It also lets you stand out and I think it makes me look more professional on resumes. If your provider is properly set up, then the spam issue is non-existent, so I also highly recommend not to self host your own email.

You need to be careful and pick a reputable TLD though. For example, .top domains are free which also means a ton of scammers and bad folk use it, so it easily gets flagged for spam. I pay $15/yr for my .dev TLD which is ran by Google so it's reputable. Also they have a special requirement for .dev domains which require to be https and blocks http on the domain level, which I find to be a security advantage and absolutely agree with.

I also have a wildcard domain so I can come up with emails on the fly. If you still want to sign up with things anonymously and not have your domain stick you, then you can use a private email forwarder like AnonAddy.

Yes, it's very useful.

I have my own domain, which I use with a service called AnonAddy. It allows me to generate unlimited unique emails on-the-go, which I can then toggle off if spam starts coming in.

I use a unique email for every single service I sign up to.

Now, you are able to do this without a custom domain, but then you are putting all your eggs in one basket, and if the domain(s) you used for signing up, suddenly aren't being renewed, you will lose access.

Thats why I have my own domain for this. If AnonAddy goes out of business, I can just take my domain, and all my aliases, to another service, such as SimpleLogin for example.

Privacy Does Not Equal Anonymity.

Yes; having anonymity does confer some level of privacy, but it is not the only means of having privacy.

Now let's peek at the advantages:

• You own the domain.
• You can host your own mail exchange (MX), configure it the way you want and host it anywhere that will permit you to send and receive emails. Point the DNS record(s) at whatever MX server(s), that allow it, that you want. Personally I use Tutanota for my inbox and SimpleLogin for my junk aliases..
• You have control over where your mail gets routed. By DNS records; you can do a lot of things and point your emails in directions that avoid restrictive networks or unwanted relays as well as securing that route too; ensuring that no one can quietly redirect your mail elsewhere. I use Njalla for my domain.
• You have control over who hosts your inbox. This allows you to swiftly change mailbox or hosting providers without losing your long used email addresses.
• You aren't sharing a domain with many users; which usually means fewer issues with email deliverability due to spam and abuse. Once your domain gains a positive reputation as a small-time email provider; most email services Will accept sent emails even if junk filters do not. Your recipients have an easy way to whitelist your entire domain.
• Your email will receive less spam overall.

Some disadvantages may include:

• Your domain will be aggressively filtered as junk by most Aggressively Configured Junk Filters.
• Your emails may be occasionally rejected by certain email providers with aggressive anti-junk configurations and applications deciding who they will receive from at the MX level.
• Your emails may be easy to snoop on at the network level; as they will have an identifiable domain on the envelope and will be primarily routed to a specific host. This is problematic if you or your mailbox provider don't force remote mail servers to use TLS encryption.
• Your domain may be abused or spoofed for spam if you do not configure your DNS and MX settings correctly. (Use DKIM so remote servers can tell if another server is spoofing your domain)
• You will be 100% responsible for all mail that is sent; or appears to be sent by your domain name. This includes all spam that spoofs your domain name; therefore you must USE DKIM to mitigate it.
• You must properly configure everything. If you misconfigure it; the remote servers will notice that and REJECT all of your emails that are sent out.
• You may need to maintain your own MX (mail server) and host that if you choose to do so. This comes with additional performance and administration burdens. Double them if you allow anyone else to use your domain as an email address; because you are now responsible for their conduct as well.

Have one. My email address is [email protected]. I work in tech so it really seems to generate the right impression on my resume.

It’s a great option, but it’s debatable whether or not it’s privacy improving. On one hand it’s your domain. You don’t need to worry about moving email services, and as you control it, you can have as many addresses as you want. One for each service, catch all, and so on. On the other hand it’s YOUR domain. Only you have access to it. It’s quite easy to filter out the first part, before the @ sign, and identify exactly who you are. It’s a unique data point, tied to you. It’s arguably as bad as handing out a phone number.

I used to use [email protected] (The benefits of having a rare last name), but I found that the work behind managing the email server myself wasn't worth it. I could probably have outsourced the hosting and spam filtering to Google or the likes, but then I might as well use my [email protected] address.

I use Cloudflare email routes. I make one address for each service and all of them forward to a managed email address. It's great that I can just turn them off when I don't wish to receive mail anymore.