I started fiddling with my alias service and started wondering what approach other people might take.
Not necessarily the best option but what do you prefer? What are the pros and cons you see with each option?

Currently I’m using anonaddy and proton, so I have a few options to create aliases.

  • The limited shared domain aliases (from my current subscription level)
    Probably the only option to not be tracked if it would be unlimited, I’d just have to pay more for the service.
  • Unlimited aliases with a subdomain of the shared domain
    For example: baked6863.addy.io
  • Unlimited aliases with custom domain.
  • Unlimited aliases with subdomain in custom domain.
    This is different from the one above since the domain could be used for different things, not dedicated to email.
  • Catch-all with addy.
    The downside I’ve read is people could spam any random word, and if then disabled the people that had an incorrect alias wouldn’t be able to communicate anymore.
  • Catch-all with proton.
    Since proton has a limit on how many email addresses you actually have, so when you receive an email to an alias and want to replay to it you’ll be doing it from the catch-all address instead of the alias.

What do you think?
What option would you choose?

  • jetAEnglish
    1·
    9 months ago

    Custom email domain name, plus sub-domains. and a catch-all email address that goes to one mailbox.

    So service@lowurgency.domain.name and service2@highpriority.domain.name

    I have it setup if I reply to a email, it comes from the address the email was sent to.

    Very convenient. So far I’ve only had to block the xfinity email address, because they had a leak and it started to get spam.