Nominet takes over failed .desi

Nominet has been picked as the Emergency Back-End Registry Operator for failed gTLD .desi, the company confirmed today.

The gig means the .uk registry will be responsible for keeping .desi ticking over — handling DNS, EPP, Whois etc — while ICANN looks for a successor registry.

.desi was operated by mom-n-pop outfit Desi Networks of Maryland on a Team Internet back-end until it threw in the towel this July, having failed to sell more than a handful of domains.

The term “desi” refers to the cultures of the Indian subcontinent and its diaspora, giving an addressable market well over a billion people. But there were only 1,743 registered domains at the last count but the only active sites that show up in Google are porn.

It’s the second gTLD to go into special measures after .wed, which Nominet is also handling. ICANN has three accredited EBERO providers, the others being CNNIC of China and CIRA in Canada.

While .wed has only one active registrar and barely 30 registered domains, .desi has almost 300 registrars, about 70 of which have domains.

ICANN rejects a whole bunch of new gTLD policy stuff

ICANN has delivered some bad news for dot-brands, applicants from poorer countries, and others, at the weekend rejecting several items of new gTLD policy advice that the community spent years cooking up.

The board of directors on Sunday approved a scorecard of determinations, including the rejection (or non-adoption) of seven GNSO recommendations that it deems “would not be in the best interests of the ICANN community or ICANN”.

In reality, it’s the latter that seems to have been foremost in the board’s mind; most of the rejections appear to be geared toward reducing ICANN Org’s legal or financial exposure.

Notably, dot-brands are denied some of the relief from cumbersome or expensive requirements that the GNSO had wanted rid of.

The board rejected a recommendation that would exempt them from the Continued Operations Instrument — a financial bond used to pay an Emergency Back-End Registry Operator should the applicant go out of business.

“[T]he Board is concerned that an exemption from an COI for Spec 9 applications would have financial impact on ICANN since there would be no fund to draw from if such a registry went into EBERO,” the board wrote.

It also rejected a request to exempt dot-brands from rules requiring them to contractually ban and monitor abuse in their TLDs. The GNSO had argued that single-registrant TLDs do not suffer abuse, but the board said this could lead to abuse from compromised domains going unaddressed.

“The Board concludes that Recommendation 9.2, if implemented, could lead to DNS abuse for second-level registrations in a single-registrant TLD going unaddressed, unobserved, and unmitigated,” it said.

Applicants hoping to benefit from the Applicant Support Program — which in 2012 offered heavily discounted application fees to poorer applicants — also got some bad news.

The GNSO wants the support to extend to other costs such as application-writing services and lawyers, which naturally enough put the frighteners on the board, which noted “such expansion of support could raise the possibility of inappropriate use of resources (e.g. inflated expenses, private benefit concerns, and other legal or regulatory concerns)”.

The board also rejected a couple of recommendations that could be seen as weakening its role as ultimate authority over all things gTLD.

It rejected a proposal to remove the controversial covenant not to sue (CNTS) from the application process unless other recommendations related to appeals processes are implemented.

ICANN said that because it has not yet approved these other recommendations, it has rejected this recommendation.

The board also rejected a recommendation that would have limited its ability to reject a gTLD application to only when permitted to do so by the rules set out in the Applicant Guidebook.

The idea was to prevent applications being arbitrarily rejected, but the board said this “may unduly limit ICANN’s discretion to reject an application in yet-to-be-identified future circumstance(s)”.

The rejections invoke part of the ICANN bylaws that now requires the GNSO Council to convene and either affirm or amend its recommendations before discussing them with the board. Presumably this could happen at ICANN 78 next month.

The bylaws process essentially gives the board the ultimately authority to throw out the GNSO recommendations if it can muster up a two-thirds supermajority vote, something it rarely has a problem achieving.

Russian registry hit with second breach notice after downtime

ICANN has issued another breach notice against the registry for .gdn, which seems to be suffering technical problems and isn’t up-to-date on its bills.

Navigation-Information Systems seems to have experienced about 36 hours of Whois/RDDS downtime starting from April 22, and is past due with its quarterly ICANN fees, according to the notice.

Contractually, if ICANN’s probes detect downtime of Whois more than 24 hours per week, that’s enough to trigger emergency measures, allowing ICANN to migrate the TLD to an Emergency Back-End Registry Operator.

Today, the registry’s web site hasn’t resolved for me in several hours, timing out instead, suggesting serious technical problems. Other non-registry .gdn web sites seem to work just fine.

NIS seems to be a Russian company — although most ICANN records give addresses in Dubai and Toronto — so it might be tempting to speculate that its troubles might be a result of some kind of cyber-war related to the Ukraine invasion.

But it’s not the first time this has happened by a long shot.

The company experienced a pretty much identical problem twice a year earlier, and it seems to have happened in 2018 and 2019 also.

NIS just can’t seem to keep its Whois up.

According to the breach notice, whenever Compliance manages to reach the registry’s 24/7 emergency contact they’re told he/she can’t help.

ICANN has given the registry until May 29 to fix its systems and pay up, or risk termination.

.gdn was originally applied for as something related to satellites, but it launched as an open generic that attracted over 300,000 registrations, mostly via disgraced registrar AlpNames, earning it a leading position in spam blocklists. Today, it has around 11,000 names under management, mostly via a Dubai registrar that seems to deal purely in .gdn names.

ICANN to auction off first failed new gTLD

ICANN is planning to auction off .wed, the first new gTLD from the 2012 application round to fail.

The TLD has been running on Nominet’s Emergency Back-End Registry Operator platform since late 2017, when former registry Atgron suffered a critical failure — apparently planned — of its registry services.

After some lawyering, Atgron finally lost its registry contract last October.

Now, ICANN has confirmed that .wed will be the subject of an open Request For Proposals, to find a successor registry operator.

It’s the first time it’s had to roll out its Registry Transition Process mechanism. All previous gTLD terminations were single-registrant dot-brands that were simply quietly removed from the DNS root.

The RFP will basically amount to an auction. Registries will have to pass the usual technical and financial background checks, but ultimately the winner will be selected based on how much they’re willing to pay.

In ICANNese: “The RFP process will identify the highest economic proposal and utilize it as the deciding factor to proceed to evaluation.”

But the money will not stuff ICANN’s overflowing coffers. After it’s covered the costs of running the RFP, any remaining cash will go to Atgron. There’s a non-zero chance the company could make more money by failing than it ever did selling domain names.

It currently has 39 domains under management, the same 39 it’s had since Nominet took over as EBERO, and the successor registry will be expected to grandfather these names. Only 32 of the names appear to be genuine end-user registrations.

Atgron’s business model, which was almost antithetical to the entire business model for domain names, is to blame for its failure.

The company tried to sell domains to marrying couples for $50 a year, on the understanding that the renewal fee after the first two years would be $30,000.

Atgron wanted to actively discourage renewals, in order to free up space for other couples with the same names.

Unsurprisingly, registrars didn’t dig that business model, and only one signed up.

Fortunately, whichever registry takes over from Atgron will be under no obligation to also take over its business model.

ICANN said it expects to publish its RFP “in the coming months” and pick a winner before the end of the year.

ICANN threatens to seize gTLD after Whois downtime

Are we about to see our next gTLD registry implosion?

ICANN has whacked the company behind .gdn with a breach notice and a threat that it may seize the TLD, after its Whois systems allegedly suffered days of downtime.

According to ICANN, .gdn exceeded its weekly and monthly downtime limits in late March and early April, in both months triggering the threshold whereby ICANN is allowed to transition the TLD to an Emergency Back-End Registry Operator.

gTLD registries are allowed to have 864 minutes (about 14 hours) of unplanned Whois downtime per month. Downtime exceeding 24 hours per week is enough to trigger ICANN’s EBERO powers.

It appears to be the third time .gdn’s Whois has gone on the blink for longer than the permitted period — ICANN says it happened in April 2018 and August 2019 too. Those incidents were not publicized.

It seems the Russian registry, Joint Stock Company “Navigation-information systems”, managed to fix the problem on April 2, and ICANN is not invoking the EBERO transition, something it has done just a couple times before, just yet.

But it does want NIS to present it with a plan showing how it intends to avoid another spell of excessive downtime in future. It has until May 8, or ICANN may escalate.

.gdn is by most measures a bullshit TLD.

While it was originally intended to address some kind of satellite navigation niche, it eventually launched as a pure generic with the backronym “Global Domain Name” in 2016.

It managed to rack up over 300,000 registrations in the space of a year, almost all via disgraced and now-defunct registrar AlpNames, and was highlighted by SpamHaus as being one of the most spam-friendly of the new gTLDs.

After AlpNames went out of business two years ago, ICANN transferred some 350,000 .gdn names to CentralNic-owned registrar Key-Systems.

Today, Key-Systems has fewer than 300 .gdn domains. The TLD’s zone file dropped by about 290,000 domains in a single day last December.

.gdn had fewer than 11,000 domains under management at the end of 2020, 90% of which were registered through a Dubai-based registrar called Intracom Middle East FZE.

Intracom pretty much only sells .gdn domains, suggesting an affiliation with the registry.

Web searches for live sites using .gdn return not much more than what looks like porn spam.

A busted Whois looks like the least of its problems, to be honest.

Forty weddings and a funeral? .wed is dead but may come up for auction

.wed has become the first commercial, open, non-branded new gTLD to have its registry contract unilaterally terminated by ICANN, and it could soon be looking for a new home.

ICANN terminated the contract with US-based Atgron last week, almost three years after imposing emergency measures to protect registrants after the company’s business model failed miserably.

The company wanted to provide a space for engaged couples to promote their weddings for about $50 a year, but its business model was based around basically forcing registrants to abandon their names by charging a $30,000 renewal fee after year two.

Unsurprisingly, it attracted few registrants — about 300 at its 2016 peak — and only one registrar.

By the time the end of 2017 rolled around, it was languishing at 39 domains (for the purposes of a whimsical headline, let’s round it up to 40) and its agreement with its back-end registry operator was on the verge of expiring.

In the hope of keeping its customers’ domains working, Atgron turned off its Whois for a week, attracting the attention of ICANN and triggering a criterion for transitioning to an Emergency Back-End Registry Operator.

It’s been on an EBERO, in this case Nominet, since December 2017, with all domains essentially frozen.

In the meanwhile, it’s been fighting against contract termination with ICANN, first in mediation and then in arbitration.

Last month, the arbitrator ruled that Atgron was in breach for failure to pay its ICANN fees, and ICANN terminated the registry agreement October 5.

.wed is certainly not the first new gTLD to get terminated by ICANN — there’s been about a dozen to date — but it is the first to be a non-dot-brand.

This means ICANN will get to test its Registry Transition Process for the first time.

When a dot-brand dies, ICANN just removes it from the root and lets it stay dead on the grounds that there’s no plausible successor and no registrants will suffer.

In this case, we’re talking about an open, non-branded gTLD with a generic string that could potentially rack up many thousands of registrations.

There’d be no obligation for a future operator to take on the silly business model.

The Registry Transition Process will go one of two ways.

If Atgron has already picked a successor registry, ICANN will conduct a series of evaluations that look like they would be a piece of cake for any existing gTLD portfolio owner to pass.

But if Atgron has no heir apparent, it goes to an RFP which basically amounts to an auction, with the company prepared to pay Atgron the most money becoming the company’s presumed preferred successor.

With Atgron still owing ICANN money — presumably hundreds of thousands of dollars — in past-due fees, I’ve little doubt what ICANN’s preferred outcome would be.

For Atgron, there’s the distinct possibility that it could make more money from crashing .wed into the ground than it ever did by actually selling domains.

.wed is not a bad string — it’s short, meaningful, and has a niche of potential registrants already forced to overpay for almost everything else — and I’m fairly confident it could easily find a new home at an existing registry.

CIRA replaces CORE as emergency backup registry

ICANN has switched around its line up of emergency registry providers, swapping out CORE Association for CIRA.
The organization last night announced that its three newly contracted Emergency Back-End Registry Operators are Nominet, CNNIC, and CIRA.
EBEROs are failsafe registries that will take over any gTLD that has failed or is on the verge of failing outright, putting its customers domains at risk.
The EBERO is responsible for winding down these gTLDs in an orderly fashion, giving registrants the chance to migrate to a different TLD.
So far, only .wed has entered the program, when the project with the imaginative business model of making it impractical to renew domains went out of business in 2017.
Nominet now caretakes .wed under the EBERO program.
Both Nominet (.uk) and CNNIC (.cn) have been approved EBEROs since 2013, under five-year contracts with ICANN.
CORE was also approved in 2013, but appears to have lost its contract. It’s been replaced by CIRA, the Canadian Internet Registry Association.
“We are honoured to be among this select group of trusted registry operators,” Dave Chiswell, VP of product development for CIRA, said in a statement. He said CIRA only suffered eight hours of downtime when it migrated .ca to a new back-end platform recently.
A key reason for CIRA replacing CORE is very likely geography. When ICANN put out its request for proposals last year, it made a big deal about how it wanted coverage in Europe, Asia and North America — where most gTLD registries are concentrated.
CORE is based in Switzerland. CIRA is obviously based in Canada and CNNIC is Chinese.
Another side-effect of the contract renegotiations is that ICANN is now paying 30% less for the services of the three providers, according to a recent board resolution.
The three providers are contracted for five years.
Whether, and to what extent, they’ll ever actually be triggered to provide EBERO services is open to debate.
Currently, there are six gTLDs in advanced stages of ICANN compliance proceedings, putting them at risk of having their contracts revoked: .whoswho, and five Persian-themed strings.
It’s not inconceivable than one or more of these gTLDs could wind up in EBERO, but ICANN appears to be cutting the registries a lot of slack to resolve their issues.

Five more gTLD deadbeats fingered by ICANN

The company that tried unsuccessfully to get the .islam new gTLD has been slammed by ICANN for failing to pay its dues on five different gTLDs.
Asia Green IT System, based in Turkey, has been considered “past due” on its registry fees since at least January, according to an ICANN breach notice sent yesterday.
The company runs .nowruz (Iranian New Year), .pars (refers to Persia/Iran), .shia (a branch of Islam), .tci (a closed dot-brand) and .همراه (.xn--mgbt3dhd, appears to mean something like “comrade” in Persian).
The only one of these to actually launch is .nowruz. It came to market March last year — bizarrely, it didn’t leave sunrise until a week after Nowruz was over — and has scraped just over 40 registrations. It does not appear to have any active web sites.
With little to no revenue, one can imagine why it might have difficulty paying ICANN’s $25,000 annual per-TLD registry fee, which it will have been paying for almost four years before lapsing.
None of its mandatory “nic.example” sites resolve for me today, though its “whois.nic.example” sites can be reached once you click through an SSL security warning.
The primary registry web site for AGIT, agitsys.com, also does not resolve for me.
ICANN’s breach notice claims that it has been unable to contact anyone at the registry, despite many outreach attempts, since January. It believes it has outdated contact data for the company.
AGIT is perhaps best-known to DI readers for its unsuccessful attempts to apply for .islam and .halal.
ICANN rejected these applications last October after an outcry from governments of Muslim-majority nations and the Organization for Islamic Cooperation.
Given AGIT’s apparent difficulties, perhaps that was a good call.
If the registry doesn’t cough up by June 13, ICANN may start termination proceedings.
It’s the 19th published breach notice ICANN has sent to a gTLD registry. In most cases, even the handful of cases that have escalated to termination, the registry has managed to resolve the issue before losing their contracts.
The only gTLD to actually get terminated to date I believe is .wed, which is currently being wound down by Nominet in its role as Emergency Back-End Registry Operator.
The most-recent registry breach notice, filed against .whoswho in January, is still “under review” by ICANN.

As .wed goes EBERO, did the first new gTLD just fail?

A wedding-themed gTLD with a Bizarro World business model may become the first commercial gTLD to outright fail.
.wed, run by a small US outfit named Atgron, has become the first non-brand gTLD to be placed under ICANN’s emergency control, after it lost its back-end provider.
DI understands that Atgron’s arrangement with its small New Zealand back-end registry services provider CoCCA expired at the end of November and that there was a “controlled” transition to ICANN’s Emergency Back-End Registry Operator program.
The TLD is now being managed by Nominet, one of ICANN’s approved EBERO providers.
It’s the first commercial gTLD to go to EBERO, which is considered a platform of last resort for failing gTLDs.
A couple of unused dot-brands have previously switched to EBERO, but they were single-registrant spaces with no active domains.
.wed, by contrast, had about 40 domains under management at the last count, some apparently belonging to actual third-party registrants.
Under the standard new gTLD Registry Agreement, ICANN can put a TLD in the emergency program if they fail to meet up-time targets in any of five critical registry functions.
In this case, ICANN said that Atgron had failed to provide Whois services as required by contract. The threshold for Whois triggering EBERO is 24 hours downtime over a week.
ICANN said:

Registry operator, Atgron, Inc., which operates gTLD .WED, experienced a Registration Data Directory Services failure, and ICANN designated EBERO provider Nominet as emergency interim registry operator. Nominet has now stepped in and is restoring service for the TLD.
The EBERO program is designed to be activated should a registry operator require assistance to sustain critical registry functions for a period of time. The primary concern of the EBERO program is to protect registrants by ensuring that the five critical registry functions are available. ICANN’s goal is to have the emergency event resolved as soon as possible.

However, the situation looks to me a lot more like a business failure than a technical failure.
Multiple sources with knowledge of the transition tell me that the Whois was turned off deliberately, purely to provide a triggering event for the EBERO failover system, after Atgron’s back-end contract with CoCCA expired.
The logic was that turning off Whois would be far less disruptive for registrants and internet users than losing DNS resolution, DNSSEC, data escrow or EPP.
ICANN was aware of the situation and it all happened in a coordinated fashion. ICANN told DI:

WED’s backend registry operator recently notified ICANN that they would likely cease to provide backend registry services for .WED and provided us with the time and date that this would occur. As such, we were aware of the pending failure worked to minimize impact to registrants and end users during the transition to the Emergency Back-end Registry Operator (EBERO) service provider.

In its first statement, ICANN said that Nominet has only been appointed as the “interim” registry, while Atgron works on its issues.
It’s quite possible that the registry will bounce back and sign a deal with a new back-end provider, or build its own infrastructure.
KSregistry, part of the KeyDrive group, briefly provided services to .wed last week before the EBERO took over, but I gather that no permanent deal has been signed.
One wonders whether it’s worth Atgron’s effort to carry on with the .wed project, which clearly isn’t working out.
The company was founded by an American defense contractor with no previous experience of the domain name industry after she read a newspaper article about the new gTLD program, and has a business model that has so far failed to attract customers.
The key thing keeping registrars and registrants away in droves has been its policy that domains could be registered (for about $50 a year) for a maximum period of two years before a $30,000 renewal fee kicked in.
That wasn’t an attempt to rip anybody off, however, it was an attempt to incentivize registrants to allow their domains to expire and be used by other people, pretty much the antithesis of standard industry practice (and arguably long-term business success).
That’s one among many contractual reasons that only one registrar ever signed up to sell .wed domains.
Atgron’s domains under management peaked at a bit over 300 in March 2016 and were down to 42 in August this year, making it probably the failiest commercial new gTLD from the 2012 round.
In short, .wed isn’t dead, but it certainly appears extremely unwell.
UPDATE: This post was updated December 12 with a statement from ICANN.

Second emergency registry tested with dead dot-brand

ICANN is running its second test of the Emergency Back-End Registry Operator system, designed as a failover for bankrupt gTLDs.
This time, the EBERO under the microscope is CORE Association, one of the three approved providers.
It this week took over operation of .mtpc, a dot-brand gTLD that Mitsubishi applied for, was delegated, never used, and then decided it didn’t want to run any more.
ICANN said:

ICANN is conducting a test of the Emergency Back-End Registry Operator program. Simulating an emergency registry operator transition will provide valuable insight into the effectiveness of procedures for addressing potential gTLD service interruptions. Lessons learned will be used to support ICANN’s efforts to ensure the security, stability and resiliency of the Internet and the Domain Name System.

The first test was conducted by ICANN and EBERO provider Nominet earlier this year, using the similarly unloved dot-brand .doosan.
I expect we’ll see a third test before long, using CNNIC, the third EBERO provider.
It would have plenty of dead dot-brands to choose from.