.shop among four gTLDs heading to auction

The new gTLDs .shop, .shopping, .cam and .phone are all set to go to auction after their various delays and objections were cleared up.
It seems that .shop and .shopping contention sets remain merged, so only one string from one applicant will emerge victorious.
That’s due to a completely mad String Confusion Objection decision that ruled the two words are too confusingly similar to coexist in the DNS.
That SCO ruling was made by the same guy who held up both sets of applications when he ruled that .shop and .通販 (“.onlineshopping”) were also too confusingly similar.
The two rulings combined linked the contention sets for all three strings.
.通販 applicant Amazon appealed its SCO loss using a special process that ICANN created especially for the occasion, and won.
But .shop and .shopping applicants were not given the same right to appeal, meaning the auction will take place between nine .shop applicants and .shopping applicants Uniregistry and Donuts.
Donuts is an applicant for .shop and .shopping, meaning it will have to make its mind up which string it prefers, if it intends to win the auction.
If it’s a private auction, Donuts would presumably qualify for a share of its own winning bid. Weird.
(UPDATE: That was incorrect).
The other contention set held up by an inconsistent SCO decision was .cam, which was originally ruled too similar to .com.
Rightside won its appeal too, meaning it will be fought at auction between Famous Four, Rightside and AC Webconnecting.
.phone had been held up for different reasons.
It’s a two-way fight between Donuts and Dish DBS, a TV company that wanted to run .phone as a closed generic. Like almost all closed generic applicants, Dish has since changed its plans.

Aussie government slams .food closed generic bid

The Australian government is among those asking ICANN deny a request to make .food a “closed generic” gTLD.
Eight people have filed comments opposing Lifestyle Domain’s application for Specification 13 status for its .food registry contract, which would allow the company to keep all .food domains for itself, since we reported the news earlier this month.
The Aussies are arguably the highest-profile opponent, and the one most likely to be taken seriously by ICANN.
Governmental Advisory Committee rep Annaliese Williams wrote:

The Australian Government issued an Early Warning to Lifestyle Domain Holdings, Inc on the grounds that ‘food’ is a common generic term, and that restricting common generic strings, such as .food, for the exclusive use of a single entity could have a negative impact on competition…
The Australian Government does not consider that Lifestyle Domain Holdings’ application to operate .food for its exclusive use serves a public interest goal.

Lifestyle Domain is a subsidiary of Scripps Networks, the company that runs the Food Network TV stations and Food.com web site.
The company claims that it has trademark rights to the word “food” that should allow it to run .food as a dot-brand gTLD.
That would mean nobody but Scripps, which won the right to .food at auction, would be able to register .food domains.
ICANN has also received negative comments from employees of registrars (both retail and corporate) and registries.
One comment, taken at face value, appears to be pro-Scripps, but I’m fairly confident it’s actually just extreme sarcasm.
The decision about whether to allow Scripps to add Spec 13 to its contract will be made by ICANN legal staff.
ICANN told me this week that there’s no ETA on a decision yet.

Credit card hack cost Web.com millions

Web.com is taking a $1 million per-quarter hit to its revenue as a result of August’s hacking attack.
It also incurred $400,000 in consulting, legal and credit monitoring fees in the third quarter as a result of the breach, CEO David Brown told analysts last night.
Some 93,000 credit card numbers were stolen during the attack, a small portion of its 3.3 million customers.
A number of customers jumped ship as a result of the attack, moving their domains elsewhere, which increased Web.com’s churn rate.
“Due to the subscription nature of our business, in the fourth and subsequent quarters we expect the breach will have about a $1 million negative impact on revenue per quarter due to the shortfall from Q3,” Brown said.
It added 15,000 customers in the quarter, lower than the 21,000 it added in Q2.
Net income for the quarter was $6.1 million, reversing a $3.4 million loss in the year-ago period, on revenue that was basically flat at $136.8 million, compared to $137.4 million a year ago.
In response to an analyst question, Brown also commented on the success, or lack thereof, of the company’s new gTLD business. He said:

That continues to be positive, but we’re not doing back-flips here. It’s not that positive. We think it’s good for the market, good for consumers and businesses to have more choices. But they’re not flying off the table. .com and .net and the original extensions still are the force in the marketplace. But as we see more gTLDs and as the market understands them and see the opportunity, we continue to believe that this will be a positive trend. But at this point, it’s not moving the needle in our business or likely in anyone’s business.

Web.com owns registrars including Network Solutions and Register.com.

.cars domains to start at $45,000, retail for $2,500

Cars Registry has set pricing for .car, .cars and .auto domains at crazy-high levels.
If you want to buy a domain in any of the three gTLDs on day one, it will cost you a whopping $45,000.
If you buy one during regular general availability, it’s likely to set you back $2,500.
The registry, a partnership of Uniregistry and XYZ.com, has set its registry fee at $2,000, according to an email sent to registrars this week.
That’s a buck higher than .sucks, one of the most expensive new gTLDs to launch to date.
The sunrise fee will be $3,000 — made up of the regular $2,000 fee plus an added $1,000. Again, that’s higher than .sucks.
The Early Access Period — which, as reported yesterday, has replaced the more usual landrush — will run for nine days with prices ranging from $45,000 to $5,000.
Compared to the usual models of XYZ.com and Uniregistry, which tend towards the mass-market, these prices are colossal.
I wonder how much the pricing was influenced by the fact that the registry has the car-related gTLD market almost entirely sewn up.
Its only potential competitor is .autos, which has been delegated for almost 18 months but has yet to even reveal its launch plans and probably isn’t going to be available to the mass market anyway.
Sunrise for all three gTLDS is due to start December 9, ending January 12. EAP will begin that day, and GA will start January 20.

.gay applicant appeals community loss, again

dotgay LLC has appealed its Community Priority Evaluation defeat again, filing a new Request for Reconsideration with ICANN this week.
It’s an unprecedented second use of the RfR process to appeal its CPE loss, in which the Economist Intelligence Unit panel decided the applicant’s definition of “gay” was far too broad to award dotgay enough points to pass the evaluation.
But dotgay wants ICANN to initiate a third CPE, to be carried out by anyone other than the EIU.
The EIU panel said earlier this month that it had “determined that the applied-for string does not sufficiently identify some members of the applicant’s defined community, in particular transgender, intersex, and ally individuals”.
Basically, EIU was pointing out, for the second time, that transgender people and straight “allies” aren’t “gay”.
It awarded dotgay 0 out of the possible 4 points available on “Nexus” criteria, meaning the applicant failed to hit the 14 points required to win.
While the RfR dodges the transgender issue altogether, dotgay has some interesting arguments in response to the “ally” question.
It’s now claiming that “ally” refers to companies and organizations that support the equal rights cause (because non-human legal entities don’t have a gender identity or sexual preference) and to proxy registrars:

Now, since an organization or company in itself can impossibly be “lesbian” or “gay”, Requester has been seeking for a way to also position these companies and organizations in this community definition. For this reason, Requester has referred to these organizations as “allies” in the context of the LGBTQIA definition.
Furthermore, as stated in the Application, LGBTQIAs are a vulnerable group in many countries and societies, and too often still the subject of prosecution for who they are. In order to put in place safeguards for those gay community members who do not wish to be directly associated with a domain name registration, organizations and companies who in essence cannot be “non-heterosexual” should have the possibility to act as a proxy service, which is common practice in the domain name industry.
In any case, any such “ally” must be approved by an Authentication Partner in order to be able to register a domain name in its own name or in the name or on behalf of a third party who meets the LGBTQI requirements.

It’s an interesting argument, but I can’t see anything in its original application that would support such a position.
dotgay may be on stronger ground with its claim that it unfairly lost one point on the “Opposition” criteria of the CPE.
Two points were available there. Applicants could lose one point immediately if there was a single letter of opposition from a relevant, non-negligible organization.
The EIU seems to have been in possession of such a letter, though its CPE ruling does not name the opponent.
dotgay thinks the opponent was the Q Center, a community center in Portland, Oregon, which opposed dotgay in writing in 2014 but, following a change in its board of directors, retracted that opposition (pdf).
So it may be the case that dotgay unfairly lost a point.
Regaining that point would not be enough to give the company a winning CPE score, but if the EIU screwed up that may be grounds for ICANN to initiate another rerun of the CPE.
However, it’s quite rare for ICANN’s board of directors to approve an RfR.
If dotgay loses, it will either have to go to auction against its rival applicants or file an Independent Review Process complaint, its final avenue of appeal.
Read its RfR here.

Verisign’s silly .xyz lawsuit thrown out

Verisign has had its false advertising lawsuit against the .xyz gTLD registry thrown out of court.
XYZ.com this week won a summary judgement, ahead of a trial that was due to start next Monday.
“By granting XYZ a victory on summary judgement, the court found that XYZ won the case as a matter of law because there were no triable issues for a jury,” the company said in a statement.
The judge’s ruling does not go into details about the court’s rationale. XYZ’s motion to dismiss has also not been published.
So it’s difficult to know for sure exactly why the case has been thrown out.
Verisign sued in December, claiming XYZ and CEO Daniel Negari had lied in advertising and media interviews by saying there are no good .com domain names left.
Many of its claims centered on this video:

XYZ said its ads were merely hyperbolic “puffery” rather than lies.
Verisign also claimed that XYZ had massively inflated its purported registration numbers by making a shady $3 million reciprocal domains-for-advertising deal with Network Solutions.
XYZ general counsel Grant Carpenter said in a statement: “These tactics appear to be part of a coordinated anti-competitive scheme by Verisign to stunt competition and maintain its competitive advantage in the industry.”
While Verisign has lost the case, it could be seen to have succeeded in some respects.
XYZ had to pay legal fees in “the seven-figure range”, as well as disclose hundreds of internal company documents — including emails between Negari and me — during the discovery phase.
Through discovery, Verisign has obtained unprecedented insight into how its newest large competitor conducts its business.
While I’ve always thought the lawsuit was silly, I’m now a little disappointed that more details about the XYZ-NetSol deal are now unlikely to emerge in court.

Should brands get a new gTLD round to themselves? Twitter thinks so

Twitter wants to get its hands on some new gTLDs but doesn’t want to wait.
Having missed the first round of new gTLD applications back in 2012, the company is now keen on getting .twitter and other strings both branded and generic.
“We’re interest in round two,” Twitter trademark counsel Stephen Coates said as ICANN’s business constituencies met the board of directors today.
“We have several interesting opportunities to develop around that space,” he said. “We are interested in both brands and generics.”
The problem for Twitter, and every other would-be gTLD applicant, is that ICANN isn’t even talking in broad terms about when the next round will be.
The absolute minimum that must happen is that ICANN must complete a review of round one, focusing on “Competition, Consumer Trust and Consumer Choice”. This CCT review is mandated by ICANN’s Affirmation of Commitments with the US government.
Almost three years after the first round opened, the volunteer team that will carry out the CCT review has not even been assembled yet.
There are a number of other factors that may or may not wind up on the critical path — such as reviews of rights protection mechanisms and security and stability at the DNS root.
Coates said he would like a “bifurcated” review process leading to two separate second application rounds.
“I would advocate for bifurcating the review process, which I think is very important, especially around RPMs,” he said. “But also bifurcating the round process, treating dot-brands differently than generic names.”
I think this outcome is unlikely.
Application rules that give preference to one type of application over another invite exploitation. It happened in the 2003 sponsored TLD round and it’s happening with “community” and “Specification 13” applications in the current round too.

Afilias gives its gTLDs a kick up the bum with U-turn 101domain buy

Afilias, once one of the fiercest opponents of registries owning registrars, has acquired 101domain to gain its first significant foothold in the registrar market.
Wolfgang Reile, president and CEO of 101domain, said he would be quitting the company and that COO/CFO Anthony Beltran will be leading the new Afilias unit in future.
The acquisition, which closed September 2, was for an undisclosed amount, but I’d say it was easily a seven-figure deal.
When Afilias rival CentralNic acquired Internet.bs last year, it paid $7.5 million.
California-based 101domain is currently about a quarter of the size that Internet.bs was when it was bought, based on gTLD domains under management, with a little over 120,000 names on its books as of June this year, according to registry reports.
But the company is well known as a go-to registrar if you want a broad choice of TLDs — it says it currently supports over 900. Its ccTLD sales may make the company much bigger.
Getting its stable of registry offerings to market is one of the reasons Afilias was drawn to 101domain.
Afilias’ own portfolio of TLDs contain some semi-restricted strings — such as .vote, which has a no-domaining policy — that would not be automatically attractive to many registrars.
Afilias told DI:

This acquisition furthers our post-vertical integration strategy of establishing a capability that enables us to both service our registry customers and ensure an outlet for TLDs of our own that may not be easy to find at a traditional registrar. 101domain is expected to continue to operate as it does today.

Afilias actually already had a registrar division — Emerald Registrar, which does business from iDomains.com — but had fewer than 1,500 domains under management at the last count.
Its registry business has over 20 million domains.
If you have a long memory, you may recall that Afilias was once dead-set against the concept of vertical integration — registries and registrars under the same ownership — which in the post-2012 new gTLD world has become industry standard.
The ICANN working group that was tasked with reforming ownership rule was held in stalemate by Afilias and Go Daddy back in 2010, before ICANN finally broke the deadlock.
New gTLD portfolio registries including Uniregistry, Google, Minds + Machines and Rightside have registrar businesses already. Famous Four seems to be closely aligned with Alpnames, and Donuts is tight with Rightside.

Odd-couple coalition wants URS deleted from legacy gTLD contracts

Commercial and non-commercial interests within ICANN have formed a rare alliance in order to oppose the Uniform Rapid Suspension policy in three new legacy gTLD contracts.
The groups want ICANN to delete URS from the .travel, .cat and .pro Registry Agreements, which were all renewed for 10-year terms last week.
The Business Constituency and the Non-Commercial Stakeholders Group put their names to a Request for Reconsideration filed with ICANN yesterday.
The Internet Commerce Association, a member of the BC, filed a separate RfR asking for the same thing yesterday too.
These groups believe that ICANN contracting staff are trying to create consensus policy by the back door, from the top down, by imposing URS on gTLDs that were delegated before the 2012 application round.
URS was created specifically for the new gTLD program and therefore should not apply to legacy gTLDs, they say. The BC/NCSG request states:

Our joint concern… is that a unilateral decision by ICANN contractual staff within the [Global Domains Division] to take the new gTLD registry agreement as the starting point for renewal RAs for legacy gTLDs has the effect of transforming the PDDRP [Post Delegation Dispute Resolution Process] and the URS into de facto Consensus Policies without following the procedures laid out in ICANN’s Bylaws for their creation. To be clear, we take no objection to a registry voluntarily agreeing to adopt RPMs in their contractual negotiations with ICANN.

The ICA has the same objections. It’s primarily concerned that the new contracts set a precedent that will ultimately force URS into the .com space, when Verisign’s contract comes up for renewal.
Both RfRs ask ICANN to delete the URS requirements from the just-signed .pro, .travel and .cat registry agreements.
The requesters suspect that rather than including URS as “the result of even-handed ‘bilateral negotiations'”, it was “staff insistence that the registries accept it to achieve timely registry agreement renewal.”
They want the ICANN board to demand to see the emails that were exchanged during negotiations in order to determine whether the registries were strong-armed into signing up for URS.
The BC/NCSG request is here. The ICA request is here.

XYZ to put global block on domains banned in China

XYZ.com plans to slap a global ban on domain names censored by the Chinese government.
Chinese words meaning things such as “human rights” and “democracy” are believed to be on the block list, which an industry source says could contain as many as 40,000 words, names and phrases.
(UPDATE: Gavin Brown, CTO of XYZ back-end CentralNic, tweeted that the list is nowhere near 40,000 names long.)
The registry seems to be planning to allow the Chinese government to censor its new gTLDs, which include .xyz, .college, .rent, .protection and .security, in every country of the world.
And it might not be the last non-Chinese registry to implement such a ban.
The surprising revelation came in a fresh Registry Services Evaluation Process request (pdf), filed with ICANN on Friday.
The RSEP asks ICANN to approve the use of a gateway service on the Chinese mainland, which the company says it needs in order to comply with Chinese law.
As previously reported, Chinese citizens are allowed to register domains in non-Chinese registries, but they may not activate them unless the registry complies with the law.
That law requires the registry to be located on the Chinese mainland. XYZ plans to comply by hiring local player ZDNS to proxy its EPP systems and mirror its Whois.
But the Chinese government also bans certain strings — which I gather are mostly but not exclusively in Chinese script — from being registered in domain names.
Rather than block them at the ZDNS proxy, where only Chinese users would be affected, XYZ has decided to ban them internationally.
Registrants in North America or Europe, for example, will not be able to register domains that are banned in China. XYZ said in its RSEP:

XYZ will reserve names prohibited for registration by the Chinese government at the registry level internationally, so the Gateway itself will not need to be used to block the registration of of any names. Therefore, a registrant in China will be able to register the same domain names as anyone else in the world.

It seems that XYZ plans to keep its banned domain list updated as China adds more strings to its own list, which I gather it does regularly.
Customers outside of China who have already registered banned domains will not be affected, XYZ says.
If China subsequently bans more strings, international customers who already own matching domains will also not be affected, it says.
CEO Daniel Negari told DI: “To be clear, we will not be taking action against names registered outside of China based on Chinese government requests.”
But Chinese registrants do face the prospect losing their domains, if China subsequently bans the words and XYZ receives a complaint from Chinese authorities.
“We treat requests from the Chinese government just like we treat requests from the US government or any other government,” Negari said.
“When we receive a valid government or court order to take action against a name and the government has jurisdiction over the registration, we will take action the registration,” he said.
Up to a third of the .xyz zone — about three hundred thousand names — is believed to be owned by Chinese registrants who are currently unable to actually use their names.
The company clearly has compelling business reasons to comply with Chinese law.
But is giving the Chinese government the ongoing right to ban tens of thousands of domain names internationally a step too far?
ICANN allows anyone to file public comments on RSEP requests. I expect we’ll see a few this time.