> bdn> I see several mentions of "[EMAIL PROTECTED]" > > bdn> I know there are thousands of domains using this. I suggest we all report > bdn> all of the ones we find to ICANN to keep fuel on the fire. > > Just a note of caution here since it is the domain owners who may get the > shaft in the end.
Only if the domain registrant refuses to provide valid information to the registrar when asked by the registrar. The issue we are dealing with here is a registrar ignoring their obligation to seek out valid data when they are informed of the problem. > I have been working with one of our customers to transfer > their domain to us from Verisign. They have a WHOIS email that shows the > [EMAIL PROTECTED] The problem is that when they log in to their > Verisign account, the email information is correct but it is not updating > the WHOIS. I'd hate to see the domain owners somehow caught up in this when > some of them may be trying to do the right thing. This is a different issue. You should first contact Netsol about the problem and keep detailed logs of all communications. If Netsol does not resolve the problem in a resonable time period, then submit a Registrar Problem Report at http://www.internic.net/cgi/registrars/problem-report.cgi > Some may guess the reason they do this is to prevent transfers away since > there is no valid email address for the admin contact for the gaining > registrar to send the transfer authorization to. They have been using [EMAIL PROTECTED] for a long time. Way before ICANN and "deregulation". It prevents registrar transfers today *and* makes it very difficult (both pre-ICANN and now) for a registrant to use their domain with non-Netsol hosted web and e-mail services.
