.cloud gets 500 sunrise regs

Aruba, the .cloud gTLD registry, said it received 500 applications during its sunrise phase, which closed this afternoon.
While low by pre-2012 standards, it’s a relatively respectable performance for a new gTLD, where sunrises periods consistently result in double-digit registrations.
It’s almost certainly in the top 10 for 2012-round gTLDs.

exactly one hour left to submit Trademark Priority Registration Orders in the .cloud sunrise… 500 received so far 🙂 #dotCloudFTW

— Get .Cloud (@getdotcloud) January 15, 2016

I gather there was only one duplicate application during the period, which ran from November 16.
Before sunrise began, Aruba already had about 30 “pioneer” registrants in the web hosting space, including Ubuntu and Weebly.
Landrush is set to kick off January 25, with general availability following February 16. Retail pricing will be around the $25 a year mark.

M+M acquires .boston from Boston Globe

Minds + Machines has added .boston to its stable of geo-gTLDs, buying the contract from the publisher of the Boston Globe newspaper.
The company said today that it has acquired 99% of Boston TLD Management, a new company into which the Globe plans to sign over its .boston ICANN contract.
The deal is contingent on ICANN approving the contract reassignment.
The ink is still moist on the .boston Registry Agreement, which was signed December 10.
The gTLD is officially in pre-delegation testing right now.
But the acquisition also means M+M will take over back-end duties for .boston. Originally, the Globe had intended to use OpenRegistry.
The gTLD was officially a “geographic” string under ICANN rules, and needed support from the local government in Boston.
.boston would become M+M’s fifth geographic gTLD — sixth if you include .london.
The company said it plans to launch the TLD later this year.

.sucks “gagging” registrar critics?

.sucks may be all about freedom of speech, but some registrars reckon the registry is trying to ban them from criticizing the new gTLD in public.
Vox Populi is proposing a change to its standard registrar contract that some say is an attempt to gag them.
A version of the Registry-Registrar Agreement dated December 18, seen by DI, contains the new section 2.1:

The purpose of this Agreement is to permit and promote the registration of domain names in the Vox Populi TLDs and to allow Registrar to offer the registration of the Vox Populi TLDs in partnership with Vox Populi. Neither party shall take action to frustrate or impair the purpose of this Agreement.

It’s broad and somewhat vague, but some registrars are reading it like a gagging order.
While many retail registrars are no doubt happy to sell .sucks domains as part of their catalogs, there is of course a subset of the registrar market that focuses on brand protection.
Brand protection registrars have been quite vocal in their criticism of .sucks.
MarkMonitor, for example, last year wrote about how it would refuse to make a profit on .sucks names, and was not keen on promoting the TLD to its clients.
Asked about the new RRA language, Vox Pop CEO John Berard told DI that it was merely an attempt to clarify the agreement but provided no additional detail.
Registrars are also angry about a second substantial change to the contract, which would allow the registry to unilaterally make binding changes to the deal at will.
The new text in section 8.4 reads:

Vox Populi shall have the right, at any time and from time to time, to amend any or all terms and conditions of this Agreement. Any such amendment shall be binding and effective 15 days after Vox Populi gives notice of such amendment to the Registrar by email.

That’s the kind of thing that ICANN sometimes gets away with, but some registrars are saying that such a change would let Vox Pop do whatever the hell it likes and would therefore be legally unenforceable.

Priced to sell: $46m of two-letter .xxx names

ICM Registry has added over 1,200 two-character .xxx names to its catalog of priced premiums.
With prices ranging from $100,000 to $37,500, the newly offered domains carry a total ticket price of over $46 million.
The only six-figure name on the list is vr.xxx. ICM said in a press release today it has already sold vr.porn and vr.sex for $100,000 apiece.
There are seven names with adult connotations (such as 69.xxx and bj.xxx) priced at $75,000, eight more at $50,000 and two at $40,000.
The rest of the list of 1,227 names are being offered at $37,500, which is roughly 10 times the prices on the equivalent .porn, .sex and .adult domains.
While ICM noted the interest in domain investing from China recently, it does not appear to have valued its numeric-only domains (such as 88.xxx) any more highly than less attractive-looking combinations (such as 0o.xxx).
Judging by the list published on ICM’s web site, it has already sold well over 300 two-character domains in its newest three gTLDs.
Had those sold at the buy-now prices it would have raised over $1.1 million in revenue.
But ICM since September has been offering an option to register premium names for premium annual fees that are lower than the one-off price. A $37,500 domain costs $3,000 a year to register, under this model.
The total value of ICM’s premium list, including all the longer domains, is roughly $115 million.

Baidu, China’s Google, gets its dot-brand gTLD

Chinese web giant Baidu had its dot-brand gTLD, .baidu, go live in the DNS root zone today.
With the extraordinary amount of focus on China in the domain industry currently, this could be one of the dot-brands to watch in 2016.
There are no active domain names in .baidu just yet, but we will likely see nic.baidu put to some use or another over the coming days.
Unusually for a dot-brand gTLD, Baidu’s contract with ICANN does not contain specifications 9 or 13, which allow dot-brands to operate differently to regular gTLDs.
This suggests an open registration policy under which any registrar can sell .baidu domains to any registrant.
However, Baidu’s original gTLD application spells out quite a different plan, focused primarily on trademark protection. It says:

All available second-level strings of .BAIDU (e.g. example .BAIDU) will be initially allocated only to limited number of eligible registrants and for internal corporate business purposes. BAIDU plans to adopt this approach and expects to maintain it for 3 years from the launch of the “.BAIDU” registry service. Such approach will be regularly evaluated and adjusted if appropriate and necessary. Depending a various internal and external factors, including market demand and user expectation, BAIDU may consider a phased roll-out approach for a broader commercial marketplace but will do so after the conclusion of the initial 3-year period.

I wouldn’t expect .baidu to launch properly any time soon.
Not only is the company probably going to want to get its dot-brand contractual protections in place, it’s also showed no huge enthusiasm for making its way through the new gTLD delegation process so far.
It signed its ICANN contract January 8 last year, meaning this week was pretty much the latest date it could permissibly go into the root.
Like most dot-brands, it’s been dragging its feet, in other words.
Baidu is the leading web property in China, dwarfing even Google in terms of search market share locally.

Afilias seeks to freeze Architelos patent after $10m lawsuit win

Afilias seems bent on burying domain security software maker Architelos, after winning a $10 million lawsuit against it.
The registry on Friday filed a court motion to freeze the patent at the heart of the lawsuit, which Afilias says — and a jury agreed — was based on trade secrets misappropriated by former Afilias employees.
Afilias said it wants to make sure Architelos does not attempt to sell the so-called ‘801 patent, which covers domain abuse-monitoring software.
Its motion asks for a court order “prohibiting Architelos from taking any action that would dilute… or diminish Architelos’ rights or ownership interests” in the patent.
It notes that Architelos has stated that it does not have the means to pay the $10 million damages awarded by a jury in August, which might give it a reason to try to sell the patent.
Afilias said Architelos had “raised the prospect of bankruptcy” during post-trial negotiations.
The motion seems to have been filed now because the judge in the case is taking an unusually long time to render her final judgment.
Despite the case being heard on a so-called “rocket docket” in Virginia, the two companies haven’t heard a peep out of the court since late October.
According to Afilias’ motion, the judge has indicated that Afilias will wind up at least partially owning the ‘801 patent, but that the jury’s $10 million verdict may be “tweaked”.
Judging by a transcript of the August jury trial, the judge herself was not particularly impressed with Afilias’ case and did not expect the jury to crucify Architelos so badly.
Out of the jury’s earshot, she encouraged Afilias to attempt to settle the case and said “if the jury verdict comes in against what I think is the clear weight of the evidence, I will most likely adjust it.”
She also said: “I would have trouble believing that any reasonable jury would find even if they were to award damages to the plaintiff that there’s any significant amount here.”
She clearly misread the jury, which a few days later handed Afilias every penny of the $10 million it had asked for.
That’s much more money than Architelos is believed to have made in revenue since it launched four years ago.
Afilias’ latest motion is set to be heard in court in early January.

More on my Twitter.sucks reg

If you were reading on Friday, you’ll know that I brought about the registration of the domain twitter.sucks and took charge of a web site hosted at that address.
I hinted that there was a little more to the story, but couldn’t get into it.
The first part of the story is here.
What I didn’t mention was that twitter.sucks was in my This.sucks account for probably less than 10 minutes before I removed it.
I have no beef with Twitter and no particular desire to moderate a .sucks discussion forum.
After removing twitter.sucks from my account, I noticed that This.sucks again gave me the option to “register” a free .sucks domain.
So I experimentally “registered” thisdotsucks.sucks too.
Again, the domain started resolving, showed up in Whois, and the associated WordPress site went live within seconds.
At this point, I discovered that I had admin privileges for both twitter.sucks and thisdotsucks.sucks sites simultaneously.
Suspecting that I may have found a bug that would allow anyone to register an essentially unlimited number of free and potentially trademark-matching .sucks domains, I informed This.sucks of my findings in the interest of responsible bug disclosure and ended my blog post prematurely.
Late Friday, This.sucks spokesperson Phil Armstrong told me that it wasn’t a bug after all.
He said that the company allows one “do-over”. So if you register a name for free, then delete it, you get another one for free.
He also said that WordPress admin privileges for domains removed from user accounts expire after a period (I had admin rights for the twitter.sucks web site for roughly 48 hours after I deleted it from my account.)
Right now, the domain twitter.sucks still exists, registered to This.sucks as before, as does the associated web site. I have no idea if another user has taken over its administration or if it’s in some kind of limbo state.
All I know is that it’s nothing to do with me any more.

.phone will be restricted after Dish gTLD auction win

The new gTLD .phone is going to be tightly restricted, after Dish DBS won the contested string at auction.
The American satellite communications firm beat Donuts to the gTLD, judging by Donuts’ withdrawal from the two-horse on Friday.
This means that if you’re not a licensed telecoms or voice-over-IP service provider, you won’t be able to register a .phone domain, at least at first.
Dish originally applied for .phone as what became known as a “closed generic” — a non-trademark, dictionary word that would nevertheless be operated as a dot-brand, with a single eligible registrant.
Due to Governmental Advisory Committee advice against such business models, Dish changed its application this September to describe .phone instead as a “controlled” gTLD.
Its application states that only Dish, its affiliates and “Qualified Applicants” will at first be able to register .phone domains.
“Qualified Applicants” basically means any company licensed to run a telecommunications service anywhere in the world. The eligibility gate appears to be the “license”.
The application says Dish will reserve the right to open up the gTLD to further classes of registrants at a later date.
While it also says that Dish will not give itself or friendly registrars any “undue preference”, the telecoms industry is suspicious.
USTelecom, the industry body representing large and small US-based telecoms companies, wrote to ICANN in November to say Dish’s volte face was “unconvincing” and its proposals “simply fail to satisfy” ICANN’s rules banning closed generics.
It said in its letter (pdf):

While Dish purports in its amended application that the .phone gTLD will be operated as a “controlled gTLD,” it is in reality an exclusive generic TLD, prone to discriminatory and subjective determinations on which entities are “Qualified Applicants,” and a discretionary reservation “to open this TLD to additional classes of registrants in the future,” who “will not be considered members.”

USTelecom says it negotiated with Dish, in an attempt to resolve its earlier formal objection against the bid, to have Dish include some reassuring Public Interest Commitments in its application, but Dish refused.
ICANN, responding to USTelecom, said that any Registry Agreement Dish signs for .phone will include the clauses that prevent it operating as a closed generic.
Now that the contention set has been settled, Dish’s next step is to proceed to contract negotiations with ICANN.

Tata’s bid for .tata gTLD scuppered by Morocco

Tata Group, the humongous Indian conglomerate, has been told its flagship application for a dot-brand gTLD has been refused.
ICANN on Friday changed the status of the application for .tata from “On Hold” to “Will Not Proceed”, a limbo state that is usually expected to lead to the application being withdrawn.
It is believed that Tata’s row with Morocco is to blame.
While Tata Group is a 150-year-old, $100 billion-a-year company, Tata is also a province of Morocco with a population of about 120,000.
Under the rules of the ICANN new gTLD program, the string “tata” is therefore a protected geographic name, for which the applicant needs to show the unequivocal support or non-objection of the relevant government.
Tata was the last applicant to pass its ICANN evaluation, when in July 2014 it finally managed to pass its Geographic Names Review on the basis of a letter from a Moroccan official.
However, in September last year the Moroccan’s government’s digital economy minister denied that the letter indicated support for .tata.
This February, ICANN threw Tata back into a Geographic Names Review, where the onus was on the company to prove that it really did have support.
That support has evidently not been forthcoming.
Morocco has indicated in letters to ICANN that it may want the .tata gTLD itself in future.
Tata unit Tata Motors has already been delegated the dot-brand gTLD .tatamotors.

Porn firm wins .cam after years of objections

The controversial new gTLD .cam has been won at auction by Dutch porn site operator AC Webconnecting, putting an end to over two years of back-and-forth objections.
Rival applicants Rightside and Famous Four Media both withdrew their applications earlier this week.
The contest for .cam was marked by several objections and appeals.
In 2013, Verisign filed and lost String Confusion Objections against AC Webconnecting and Famous Four, but won its near-identical objection against Rightside.
Verisign had claimed that .cam and .com are so similar-looking that confusion among internet users is bound to arise.
Because the SCO panels in the three cases returned differing opinions, Rightside was one of two applicants given the right to appeal by ICANN in October 2014.
I never quite understood why Verisign wasn’t also given the right to appeal.
Rightside won the right to stay in the .cam contention set almost a year later.
Despite all that effort, it did not prevail in the resulting auction.
Separately, back in 2013, AC Webconnecting filed and lost Legal Rights Objections against its two rivals, based on a “.cam” trademark it acquired purely for the purpose of fighting off new gTLD competitors.
I’d be lying if I said I knew a lot about the soon-to-be registry.
Based in Rotterdam, its web site comes across as a wholly safe-for-work web design firm.
However, it seems to be mainly in the business of operating scores, if not hundreds, of webcam-based porn sites.
Its application for .cam states that it will be for everyone with an interest in photography, however.
When it goes live, its most direct competitor is likely to be Famous Four’s .webcam, which already has an 18-month and 70,000-domain head start.
It remains to be seen whether its clear similarity to .com will in fact cause significant confusion.