Using a catch-all domain is a mistake
notcheckmark.com
Using a catch-all domain is a mistake
1–10 of 304 posts
Re: Using a catch-all domain is a mistake
#2I try to disguise it a little to avoid the awkwardness, and also put the recipient into the subdomain instead of sender name. For example for grubhub I'd do:
me@grb.mydomain.com
No need to remember anything because it's all in a password manager. I've found this worthwhile, already blocked a couple spammers.
You could also go with something fully random, you still get the same benefit. It's easy to look in your email history and see what you originally used the email address for. Password manager obviously required though.
Re: Using a catch-all domain is a mistake
#3reminds me a bit of the family member who owns firstname@lastname.com and can't get random non technical people to believe that their email address domain really is lastname.com
"but don't you mean at gmail.co..."
no
Re: Using a catch-all domain is a mistake
#4I do this and my biggest regret is that I cannot easily check haveibeenpwned.com to find out if any of the accounts have been breached.
Re: Using a catch-all domain is a mistake
#5I do this and my biggest regret is that I cannot easily check haveibeenpwned.com to find out if any of the accounts have been breached.
Yes you can: https://haveibeenpwned.com/DomainSearch
Re: Using a catch-all domain is a mistake
#6I do this and my biggest regret is that I cannot easily check haveibeenpwned.com to find out if any of the accounts have been breached.
You can authenticate whole domains and see whenever anyone at your domain is listed.
Re: Using a catch-all domain is a mistake
#7Re: Using a catch-all domain is a mistake
#8I have a variation that I use for online sign-ups only. I have to explicitly declare the alias before using it. So it’s relatively easy to check which ones I have used in the past (and the name tells me which site I used it for) and I can easily “revoke” by removing the alias. I can’t really use it when asked for an email address at a store, for example - but it doesn’t happen that often (going to real stores, I mean :) )
Re: Using a catch-all domain is a mistake
#9I've been using email aliases for over a decade and have never experienced the leading examples the author mentions. Although I already have email accounts setup for impromptu scenarios, setting up an email alias in one minute is easy enough.
Re: Using a catch-all domain is a mistake
#10reminds me a bit of the family member who owns firstname@lastname.com and can't get random non technical people to believe that their email address domain really is lastname.com "but don't you mean at gmail.co..." no
I've been using firstname@lastname.com for ages and this doesn't happen to me. Usually it's "huh that's neat", but I also have a very unique last name