Let’s all beat up Go Daddy!

I think it’s fair to say that Go Daddy is ending 2011 on a bum note.
A handful of competitors, notably Namecheap, are exploiting the recent outrage about the company’s support for the Stop Online Piracy Act (since recanted) to really stick the boot in.
NameCheap today called for December 29 to be marked as Move Your Domain Day and is currently sponsoring the hashtag #BoycottGoDaddy on Twitter.
It also said it will donate $1 to the Electronic Frontier Foundation for every domain transferred to it that day using the coupon code SOPASUCKS.
Other registrars are joining in with somewhat less gusto.
Dotster, for example, is offering cheap transfers with the discount code NOFLIPFLOP, a reference to Go Daddy’s changed position on SOPA.
So what’s the net effect of all this on Go Daddy’s business? It’s difficult to tell with much accuracy at this point.
NameCheap claims to have seen 40,000 inbound transfers in the last week, most of them presumably coming from former Go Daddy customers.
That’s going to be a difficult claim to verify however, even when December’s official gTLD registry reports are published a few months from now.
Unlike most ICANN-accredited registrars, NameCheap does not register domains directly — it has fewer than 200 .com domains under management, according to the most recent registry report.
The company started off life as an eNom reseller and appears to have never gotten around to migrating its customers.
(I wonder how many people transferring their domains this week are aware that some of their fees are probably flowing into the coffers of Demand Media, another popular internet hate figure.)
Several media articles have sourced DomainTool’s DailyChanges service for numbers of transfers out of domaincontrol.com, Go Daddy’s default name server constellation.
But as Andrew Allemann and Elliot Silver have already noted, those numbers are not a reliable indication of how many domains are being transferred from Go Daddy to other registrars.
Here’s a graph showing the transfers in and out of domaincontrol.com since the start of the month.

Transfers out briefly overtook transfers in this week, but by a negligible number.
The two big spikes you can see – both of which occur before the boycott began on December 22 – can be attributed to domainers (possibly a single domainer) moving thousands of domains from domaincontrol.com to internettraffic.com, a parking service, and back again.
Those movements had nothing to do with SOPA or the boycott, nor do they indicate that the domains were transferred away from Go Daddy. Name server changes != transfers.
Facts shouldn’t get in the way of a good story, however.
That’s probably why NameCheap seems to have got away with its insinuations about Go Daddy “blocking” transfers yesterday, which turned out to be highly questionable.
It transpires that transfers into NameCheap were failing not because of any nefarious activity by Go Daddy, but because NameCheap’s Whois queries were being automatically rate limited.
This was likely because NameCheap failed to white-list the IP addresses it uses for port 43 Whois look-ups either using ICANN’s RADAR tool or by notifying Go Daddy directly.
Registrar expert Jothan Frakes said as much on this blog yesterday, as did Michele Neylon of the unrelated registrar Blacknight on Twitter.
Go Daddy senior direct of product development Rich Merdinger suggested in a statement last night that NameCheap looked for the PR opportunity before picking up the phone:

Namecheap posted their accusations in a blog, but to the best our of knowledge, has yet to contact Go Daddy directly, which would be common practice for situations like this. Normally, the fellow registrar would make a request for us to remove the normal rate limiting block which is a standard practice used by Go Daddy, and many other registrars, to rate limit Whois queries to combat WhoIs abuse.

NameCheap has naturally disputed this interpretation of events, saying it had tried to get in touch with Go Daddy but received no response for 24 hours (Christmas Day, presumably).
Regardless of the he said/she said, the narrative in the media and on Twitter for the last couple of days has been pretty clear — Go Daddy: Bad, NameCheap: Good.
The SOPA story seems to have hit a nerve, and there are no shortage of pissed-off Go Daddy customers with horror stories to recount or just general criticisms of the company’s fairly brash image.
Warren Adelman picked a hell of a time to take over as CEO.

Whois throttling returns to bite Go Daddy on the ass

Go Daddy has been accused by a competitor of “thwarting” domain name transfers in violation of ICANN rules. (Note: story has been updated, see below).
The problem has reared its head due to the ongoing SOPA-related boycott of the company’s services, and appears to be related to Go Daddy’s decision earlier this year to throttle Whois queries.
NameCheap, one of the registrars that has been offering discounts to Go Daddy customers outraged by its recently recanted support of the controversial Stop Online Piracy Act, blogged today:

As many customers have recently complained of transfer issues, we suspect that this competitor [Go Daddy] is thwarting efforts to transfer domains away from them.
Specifically, GoDaddy appears to be returning incomplete WHOIS information to Namecheap, delaying the transfer process. This practice is against ICANN rules.
We at Namecheap believe that this action speaks volumes about the impact that informed customers are having on GoDaddy’s business.
It’s a shame that GoDaddy feels they have to block their (former) customers from voting with their dollars. We can only guess that at GoDaddy, desperate times call for desperate measures.

Part of transferring a domain from Go Daddy to NameCheap involves checking the identity of the registrant against Whois records.
Judging by a number of complaints made by Reddit readers today, it appears that NameCheap and other registrars are attempting to automatically query Go Daddy’s Whois database on port 43 at sufficient volume to trigger whatever throttling algorithm Go Daddy has in place to prevent the “harvesting” of contact data.
Go Daddy caused a similar ruckus earlier this year when it started blocking DomainTools and other Whois aggregation services from collecting full Whois records.
The registrar giant claimed then that it was trying to protect its customers by preventing the inappropriate use of their contact data.
However, while blocking a third-party information tool is merely annoying and disturbing, interfering with legitimate inter-registrar transfers could get Go Daddy into hot water, even if it is inadvertent.
NameCheap says it is doing the required Whois look-ups manually for now, and that it will honor each transfer request.
Giving Go Daddy the benefit of the doubt, I assume that this problem is ongoing largely due to the Christmas holiday, and that it will be rectified as soon as the appropriate people become aware of it.
Add this to your list of reasons .com and .net need a thick Whois.
UPDATE: All registrars have access to an ICANN service called RADAR, which enables them to specify the IP addresses they use to query competitors’ Whois databases.
Whitelisting IP addresses in this way could prevent a registrar’s queries being throttled, but not all registrars use the service.
According to this screenshot, NameCheap has not whitelisted any IP addresses in RADAR, which may be the reason it is having problems transferring Go Daddy customers’ domains to itself.

Saucy domain name commercials… in India?

By now everybody is familiar with attempts by American companies such as Go Daddy, and more recently ICM Registry, to make domain names appear sexy in TV commercials.
But did you know BigRock.com is doing something similar in India, where the boundaries of decency are even more strictly defined than in the US?
I just enountered BigRock’s YouTube channel for the first time, and I think it’s fair to say that its commercials are somewhat “edgy” too, at least as measured by Indian standards.
Here are a few examples.


It’s possible to pick up on some social commentary in some of the spots, even if you don’t speak fluent Hinglish.

Go Daddy to advertise .co at the Super Bowl

Go Daddy plans to advertise .co domain names during the Super Bowl broadcast for the second year in a row.
The company has bought two 30-second slots during the show, one of which will plug .co and will feature celebrity spokesmodels Danica Patrick and Jillian Michaels.
Scripts for both ads have been approved by NBC censors already, Go Daddy said.
It will be the eighth consecutive year the company has advertised during the inexplicably popular sporting event, which had a record-breaking 111 million US viewers this February.
The 2011 ad revealed Joan Rivers, her head spliced onto the body of a much younger glamor model, as the .co Go Daddy Girl.
I estimated at the time that .CO Internet took roughly 30,000 to 50,000 extra registrations due to the Super Bowl commercial.

Zip.ca lets zip.tv expire then files UDRP to get it back

The Canadian movie rental site Zip.ca, a sister company of Pool.com, has filed a cybersquatting complaint with WIPO over the domain name zip.tv.
A UDRP filed over a dictionary word would often scream reverse domain name hijacking, but it appears that in this case Zip.ca owned the matching .tv but accidentally let it expire.
According to historical Whois records, Zip.ca owned zip.tv until July 6 this year, when the registration expired and it went into its registrar’s “Reactivation Pending” status.
It was then acquired by a Chinese registrant, Mai Lifang, in October. The domain is currently parked.
It’s embarrassing for Zip.ca, given that its parent, Momentous, is primarily a domain name company, owning DomainsAtCost.com, Pool.com, Internic.ca, Rebel.com and NameScout.
Zip.tv was not just a defensive registration, either. It was previously promoted as a community-focused YouTube-style companion site for Zip.ca back in 2007.
The company also owns a trademark on the domain.

Registrar threatened with shutdown for failing to reveal registrant

ICANN has told a Turkish domain name registrar that its accreditation will be terminated unless it fixes its apparently shoddy Whois services.
While Alantron has a track record of Whois failures and connections to abusive domains, ICANN’s threat appears to have been made in connection with a single domain name.
ICANN compliance director Stacey Burnette wrote to Alantron (pdf):

On 12 October 2011, ICANN requested that Alantron make registration records available to ICANN concerning a specific domain name, as ICANN received a complaint that there was no Whois output available for the domain name. Although numerous requests were made by ICANN to make the registration records available for inspection and copying, as of the date of this letter, Alantron has not made any arrangements to comply with ICANN’s request.

The letter also details Alantron’s alleged failures to make Whois available through Port 43 and its web interface going back to September 1.
ICANN has also threatened to suspend Alantron’s ability to create new registrations. Alantron received a similar de-accreditation warning for Whois failures in April 2010.
It does not say who made the complaint or which domain is in question, but the company has come under fire from security pros in the past for allowing its services to be abused to push fake pharmaceuticals.
Alantron, which has about 26,000 domains under management according to Webhosting.info, has until November 25 to rectify the problem.

Court throws out Russian gaming scandal claims

Russian registrar RU-Center has won its appeal against a $7.5 million government fine, following claims that it gamed the launch of .РФ, registering tens of thousands of names to itself.
The Moscow Arbitration Court yesterday reversed the decision of the Federal Antimonoply Service, according to a statement from RU-Center, the .РФ registry and local media reports.
The dispute centers on the launch of the Cyrillic-script ccTLD last November, which saw over 200,000 registrations in the first six hours and half a million domains registered in the first few weeks.
RU-Center was quickly hit by claims that it had used its access to the registry, ccTLD Coordination Center, to register over 65,000 premium names to itself in order to auction them to users.
It later emerged that some of the Coordination Center’s launch policy-setters had ownership interests in RU-Center either directly or through family members.
In challenging the FAS ruling, RU-Center said that it only registered domains in its own name, via other registrars, because it had taken over 120,000 pre-orders from customers but was limited to filing 4,800 registrations per hour by the registry.
It also said that the domains remained in its own name because registry rules prohibited transfers during the first year of registration. The transfers will be effective November 11, it said.

Domain registrars pressured into huge shakeup

Domain name registrars have agreed to negotiate big changes to their standard contract with ICANN, after getting a verbal kicking from the US and other governments.
While the decision to revamp the Registrar Accreditation Agreement was welcomed by intellectual property interests, it was criticized by non-commercial users worried about diluting privacy rights.
The ICANN registrar constituency said in a statement today that it will enter into talks with ICANN staff in an effort to get a new RAA agreed by March next year.
It’s an ambitious deadline, but registrars have come under fire this week over the perception that they have been using ICANN’s arcane processes to stonewall progress.
So, what’s going to change?
The registrars said that the negotiations will focus on 12 areas, originally put forward by international law enforcement agencies, that have been identified as “high priority”.
They cover items such as an obligation to disclose the names of registrants using privacy services, to work with law enforcement, and to tighten up relationships with resellers.
Here’s a list of all 12, taken from a recent ICANN summary report (pdf).
[table id=1 /]
The changes were first suggested two years ago, and ICANN’s increasingly powerful Governmental Advisory Committee this week expressed impatience with the lack of progress.
There’s a US-EU cybercrime summit coming up next month, and GAC members wanted to be able to report back to their superiors that they’ve got something done.
As I reported earlier in the week, the GAC gave the registrars a hard time at the ICANN meeting in Dakar on Sunday, and it took its concerns to the ICANN board yesterday.
“We are looking for immediate visible and credible action to mitigate criminal activity using the domain name system,” US GAC representative Suzanne Radell told the board.
She won support from Steve Crocker who, in his first meeting as ICANN’s chairman, has shown a less combative style than his predecessor when talking with governments.
He seemed to agree that progress on RAA amendments through the usual channels – namely the Generic Names Supporting Organization – had not met expectations.
“One of the things that is our responsibility at the board level is not only to oversee the process, not only to make sure rules are followed and that everything is fair, but at the end of the day, that it’s effective,” he said.
“If all we have is process, process, process, and it gets gamed or it’s ineffective just because it’s not structured right, then we have failed totally in our duty and our mission,” he said.
An immediate result of the registrars’ decision to get straight into talks was the removal of an Intellectual Property Constituency motion from today’s GNSO Council meeting.
The IPC had proposed that the RAA should be revised in a trilateral way, between the registrars, ICANN, and everyone else via the GNSO.
Yanking the motion, IPC representative Kristina Rosette warned that the IPC would bring it back to the table if the RAA talks do not address the 12 high-priority items.
It would be unlikely to pass – registrars and registries vote against anything that would allow outside interests to meddle in their contracts, and they have the voting power to block such motions.
The ideas in the motion nevertheless stirred some passionate debate.
Tucows CEO Elliot Noss described the GAC’s heavy-handed criticisms as “kabuki theater” and “an attempt to bring politics as usual into the multi-stakeholder process” and said the RAA is not the best way to add protections to the DNS.
“Getting enforcement-type provisions, be they law enforcement or IP protections, into the RAA accomplishes only one thing. It turns the ICANN compliance department into a police department,” he said.
Wendy Seltzer, representing the Non-Commercial Users Constituency, said the changes proposed to the RAA “would reduce the privacy of registrants” and put them at increased risk of domain take-downs.
A broader issue is that even after a new RAA is negotiated registrars will be under no obligation to sign up to it until their current contracts expire.
Because many leading registrars signed their last contract after it was revised in 2009, it could be three or four years before the new RAA has any impact.
I’m not sure it’s going to be enough to fully satisfy the GAC.
Radell, for example, said yesterday that some items – such as the registrar obligation to publish an abuse contact – should be brought in through a voluntary code of conduct in the short term.
She also called for the 20% of registrars deemed to be bad actors (not a scientifically arrived-at number) should be de-accredited by ICANN.
UPDATE (October 27): Mason Cole of the registrars constituency has been in touch to say that the RAA talks will not only look at the 12 “high priority” or law enforcement recommendations.
Rather, he said, “there will be consideration of a broader range of issues.”
This appears to be consistent with the registrars’ original statement, which was linked to in the above post:

The negotiations are in response to the development of a list of recommendations made by law enforcement agencies and the broader Internet community to provide increased protections for registrants and greater security overall.

GAC slams registrars over “silly” crime domain moves

ICANN’s Governmental Advisory Committee is seriously annoyed with domain name registrars over what it sees as a failure to take the demands of law enforcement seriously.
The first official day of ICANN’s 42nd public meeting in Dakar, Senegal, was highlighted by a fractious discussion between the GAC and the Generic Names Supporting Organization.
Governments are evidently losing patience with the industry over what they see as incessant foot-dragging and, now, halfhearted bone-throwing.
The US, which is easily the most influential GAC member, was harshly critical of recent efforts by registrars to self-regulate themselves some law enforcement cooperation policies.
US GAC representative Suzanne Radell, saying she was speaking on behalf of the GAC, described a registrar move to start publishing legal service addresses on their web sites at some point in the future as as “paltry”, “mind-boggling” and “silly”.
She heavily implied that if the industry can’t self-regulate, the alternative is governments doing it for them. She was backed up by her counterparts from the UK, Australia and the European Commission.
Registrars have been talking to law enforcement for a few years about how to more effectively work together to prevent crime online.
In October 2009, agencies including the FBI and the UK Serious Organised Crime Agency publish a set of 12 recommendations about how to clean up the industry.
A lot of it was pretty basic stuff like a prohibition on registrar cybersquatting and an obligation to publish an abuse point of contact.
Despite a lot of talking at ICANN meetings, up until a couple of weeks ago there had not been a great deal of tangible progress.
The GNSO passed a resolution, proposed by registrars, to ask for an Issue Report to discuss whether registrars should be forced to post on their sites: a physical address for legal service, the names of key executives, and an abuse contact.
In ICANN’s world, an Issue Report usually precedes a Policy Development Process, which can take a year or more to produce results.
While the GNSO motion passed, it was opposed as inadequate by factions such as the Intellectual Property Constituency, which has close ties to the US government.
As the IPC seemed to correctly predict, the GAC was not amused.
“It is simply impossible for us to write a briefing memo for our political managers to explain why you need a policy to simply put your name on your web site,” Radell told the GNSO Council yesterday. “It is simply mind-boggling that you would require that.”
She pointed out that at a session during the Singapore meeting, registrars had indicated a willingness to address more of the law enforcement demands.
“That’s the context in which we are now coming to you saying this looks pretty paltry and actually it looks a little silly,” she said.
Mason Cole from the registrar constituency denied that they were “roadblocking” law enforcement’s demands, saying that a PDP is the fastest way to create a policy binding on all registrars.
“I think law enforcement was very clear when they made their proposals to us that what they were looking for was binding, enforceable provisions of policy that could be imposed on the registrars,” he said. “A code of conduct or a voluntary method would not arrive at binding, enforceable policy and therefore probably wouldn’t achieve the outcomes that law enforcement representatives were seeking.”
The debate didn’t end yesterday. Radell said she intends to take it up with the ICANN board of directors, presumably at their joint meeting tomorrow.
The implicit threat underlying the GAC’s protest is a legislative one, and Radell and other GAC members made it pretty clear that their governments back home regard domain names as a crucial tool in fighting online crime.

More layoffs planned at NetSol

Web.com plans to lay off more people than previously expected at recently acquired domain name registrar Network Solutions, according to a report.
“There is significantly more overlap than we originally estimated, and so it’s likely going to be more headcount reduction,” CEO David Brown said in a Reuters interview.
He named marketing, development, and engineering as areas where the merged company plans to cut more than $30 million in costs.
If there was any doubt about it, he confirmed that NetSol’s incumbent CEO faces the chop. Lower-level staff appear to have safer positions.
At least two senior NetSol executives have already jumped shipped since the acquisition was announced.
Senior director of policy Statton Hammock left to form his own consulting business a month ago, and last week senior policy manager Paul Diaz joined the Public Interest Registry.
Web.com announced its $561 million acquisition of NetSol in early August. It had already acquired the company’s old rival, Register.com.