Agreed, though i do think it’s a privacy thing. Many people use privacy and anonymity interchangeably but they are different things.
The options are:
- use a single email. If it is leaked you need to update hundreds of accounts or risk falling for a malicious email
- use a catch-all email and each service gets a separate email, but you can’t turn off receiving mail at a specific address unless you use a sieve filter. This doesn’t stop people from just guessing random addresses.
- use specific aliases for each service. Idk about this specific project but usually you can turn off receiving mail at an alias. So if a company gets a data breach i just change my email (or close the acct), then i turn off the old alias.
I did the catchall for a few years but have been doing aliases for 5+ now. In the end, the only people/ companies who have my email are the ones I want.
Yes. If you’re using lets encrypt then note that they do not support wildcard certs with the HTTP-01 challenge type. You will need to use the DNS-01 challenge type. To utilize it you would need a domain registrar that supports api dns updates like cloudflare and then you can use the acme.sh package. Here is an example guide i found.
Note that you could still request multiple explicit subdomains in the same issue/renew commands so it’s not a huge deal either way but the wildcard will be more seamless in the future if you don’t know what other services you might want to selfhost.