Just to update on my previous entry. When I last checked you will recall that the domain whois had changed to an Enom placeholder.
Shortly after this I received another email alert from my script to tell me the domain whois had changed again. It had returned to the ‘Domain not found: Code FW-1’ which surely indicated something was afoot. Hoping for the name to be dropped, I was dissapointed to find that it eventually changed to the following (modified to omit domain name):
Administrative Contact:
Whois Privacy Protection Service, Inc.
Whois Agent (vrcnpthfc@whoisprivacyprotect.com)
+1.4252740657
Fax: +1.4256960234
PMB 368, 14150 NE 20th St – F1
C/O domainiwanted.com
Bellevue, WA 98007
USTechnical Contact:
Whois Privacy Protection Service, Inc.
Whois Agent (vrcnpthfc@whoisprivacyprotect.com)
+1.4252740657
Fax: +1.4256960234
PMB 368, 14150 NE 20th St – F1
C/O domainiwanted.com
Bellevue, WA 98007
USRegistrant Contact:
Whois Privacy Protection Service, Inc.
Whois Agent ()Fax:
PMB 368, 14150 NE 20th St – F1
C/O domainiwanted.com
Bellevue, WA 98007
USStatus: Locked
Name Servers:
dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.comCreation date: 23 Feb 2009 17:25:00
Expiration date: 22 Feb 2010 11:00:00
After some more investigation, I have found that ‘Whois Privacy Protection Service, Inc’ is the Whois protection service offered by Enom for $6/year. So if you ever see a whois record like this, it has definitely been registered through Enom.
So the existance of the record is either a handy pseudonym for some cowardly domainer who snaps up his domains via Enom, or is in fact Enom itself using insider information to snag and slap adverts on prospective domains while wishing to hide the fact they engage in such contemptible practices. I put the probability of it being one of these at 50/50.
So, it looks like my half-desired name is gone, at least for a year. While it might be annoying I still won’t explicitly state which domain it was, simply to deprive whomever now owns of it of those few curious hits it would get as a result.
2 replies on “Acquiring an expired domain name II”
I found this blog post by googling for ‘Domain not found: Code FW-1’. This is at the bottom of a ‘pendingDelete’ domain I am interested in, also through eNom. I only just registered the .net a couple of weeks ago and had been following the corresponding .com domain. It stayed in “redemption period” for something ridiculous like 2 months since the previous owner had let it expire.
A couple of days ago I started get spammed by services who wanted to charge me up to $199 to back order the domain, so I called eNom themselves. While they can’t back order it they referred me to namejet.com but lo and behold I believe they are the same company. Well at least they don’t want $199 but only $69, and I presume since they are the controlling registrar I should have an almost certain lock on this back order unless I’m outbid.
I will keep you posted. If somehow I don’t get the .com domain I’m going to trademark the 6-letter portion preceding the .net and .com. It will also be demonstrable that I owned the .net before whoever the latest owner of the .com might be.
Well its now registered through snapnames. What a bunch of baloney