Disappointing .sexy launch shows the importance of the channel

.sexy not so sexy after all?
Uniregistry’s first new gTLDs to launch, .sexy and .tattoo, have showed a poor first-day performance after the company failed to secure Go Daddy as a registrar partner.
During the 60-day sunrise period and the first 30 hours of general availability, .sexy sold just shy of 2,700 domains, judging by zone files, while .tattoo racked up a pitiful 700 registrations.
This makes .sexy the 19th most popular new gTLD. On the DI PRO league table it’s sandwiched between .holdings and .camera, and .tattoo the 28th, between .voyage and .careers.
It’s not a completely terrible performance for .sexy — .camera and .holdings have been on the market for three and four weeks respectively — but one might have expected better sales for a string that isn’t tied to a particular vertical niche and is, arguably, just intrinsically attractive.
.sexy’s first-day performance is in the same ball park as Donuts’ .gallery and .estate, hardly strings to get excited about.
For .tattoo, the story is less gray — under 1,000 domains sold is not a success in anyone’s book.
I think there are a couple reasons for the poor showing.
First, the strings themselves. While I can see .sexy proving popular with regular buyers, it doesn’t easily lend itself to domain names that are instinctively attractive to domainers.
You can put pretty much any profession or product name in front of a .guru and it is meaningful as a brand or a rather grandiose self-appointed title. Not so with .sexy.
Ironically, this appears to be Uniregistry CEO Frank Schilling’s “Toilet Paper Test” in action.
Schilling argues that the test of how generic, and by extension popular, a gTLD is should be whether toiletpaper.[tld] works. I think toiletpaper.guru works, but toiletpaper.sexy does not.
Second, Uniregistry lacked distribution.
While it had big registrars such as eNom and NameCheap (almost 50 in total) on its books, it lacked Go Daddy and 1&1 — the two companies that have been pushing pre-registrations more heavily than any other.
The reason Donuts’ gTLDs performed better in their first hours is that these companies, mainly Go Daddy, had been collecting pre-regs for weeks and spammed the registry with registration requests at the first second they were able. Day one registrations actually represent weeks of marketing and leads.
Uniregistry took an awfully big risk by demanding registrars hand over part of the customer relationship to the registry, and it seems to have impacted its sales.
The company plans to shortly launch its own registrar, and is betting hard of this being a successful sales channel.
I’m somewhat skeptical about this strategy, at least in the short term.
Go Daddy has spent tens (hundreds?) of millions of dollars on marketing over the last decade or so. It has a lot of eyeballs already and it’s going to be nigh-on impossible to replicate that degree of success.
Uniregistry is not the only new gTLD portfolio registry enthusiastically embracing vertical integration.
The trail was blazed by Minds + Machines, which launched its own registrar last November. Today, it’s difficult to tell on the company’s web site where the registrar ends and the registry begins.
What’s M+M’s launch channel going to look like? We’re not going to know for sure until its first TLDs hit the market.
Are the big registrars going to make the vertically integrated business model difficult to carry off successfully? While registries are obliged to give access to any registrar that wants to sell their names, registrars have no obligations to carry any TLD they don’t want to.

New gTLD registries given way to free up millions of blocked names

Up to 9.8 million new gTLD domain names are to get a get-out-of-jail card, with the publication yesterday of ICANN’s plan to mitigate the risk of damaging name collisions.
As a loyal DI reader, the details of the plan will not come as a great surprise. It was developed by JAS Global Advisors and previewed in a guest post by CEO Jeff Schmidt in January
Name collisions are scenarios where a TLD delegated by ICANN to the public DNS matches a TLD that one or more organizations already uses on their internal networks.
Verisign, in what many view as protectionist propaganda, has been arguing that name collisions could cause widespread technical and economic damage and even a risk to life.
Things might stop working and secret data might leak out of corporate networks, Verisign warns.
JAS’ proposed solution, which ICANN has opened for public comment, is quite clever, I think.
Called “controlled interruption”, it will see new gTLD registries being asked to wildcard their entire second level of their TLDs to point to the IP address 127.0.53.53.
If there’s a name collision on example.corp the company using that TLD on its network will notice unusual behavior and will have an opportunity to fix the problem.
Importantly, no data apart from the DNS look-up will leak out of their networks — the 127/8 IP address block is reserved by various standards for local uses only.
The registry will essentially bounce the DNS request back to the network making the request. If that behavior causes problems, the network administrator will presumably check her logs, notice the odd IP address, and Google it for further information.
Today, she’ll find a Slashdot article about the name collisions plan, which should put the admin on the road to figuring out the problem and fixing her network. In future, maybe ICANN will rank for the term.
Registries would be able to choose whether to wildcard their whole TLD or to only point to 127.0.53.53 those second-level names currently on their collisions block lists.
In either case, the redirection would only last for the first 120 days after delegation. That’s the same duration as the quiet period ICANN already imposes on new delegations, during which only “nic.” may resolve.
After the 120 days are up, the name collisions issue would be considered permanently closed for that TLD.
If this goes ahead, the plan will allow registries to unblock as many as 9.8 million domain names representing 6.8 million unique second-level labels, according to DI PRO collisions database.
It could also put an end to the argument about whether name collisions really were a significant problem (160,000 new gTLD names are already live and we haven’t heard any reports of collisions yet).
Pointing to the fact that new TLDs, some of which showed evidence of collisions, were getting delegated rather regularly before the current new gTLD round, JAS said in its report:

We do not find that the addition of new Top Level Domains (TLDs) fundamentally or significantly increases or changes the risks associated with DNS namespace collisions. The modalities, risks, and etiologies of the inevitable DNS namespace collisions in new TLD namespaces will resemble the collisions that already occur routinely in the other parts of the DNS.

However…

Collisions in all TLDs and at all levels within the global Internet DNS namespace have the ability to expose potentially serious security and availability problems and deserve serious attention.

JAS calls its plan “a conservative buffer between potential legacy usage of a TLD and the new usage”.
As wildcarding is currently prohibited by ICANN’s standard Registry Agreement (ironically, to prevent a repeat of Verisign’s Site Finder) an amendment is going to be needed, as the JAS plan acknowledges.
The drawback of the plan is that if an organization is relying on a colliding internal TLD, whatever systems use that TLD could break under the plan. The 127/8 redirection is a way to help them resolve the breakage, not always to prevent it happening at all.
For new gTLD registries it’s pretty good news, however. There are many thousands of potentially valuable premium names blocked under the current regime that would be made available for sale.
If you’re an applicant for .mail, however, it’s a different story. The JAS report says .mail should be reserved forever, putting it in the same category as .home and .corp:

the use of .corp and .home for internal namespaces/networks is so overwhelming that the inertia created by such a large “installed base” and prevalent use is not likely reversible. We also note that RFC 6762 suggests that .corp and .home are safe for use on internal networks.
…
Like .corp and .home, the TLD .mail also exhibits prevalent, widespread use at a level materially greater than all other applied-for TLDs. Our research found that .mail has been hardcoded into a number of installations, provided in a number of example configuration scripts/defaults, and has a large global “installed base” that is likely to have significant inertia comparable to .corp and .home. As such, we believe .mail’s prevalent internal use is also likely irreversible and recommend reservation similar to .corp and .home.

In other words, .mail is dead and the five remaining applicants for the string are probably going to be forced to withdraw through no fault of their own. Should these companies get a full refund from ICANN?

Mistake blamed for “Germans only” .voting policy

It seems the new gTLD .voting will not be restricted to Germans after all.
We reported earlier today that .voting registry Valuetainment had submitted a registration policy that required all registrants to have a presence in Germany.
The language used in the policy was identical, we later discovered, to that found in the equivalent policy for .ruhr, a German geographic gTLD operated by a different registry.
But Thomas Rickert of the German law firm Schollmeyer & Rickert, which has both .voting and .ruhr registries as clients, just called to let us know that the policy as submitted to ICANN was a mistake.
It seems there will be no local presence requirement for .voting after all.
Valuetainment will be submitting a revised policy to ICANN without the error. The German-language version of the policy does not contain the error, Rickert said.
Rickert said he’d like it to be known that the registry was blameless in this instance.

Pirate Bay a victim as Go Daddy suspends hundreds of new gTLD domains

New gTLDs may have only been in general availability for a few weeks, but there’s already evidence of substantial abuse.
Go Daddy has suspended at least 305 new gTLD domain names, putting them on its spam-and-abuse.com name servers, standard Go Daddy practice for domains suspected of abuse.
Over 250 of these were put on the naughty step in the last 24 hours.
The suspended names include, notably, thepiratebay.guru, which matches the name of controversial torrent site frequented by people who like downloading copyrighted material for free.
The Pirate Bay has been like crazy recently, as one ccTLD after another shuts down its latest attempt to find a reliable home.
The .guru domain is registered under Go Daddy’s Domains By Proxy privacy service, so it’s not clear if it actually belongs to The Pirate Bay or to an opportunistic third party.
Other suspended names include premium-looking names such as electric.guru, sexualhealth.guru, as well as obvious cybersquatted names such as verizon.guru (not registered to Verizon).
But the majority of the suspended names seem to belong to a single registrant in Washington state, all in .guru and largely “pigeon shit” names such as bestdrinksites.guru and bestfashionsites.guru.
While 305 seems like a large number (albeit only 0.2% of the current new gTLD names sold), it appears that so far a single individual is responsible for most of the “abuse” in new gTLDs.

ROTD conducts first new gTLD auction as One.com wins .one

Danish registrar One.com has won the .one contention set in the first private auction carried out by new gTLD consultancy Right Of The Dot.
One.com beat Radix, the United Arab Emirates-based portfolio applicant, to the string. Radix withdrew its application last week. The price has not been disclosed.
ROTD, Mike Berkens and Monte Cahn-managed company, has been competing with Applicant Auction for contention set resolution services and this is its first win.
The .one auction was carried out using a “single sealed bid second price” methodology, in which all participants privately submit a single bid and the winner pays the second-highest losing bid.
In this case, One.com will have paid Radix whatever bid Radix had put forward, with ROTD and escrow partner Escrow.com taking their fees from the winning bid.
Applicant Auction uses an “ascending clock” method, where bids are set in increments by the auctioneer over the space of several rounds, with bidders choosing to stay in or drop out in each round.
Cahn said in a press release: “Our Single Sealed Bid Second Price auction method protects the participants from ‘auction fever,’ which often causes over-bidding as people get emotionally tied to the process of winning at any cost due to time committed and sometimes throw their budgets out the window.”

Uniregistry doing private new gTLD auctions? Company deals with Donuts on five strings

Uniregistry and Donuts have settled at least five new gTLD contention sets this week, raising the question of whether Uniregistry has reversed its objection to private auctions.
I think it has.
In five of the six head-to-head contention sets between the two companies, Donuts has won the rights to .furniture, .auction and .gratis, and Uniregistry has won .audio and .juegos.
The losing company has already withdrawn their applications in all five cases.
I gather that a deal was made, but Uniregistry won’t say whether it was via a private auction or not and I’ve not yet had a reply to a request for comment from Donuts.
The withdrawals come the same week as Applicant Auction was scheduled to conduct its latest private auction for new gTLD contention sets. The auction was slated for February 18.
But Uniregistry, which has previously spoken out against the private auction concept — saying it raises antitrust concerns — declined to confirm or deny whether these five contests were resolved by auction.
“We’re grateful to have found a way through the impasse and resolved the contention,” was all Uniregistry CEO Frank Schilling would say.
Applicant Auction’s project director Sheel Mohnot confirmed that a new gTLD auction took place this week but said he could not disclose the participants or the strings.
To the best of my knowledge, that’s a new line — the auctioneer has always kept quiet about sales prices in the past, but has always revealed which companies were involved.
So has Uniregistry changed its mind about the legality of private new gTLD auctions? My guess is: “Yes.”
The only remaining string where the two companies are competing in a two-horse race is .shopping, according to the DI PRO database, but that’s subject to some weird string similarity nonsense and probably not suitable for a private auction yet.

100 .sexy names reserved by Uniregistry

areyou.sexy? youare.sexy?
If you’re thinking about trying to bag these names when Uniregistry takes .sexy into general availability next week, you’re out of luck — they’re among almost 100 registry-reserved names.
Under ICANN’s standard Registry Agreement, new gTLD registries are allowed to register up to 100 names to themselves “necessary for the operation or promotion of the TLD”.
To date, not many registries appear to have taken advantage of this contractual allowance, but .sexy is one of them.
Uniregistry has mostly reserved fairly standard operational names such as register.sexy, about.sexy, names.sexy and so on, but there are a few interesting choices that hint at possible future services.
Do auctions.sexy and marketplace.sexy hint at moves into the secondary market? Could areyou.sexy be the destination of a future advertising campaign? What are we going to see at build.sexy and pay.sexy?
Here are the names Uniregisty seems to have reserved:

247.sexy, a.sexy, about.sexy, abuse.sexy, account.sexy, areyou.sexy, auction.sexy, auctions.sexy, build.sexy, buy.sexy, cart.sexy, com.sexy, contact.sexy, corp.sexy, create.sexy, dev.sexy, diy.sexy, dom.sexy, domain.sexy, domains.sexy, email.sexy, finance.sexy, find.sexy, free.sexy, get.sexy, geta.sexy, getmy.sexy, help.sexy, home.sexy, host.sexy, hosting.sexy, http.sexy, iwanta.sexy, join.sexy, lease.sexy, legal.sexy, link.sexy, list.sexy, login.sexy, lookup.sexy, mail.sexy, main.sexy, make.sexy, manage.sexy, market.sexy, marketplace.sexy, mobile.sexy, move.sexy, name.sexy, names.sexy, net.sexy, news.sexy, operations.sexy, ops.sexy, partners.sexy, pay.sexy, payment.sexy, pro.sexy, reg.sexy, register.sexy, registera.sexy, registrar.sexy, registrars.sexy, registry.sexy, renew.sexy, rent.sexy, report.sexy, reports.sexy, reserve.sexy, reserved.sexy, s.sexy, search.sexy, secure.sexy, sell.sexy, seo.sexy, sexy.sexy, shop.sexy, signup.sexy, site.sexy, support.sexy, trade.sexy, transfer.sexy, try.sexy, uni.sexy, unireg.sexy, uniregistry.sexy, use.sexy, web.sexy, webmail.sexy, website.sexy, www.sexy, youare.sexy, your.sexy and youre.sexy.

Of particular note: your.sexy, with which Uniregistry seems to acknowledge the declining standards of grammar among the internet-using public, and www.sexy, which seems to be registered and resolving despite appearing on .sexy’s list of must-block name collisions.

Are these the 10 most-popular new gTLD domains?

I’m a firm believer that the success of new gTLDs will be measured not just in registration volumes but also in usage, and usage is a lot trickier to measure than domains under management.
One way of measuring usage that’s very familiar to many domainers is Alexa, the Amazon-owned web metrics service that uses toolbars and other data sources to rank web sites by popularity.
This kind of popularity data has been incorporated into TLD Health Check for some time, as one of many means to compare TLDs.
Alexa data isn’t perfect, but it is data, so I thought it might be interesting to see which of the 147 new gTLDs currently in the root are showing up in its daily list of the top one million domains.
There are 10 names, half of which are .guru domains, on yesterday’s list. There are not many functioning web sites yet, but for whatever reason these domains all, according to Alexa, have traffic.
These are the domains, with their popularity rank in parentheses:
www.link (356,406)
The highest-ranking new gTLD domain on our list is actually banned by ICANN due to the purported risk of name collisions.
It’s reserved by Uniregistry and will not resolve or be made available for registration for the foreseeable future.
I think what we’re looking at here is a case of somebody (or more likely lots of people) using www.link in web pages when they really should be using example.com.
beatport.singles (538,603)
Possible cybersquatting? Beatport (I’m old and unhip enough that I had to Google it) is an online electronic music store and the domain is registered via Go Daddy’s Domains By Proxy service.
The domain presumably refers to music “singles” rather than marital status, but it doesn’t seem to resolve from where I’m sitting. Quite why it’s getting traffic is beyond me. A typo in a URL somewhere? IP lawyers?
gtu.guru (589,205)
The first resolving name on our list leads to a work-in-progress Blogger blog. It’s registered to a chap in Gujarat, India, leading me to infer that GTU is Gujarat Technological University. Another squat?
seo.guru (671,647)
The first domainer on the list, I believe. The guy who registered seo.guru paid roughly $2,500 for it during Donuts’ first Early Access Program. It’s currently parked at Go Daddy.
I’d hazard a guess that it’s on the list because it’s a dream URL for an SEO professional (or charlatan, take your pick) and SEOs checking its availability are much more likely to have the Alexa toolbar installed.
deals.guru (790,778)
This one resolves to an under construction page.
I’d speculate that the pre-release $8,100 sale of deals.xyz caused a lot of domainers to check out whether the same second-level was available in other new gTLDs, spiking its traffic and causing an Alexa appearance.
nic.club (796,727)
The only registry-owned domain on our list — nic.club is the official registry web site of .CLUB Domains, which has its .club gTLD in sunrise until the end of March.
Is its appearance on the list indicative of strong pre-launch marketing or something else?
beekeeping.guru (857,778)
I’m not making this stuff up. This domain belongs to a British pest control company but resolves to a default Apache page. I can’t begin to guess why it’s getting traffic.
cp.wien (864,800)
An unregistered name in a sunrise gTLD. Possible name collision?
shop.camera (873,146)
Hot dang, we have a web site!
The domain shop.camera was only registered 10 days ago, but it already leads to what appears to be a fully-functioning Amazon affiliate site, complete with “Shop.Camera” branding.
freebitcoin.guru (994,404)
An email-gathering affiliate marketing site that I personally wouldn’t touch with yours. Still, it looks quite slick compared to the others on the list and it appears that the owner has made some effort to promote it.

CentralNic gets its foot in the door as Famous Four back-end

New gTLD portfolio applicant Famous Four Media has selected CentralNic to provide back-end registry services, joining existing providers ARI Registry Services and Neustar.
CentralNic will be “a preferred provider” of Domain Venture Partners, which is the parent company of Famous Four’s 60 new gTLD applicants, according to a joint statement issued by the companies today.
Neither firm wanted to give any firm details about how CentralNic fits into Famous Four’s strategy, such as whether CentralNic might replace existing back-ends as it did with 27 formerly GMO Registry bids.
Famous Four is already partnered with Neustar on 52 new gTLD applications and ARI on five more.
DVP chief operating officer Charles Melvin told DI in a statement:

CentralNic will sit as one of our preferred backend technology partners. We are in the process of agreeing terms with a limited number of select providers to sit on our preferred panel. Until such agreements have been put in place it would be inappropriate for us to comment on them.

The deal is related to DVP II, an investment vehicle through which DVP hopes to raise up to $400 million “to acquire Top-Level Domain registries, some of which are already live.”
We were leaked a copy of a June 2013 investor presentation related to DVP II, in which the company said its back-end partner had “the lowest fees in the industry”.
With its new “preferred panel”, it looks like the company is hedging its bets.

NCC buys .trust new gTLD from Deutsche Post

NCC Group, owner of .secure applicant Artemis, has bought the rights to .trust from Deutsche Post, which has an uncontested bid for the new gTLD but decided it doesn’t want it.
The price tag of the deal was not disclosed.
NCC, which is also one of the two major data escrow providers supporting new gTLD applicants, said in a statement:

Deutsche Post originally obtained the gTLD through ICANN’s new gTLD allocation process during 2013 but has now chosen not to utilise it.
NCC Group will use .trust as the primary vehicle for launching its Artemis internet security service, which aims to create global internet safety through a secure and trusted environment for selected customers.
The Group remains in the contention stage with its application to ICANN for the .secure gTLD. It believes that there will be a benefit in having a number of complementary named gTLDs, all of which offer the same high levels of internet security.

While Artemis has applied for .secure, it’s facing competition from the much richer Amazon.
Its initial hope that Amazon’s bid would be rejected due to the controversy over “closed generics” seems to have been dashed after Amazon was allowed to change its application.
NCC may be characterizing .trust as an “additional” security TLD, but it’s quite possible it will be its “only” one.
Deutsche Post, which as owner of DHL is the world’s largest courier service, has passed Initial Evaluation on .trust but has not yet signed its ICANN contract.
ICANN’s web site still shows Deutsche Post as the applicant for .trust and it’s not clear from NCC’s statement how the transfer would be handled.