- Impact
- 2,959
*
As we all know, the whois email address is a major vulnerable spot in the whois data base, particularly the email sign-in point.
In your opinion, what are some pros and cons of setting up a catch-all email address?
My idea: to set up a whois email address that is different from my sign-in user ID.
For example, the whois address would be [email protected], but the actual sign-in ID would be "secret," something like [email protected] (I wouldn't be using the sample sign-in ID--too obvious) .
Is this a good or bad idea?
Or would it be a better idea to bite the bullet and buy an email service that offers more than one sign-in addresses, but not the scary catch-all email?
Thoughts?
*
As we all know, the whois email address is a major vulnerable spot in the whois data base, particularly the email sign-in point.
In your opinion, what are some pros and cons of setting up a catch-all email address?
My idea: to set up a whois email address that is different from my sign-in user ID.
For example, the whois address would be [email protected], but the actual sign-in ID would be "secret," something like [email protected] (I wouldn't be using the sample sign-in ID--too obvious) .
Is this a good or bad idea?
Or would it be a better idea to bite the bullet and buy an email service that offers more than one sign-in addresses, but not the scary catch-all email?
Thoughts?
*















