Introduction

Here is an example of how Network Solutions contributes to the spam problem. Their private registration is unnecessary, and therefore was designed only to increase their revenue. And, it provides a haven for spammers by concealing their identity.

Note that Network Solutions has a long history of supporting whois abuse: see this Letter from Louis Touton to Bruce Beckwith Regarding Breach of VeriSign Registrar's Accreditation Agreement (Whois Data Accuracy).

One Example

My story starts with receipt of this spam message. The message even starts by acknowledging that it is spam.

I did a quick whois to find out what it said about forensicguard.com. Something really odd there: the administrative contact email address was xr8249n64uy@networksolutionsprivateregistration.com. I called Network Solutions Customer Service, and they verified that they started providing a private registration service about a week ago. I expressed my concern to the Network Solutions representative, who suggested that I email Network Solutions.

So, I did. Network Solutions responded that "deleting a domain name will rarely stop spaming activities." Whose side are they on?

I've had exasperating series of email exchanges with Network Solutions Customer Service, including responses from them that had nothing to do with the problem. And one response that says that they've given up on this issue. Well, I haven't, so I finally spoke with a supervisor who said that it will be escalated.

Update as of late 8 January 2004: After nearly a week, some progress: forensicguard.com is no longer a private registrant. Their (alleged) contact information is now available through whois. The domain is still valid; so, they had little to lose by spamming. Network Solutions still provides them with their domain name, DNS, and hosting service.

How Network Solutions Encourages Spammers

Here's what I learned from this example:
  1. Network Solutions doesn't think that shutting down spammer's domains will stop them.

  2. Spammers have nothing to lose by violating Network Solutions' Acceptable Use Policy. Network Solutions still provides services to forensicguard.com, even after that registrant spams.

  3. Network Solutions recently set up a private registration facility, and provided the networksolutionsprivateregistration.com domain for their registrants to hide behind. That includes spammers, of course.

  4. Always ask for a ticket number when speaking on the phone with Network Solutions Customer Service.

  5. Network Solutions Customer Service appears to cycle through canned responses. They offered me some that had absolutely nothing to do with the issue at hand. In one conversation on the phone, the representative assured me that Network Solutions was "researching the issue", after 1) she told me that she could find no record of it, and 2) I informed her that I had received a response from Network Solutions stating that they unable to assist me further.

Is Private Registration a Good Idea?

If properly implemented, I think that private registration would be a good idea: it would protect the contact information of domain registrants. DomainsByProxy appears to be off to a good start: they state how it works and how they handle abuse. Their contact phone numbers apparently go to a live person. They review First Class mail and, if a legal notice, forward to the domain registrant. Furthermore, they appear to take action against spammers; Aginet reported a problem with DomainByProxy's registrant super-offerz.com. As of early February 2004, that domain is in PENDINGDELETE status, i.e., shut down at least temporarily.

However, as currently implemented by Network Solutions, their private registration assists spammers.

Here's how: currently, inaccurate whois information is one reliable way to shut down a spammer. The way things work now, in practice, whois information need not initially be accurate. ICANN even acknowledges this in their Registrar Advisory Concerning Whois Data Accuracy of 10 May 2002:

Although 3.7.8 envisions that ICANN may develop a policy requiring registrars to verify the contact details at the time of registration, ICANN has not yet done so.
And I know, based on other examples, that Network Solutions does not verify whois information supplied by their registrants. As long as there was no abuse, a registrant need not, in practice, provide any useful contact information.

So what good is whois? If anyone reports an inaccuracy to the registrar, it must take reasonable steps to correct, according to Section 3.7.8 of the ICANN Registrar Accreditation Agreement:

3.7.8 Registrar shall, upon notification by any person of an inaccuracy in the contact information associated with a Registered Name sponsored by Registrar, take reasonable steps to investigate that claimed inaccuracy. In the event Registrar learns of inaccurate contact information associated with a Registered Name it sponsors, it shall take reasonable steps to correct that inaccuracy.
Finally, Section 3.7.7.2 of the ICANN Registrar Accreditation Agreement states that breach of the registration agreement is a basis for cancellation of the domain name:
3.7.7.2 A Registered Name Holder's willful provision of inaccurate or unreliable information, its willful failure promptly to update information provided to Registrar, or its failure to respond for over fifteen calendar days to inquiries by Registrar concerning the accuracy of contact details associated with the Registered Name Holder's registration shall constitute a material breach of the Registered Name Holder-registrar contract and be a basis for cancellation of the Registered Name registration.
Network Solutions' current implementation of private registration encourages spammers by removing this process for cancelling of domain registration.

How Can I Help?

Please let me know of any corroborating evidence that you have, such as spam from forensicguard.com or any other Network Solutions private registrant. Please include the words "private registration" in your Subject so that my spam filter doesn't snag it :-)

(To find out if a domain belongs to a Network Solutions private registrant, perform a simple whois search. If the email address of the Administrative Contact is at networksolutionsprivateregistration.com, then they are.)

Please let ICANN and Network Solutions know how you feel about Network Solutions' implementation of private registration.

Legislative Assistance?

Rep. Lamar Smith (R-Texas) introduced the Fraudulent Online Identity Sanctions Act (H.R. 3754) before U.S. House of Representatives on February 3, 2004. Its stated purpose is "to provide additional civil and criminal remedies for domain name fraud."


See my list of contributions to the fight against spam.

David Levine
2 January 2004
Last updated: $Date: 2004/11/18 14:42:50 $