[92698] in North American Network Operators' Group
Re: [Fwd: Important ICANN Notice Regarding Your Domain Name(s)]
daemon@ATHENA.MIT.EDU (Alexander Harrowell)
Thu Oct 5 08:22:51 2006
Date: Thu, 5 Oct 2006 13:22:01 +0100
From: "Alexander Harrowell" <a.harrowell@gmail.com>
To: "Joe Abley" <jabley@ca.afilias.info>
Cc: "Steve Sobol" <sjsobol@justthe.net>,
"Chris Stone" <cstone@axint.net>, nanog@nanog.org
In-Reply-To: <279A4962-FE61-42DB-9B29-57CFDAD016B5@ca.afilias.info>
Errors-To: owner-nanog@merit.edu
Are you sure it's genuine? Those WWD domains (especially
secureserver.net) account for a large fraction of the spam and
phishing attempts I receive.
On 10/5/06, Joe Abley <jabley@ca.afilias.info> wrote:
>
>
> On 4-Oct-2006, at 19:04, Steve Sobol wrote:
>
> > ICANN *does* have a requirement for accurate information in WHOIS and
> > while I don't know how strongly the requirement is enforced, they
> > *can*
> > pull your domain registration if you don't have accurate information.
>
> While I'm not familiar with the precise enforcement mechanisms or
> policy, I do know of one ISP who had the delegation for their (.com)
> domain name unexpectedly pulled by the registry in response to a
> complaint about inaccurate whois information directed at ICANN.
>
> It was painful for the ISP, especially since it happened during the
> time that Verisign's sitefinder was live, which caused e-mail to ISP
> customers to be hard bounced from Verisign and people looking for
> their web page to be presented with a "this domain is not registered"
> page instead of a browser error.
>
> It's well worth avoiding, even without the additional sitefinder
> complications :-)
>
>
> Joe
>
