Uniregistry’s portfolio of quirky new gTLDs grew today. The company seems to have beaten Google to .lol in a private deal.
The two companies were the only ones to apply for .lol, and Google’s application was formally withdrawn today.
As usual for private contention set settlements, the winning price has not been disclosed.
Uniregistry has 18 delegated gTLDs in its stable, with five more currently uncontested applications (.lol makes six) waiting in the wings.
I like .lol as a gTLD. It’s a punchy, short, meaningful string that certainly belongs to the right of the dot.
I can see it being deployed in the near term by the incessant sewer of BuzzFeed clones that are increasingly stinking up social media, which could give increased visibility and helpful viral marketing.
Longer term, there may be a worry if in future the kidz stop using “lol” and start viewing it as something their parents say, but we’re probably a ways from that yet.
Verisign’s .net gTLD has had a disappointing start to 2015, as its zone file dipped below 15 million domains for the first time since achieving the milestone.
As of last night, .net had 14,998,404 names in its zone, a daily dip of over 10,000 domains.
That’s down by about 200,000 names from the roughly 15.2 million it had in March 2014, the earliest count for which I have records.
The gTLD first passed 15 million in August 2013, according to a celebratory blog post at the time.
Verisign has previously blamed the “confusion” created by the launch of new gTLDs for the decline, which was inexorable in 2014.
In October, CEO James Bidzos told financial analysts that “.net may be more susceptible to that confusion that swirls around new gTLDs.”
My similar view is that the existence of new gTLDs is causing people to wake up to the fact that defensive or shopping cart up-sell .net registrations are now superfluous, and that the days of .net riding on big brother .com’s coat-tails may be numbered.
There are still about 31,000 dark .net domains — registered names not present in its zone file — according to Verisign.
At the end of August 2014, .net had 15,569,398 registered names, according to the most recent available ICANN registry report.
ICANN and Power Auctions have completed December’s mini-batch of “last resort” new gTLD auctions, adding a total of $6.4 million to its mysterious auction cash pile.
Johnson & Johnson won .baby, fighting off five portfolio applicants and paying a winning bid of $3,088,888.
Meanwhile, the Canadian Real Estate Association beat Afilias to .mls, paying $3,359,000.
I called it for CREA earlier this week, noting that the organization wanted .mls enough that it filed two applications, a failed Community Priority Evaluation, and an unsuccessful Legal Rights Objection against Afilias.
ICANN has now raised over $34 million selling off 10 strings at last resort auctions, with prices ranging from $600,000 (.信息) to $6.7 million (.tech).
The money has been set aside for purposes currently undecided. At least one applicant wants ICANN to redistribute the cash to losing bidders, which I don’t think is particularly likely.
ICANN’s fifth set of last-resort new gTLD auctions is set for tomorrow and it’s another small batch.
Just two contention sets — .baby and .mls — are set to be resolved, with ICANN stashing the winning bids into its special fund.
.baby is hotly contested with no fewer than six applicants — five portfolio applicants and one big brand.
Will Johnson & Johnson get what was once a single-registrant “closed generic”, or will Donuts, Google, Radix, Famous Four or Minds & Machines prevail?
Meanwhile, .mls (for “multiple listing service”, a type of real estate listings aggregation service popular in North America) is a two-horse race between Afilias and the Canadian Real Estate Association.
I’m tempted to call this one for CREA. The organization is so desperate for the .mls gTLD that it filed two applications, one “community” and one vanilla.
The community application was withdrawn earlier this year when CREA scored 11 out of 16 points on its Community Priority Evaluation, failing to pass the 14-point threshold.
The organization even filed a Legal Rights Objection against Afilias in attempt to kill off the competition, which also failed.
Having fought off these challenges, Afilias is either going to get the gTLD or walk away empty-handed. The last resort auction does not compensate unsuccessful bidders for their investments.
Amazon is now the proud owner of the .secure new gTLD, after much smaller competing applicant Artemis Internet withdrew its bid.
Coincidentally, the settlement of the contention set came just yesterday, the day before Artemis took its .trust — which I’ve described as a “backup plan” — to sunrise.
I assume .secure was settled with a private deal. I’ve long suspected Artemis — affiliated with data escrow provider NCC Group — had its work cut out to win an auction against Amazon.
It’s a shame, in a way. Artemis was one of the few new gTLD applicants that had actually sketched out plans for something quite technologically innovative.
Artemis’ .secure was to be a “trust mark” for a high-priced managed security service. It wasn’t really about selling domain names in volume at all.
The company had done a fair bit of outreach work, too. As long ago as July 2013, around 30 companies had expressed their interest in signing up as anchor tenants.
But, after ICANN gave Amazon a get-out-of-jail-free card by allowing it to amend its “closed generic” gTLD applications, it looked increasingly unlikely Artemis would wind up owning the gTLD it was essentially already pre-selling.
In February this year, it emerged that it had acquired the rights to .trust from Deutsche Post, which had applied for the gTLD unopposed.
This Plan B was realized today when .trust began its contractually mandated sunrise period.
Don’t expect many brands to apply for their names during sunrise, however — .trust’s standard registration policies are going to make cybersquatting non-existent.
Not only will .trust registrants have their identities manually vetted, but there’s also a hefty set of security standards — 123 pages (pdf) of them at the current count — that registrants will have to abide by on an ongoing basis in order to keep their names.
As for Amazon, its .secure application, as amended, is just as vague as all of its other former bids for closed, single-registrant generic strings (to the point where I often wonder if they’re basically still just closed generics).
It’s planning to deploy a small number of names to start with, managed by its own intellectually property department. After that, its application all gets a bit hand-wavey.