Latest news of the domain name industry

Recent Posts

Top-level domains top 500

The number of live top-level domains on the internet has surpassed 500 for the first time.

The delegation yesterday of 12 new gTLDs — .archi, .consulting, .cooking, .country, .fishing, .haus, .商城, .horse, .miami, .rodeo, .vegas and .vodka — tipped the total TLD count to 507.

For the numbers geeks, here are some stats from the DI PRO database:

  • 285 ccTLDs
  • 222 gTLDs
  • 60 IDN TLDs
  • 24 IDN gTLDs
  • 199 gTLDs delegated in the 2012 round
  • 15 gTLDs delegated in previous rounds
  • 8 legacy gTLDs
  • 129 new gTLDs have started Sunrise periods
  • 65 new gTLDs have started Trademark Claims periods
  • 367 new gTLDs have ICANN contracts
  • 1 new gTLD application is still in Initial Evaluation
  • 6 new gTLD applications are still in Extended Evaluation
  • 9.7 new gTLDs have been delegated per week, on average, since January 1, 2014
  • 36 new gTLDs were delegated in March

Based on the rate that Verisign has been adding new gTLDs to the root recently, we should expect that to top 200 in the next few days. The number of new gTLDs could outstrip the number of ccTLDs next month.

ARI and Radix split on all new gTLD bids

Kevin Murphy, March 31, 2014, Domain Registries

Radix no longer plans to use ARI Registry Services for any of its new gTLDs, I’ve learned.

The company has already publicly revealed that CentralNic is to be its back-end registry services provider for .space, .host, .website and .press, but multiple reliable sources say the deal extends to its other 23 applications too.

I gather that the split with ARI wasn’t entirely amicable and had money at its root, but I’m a bit fuzzy on the specifics.

The four announced switches are the only four currently uncontested strings Radix has applied for.

Of Radix’s remaining active applications, the company has only so far submitted a change request to ICANN — which I gather is a very expensive process — on one, .online.

For the other 22, ARI is still listed as the back-end provider in the applications, which have all passed evaluation.

Radix is presumably waiting until after its contention sets get settled before it goes to the expense of submitting change requests.

No sunrise periods for dot-brands

Kevin Murphy, March 31, 2014, Domain Policy

ICANN has finally signed off on a set of exemptions that would allow dot-brand gTLDs to skip sunrise periods and, probably, work only with hand-picked registrars.

Its board’s New gTLD Program Committee passed a resolution at ICANN 49 last week that would add a new Specification 13 (pdf) to Registry Agreements signed by dot-brands.

The new spec removes the obligation operate a sunrise period, which is unnecessary for a gTLD that will only have a single registrant. It also lets dot-brands opt out of treating all registrars equally.

Dot-brands would still have to integrate with the Trademark Clearinghouse and would still have to operate Trademark Claims periods — if a dot-brand registers a competitor’s name in its own gTLD during the first 90 days post-launch, the competitor will find out about it.

ICANN is also proposing to add another clause to Spec 13 related to registrar exclusivity, but has decided to delay the addition for 45 days while it gets advice from the GNSO on whether it’s consistent with policy.

That clause states that the dot-brand registry may choose to “designate no more than three ICANN accredited registrars at any point in time to serve as the exclusive registrar(s) for the TLD.”

This is to avoid the silly situation where a dot-brand is obliged to integrate with registrars from which it has no intention of buying any domain names.

Spec 13 also provides for a two-year cooling off period after a dot-brand ceases operations, during which ICANN will not delegate the same string to another registry unless there’s a public interest need to do so.

The specification contains lots of language designed to prevent a registry gaming the system to pass off a generic string as a brand.

There doesn’t seem to be a way to pass off a trademark alone, without a business to back it up, as a brand. Neither is there a way to pass off a descriptive generic term as a brand.

The rules seem to allow Apple to have .apple as a dot-brand, because Apple doesn’t sell apples, but would not allow a trousers company to have .trousers as a dot-brand.

ICANN muddles through solution to IGO conflict

Kevin Murphy, March 31, 2014, Domain Policy

ICANN may have come up with a way to appease both the GNSO and the GAC, which are at conflict over the best way to protect the names and/or acronyms of intergovernmental organizations.

At the public forum of the ICANN 49 meeting in Singapore last Thursday, director Bruce Tonkin told the community that the ICANN board will consider the GNSO’s recommendations piecemeal instead of altogether.

It will also convene a meeting of the GNSO, GAC, IGOs, international nongovernmental organizations and the At-Large Advisory Committee to help reach a consensus.

The issue, you may recall from a DI post last week, is whether the names and acronyms of IGOs and INGOs should be blocked in all new gTLDs.

The GNSO is happy for the names to be protected, but draws the line at protecting acronyms, many of which are dictionary words or have multiple uses. The GAC wants protection for both.

Both organizations have gone through their respective processes to come to full consensus policy advice.

This left ICANN in the tricky situation of having to reject advice from one or the other; its bylaws did not make a compromise easy.

By splitting the GNSO’s 20 or so recommendations up and considering them individually, the ICANN board may be able to reconcile some with the GAC advice.

It would also be able to reject bits of GAC advice, specific GNSO recommendations, or both. Because the advice conflicts directly in some cases, rejection of something seems probable.

But ICANN might not have to reject anything, if the GAC, GNSO and others can come to an agreement during the special talks ICANN has in mind, which could happen as soon as the London meeting in June.

Even if those talks lead to nothing, this proposed solution does seem to be good news for ICANN perception-wise; it won’t have to blanket-reject either GNSO or GAC policy advice.

This piecemeal or ‘scorecard’ approach to dealing with advice hasn’t been used with GNSO recommendations before, but it is how the board has dealt with complex GAC advice for the last few years.

It’s also been used with input from non-GNSO bodies such as the Whois Review Team and Accountability and Transparency Review Team.

Judging by a small number of comments made by GNSO members at the public forum on Thursday, the solution the board has proposed seems to be acceptable.

ICANN may have dodged a bullet here.

The slides used by Tonkin during the meeting can be found here.

Republicans introduce pointless ICANN bill

Kevin Murphy, March 28, 2014, Domain Policy

Three Republican Congressmen have introduced a bill that would prevent the US government removing itself from oversight of the DNS root zone.

For a year.

The inappropriately titled Domain Openness Through Continued Oversight Matters (DOTCOM) Act is designed to:

prohibit the National Telecommunications and Information Administration from relinquishing responsibility over the Internet domain name system until the Comptroller General of United States submits to Congress a report on the role of the NTIA with respect to such system.

Basically, the NTIA would be barred from walking away from root zone oversight until an analysis of the advantages and disadvantages of the transition was published, which would have to happen within a year.

The report would also have to include a definition of “multi-stakeholder”.

The three Republicans who introduced the bill — Representatives Todd Rokita, John Shimkus, and Marsha Blackburn — either have no idea what they’re talking about, or they’re being intellectually dishonest.

Blackburn said in a press release:

We can’t let the Internet turn into another Russian land grab. America shouldn’t surrender its leadership on the world stage to a “multistakeholder model” that’s controlled by foreign governments. It’s imperative that this administration reports to Congress before they can take any steps that would turn over control of the Internet.

Shimkus said:

In the month of March alone we’ve seen Russia block opposition websites, Turkey ban Twitter, China place new restrictions on online video, and a top Malaysian politician pledge to censor the Internet if he’s given the chance. This isn’t a theoretical debate. There are real authoritarian governments in the world today who have no tolerance for the free flow of information and ideas. What possible benefit could come from giving the Vladimir Putins of the world a new venue to push their anti-freedom agendas?

This is hysterical nonsense.

Not only has ICANN no intention of allowing the IANA function to be controlled by foreign governments, the NTIA has explicitly stated from the start that no governmental solution would be acceptable.

It’s also ironic that the only two governments to ever consider censoring the root zone were the European Commission and the United States, under the Republican Bush administration.

The current expectation, assuming community talks proceed as swiftly as hoped, is for stewardship of the IANA function to leave the NTIA’s hands when the current contract expires in October 2015.

Even if the DOTCOM (really?) Act were to be passed into US law this year, it shouldn’t have any serious impact on the timing of the root transition.

With that in mind, the three-page bill (pdf) looks quite a lot like an extended press release, rather than a serious attempt to keep the root in US hands.