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.

Scottish registry dumps the pound over Brexit fears

The .scot gTLD registry has decided to dump the British pound as its currency of choice, due to fears over Brexit.
DotScot’s back-end, CORE, told registrars this week that it will start billing in euros from March 29.
The switch is being made due to “the expected volatility in currency exchange rates between GBP and other main currencies post-Brexit”.
March 29 is currently enshrined in UK law as the date we will formally leave the European Union, though the interminable political machinations at Westminster are making it appear decreasingly unlikely that this date could be extended.
CORE said that the prices for .scot registrations, renewals and transfers will be set at €1.14 for each £1 it currently charges. That’s the average exchange rate over the last 12 months, registrars were told.
.scot is a geographic gTLD, rather than a ccTLD, which was approved in ICANN’s 2012 application round. It has about 11,000 domains under management.
Its largest registrar, 1&1 Ionos (part of Germany’s United Internet), charges £40 a year.
Only 38% of Scots voted in favor of Brexit back in 2016, the lowest of any of the UK’s four nations, with no region of Scotland voting “Leave”.
Naturally, a great many Scots believe they’re being dragged out of the EU kicking and screaming by their ignorant, English-bastard neighbors. Which strikes me as a fair point.

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.

Four more new gTLD contracts signed, including .email

Four new gTLD registries signed their contracts with ICANN yesterday.
Donuts added Registry Agreements for .email and .codes to its portfolio, bringing its total up to 43.
CORE Association signed for بازار., which means “bazaar”. It’s CORE’s third and final RA as an applicant and its only Arabic application. It’s already live with two Cyrillic strings.
Finally, DotBerlin signed its contract for the city TLD .berlin, apparently confirming the rumor that the one it signed on stage alongside .wien at the newdomains.org conference earlier this week was in fact a prop.
According to the DI PRO database, ICANN now has contracts with 80 new gTLDs and 18 legacy gTLDs.

First new gTLDs to go live “in the next few hours”

The first four new gTLDs are expected to go live in the next few hours.
That’s according to the registries themselves, and reports out of the Internet Governance Forum in Bali, where ICANN division president Akram Atallah was speaking on a panel earlier today.
The gTLDs are: .сайт (Russian “.site”) and .онлайн (Russian “.online”) from CORE Association, شبكة. (Arabic “.web”) from dotShabaka Registry and .游戏 (Chinese “.games”) from Donuts.
By “go live” I mean of course that the ASCII versions of these strings (for example, .xn--ngbc5azd for شبكة.) will be entered into the DNS root.
It may take a short while for the registries to activate second-level domains (such as nic.) under their new TLDs, and nothing will actually go on sale for weeks.
They’re all of course internationalized domain names, given ICANN’s decision almost a year ago to prioritize IDNs at all stages of the evaluation and delegation process.
All four received their block-lists of “collision risk” second-level domains on Friday and elected to implement the blocks to get to delegation faster.
The three registries signed their contracts on stage at the ICANN meeting in Durban July 15.
This is a pretty big day for ICANN and its community. After many years and countless arguments and delays, new gTLDs are actually about to go live!

Live new gTLDs this month? First four pass to delegation

New gTLDs are on the home stretch, after ICANN sent the first four applications to the final delegation stage of the process.
The four are: .сайт (Russian “.site”) and .онлайн (Russian “.online”) from Core Association, شبكة. (Arabic “.web”) from dotShabaka Registry and .游戏 (Chinese “.games”) from Donuts.
These were also the first four to sign their registry contracts with ICANN — over three months ago — and the first to be given their name collisions mitigation plan, just a few days ago.
Proceeding to delegation means the applications are now in the hands of IANA, the ICANN department with responsibility over changes to the DNS root system.
IANA has its own set of procedures to follow before delegating, which have historically taken a couple of weeks to process. If I recall correctly, .xxx was with IANA for about 10 days before it went live.
It seems possible that the first new gTLDs could be live this month, meaning the first sunrise periods could kick off in early December, with general availability following a month later.
However, the Christmas and New Year holiday period may wind up forcing some registrars to stagger their dates in order to benefit from the best publicity window when they finally go on sale.

First collision block-lists out now. How painful will they be for new gTLDs?

ICANN has published the name collision block-lists for the first four new gTLDs, and they making pretty interesting reading.
The four registries in question will be required to block between 104 and 680 unique second-level domains from their gTLDs if they want to use the fastest path to delegation on offer.
The four gTLDs with lists published this morning are: .сайт (Russian “.site”), .онлайн (Russian “.online”), شبكة. (Arabic “.web”) and .游戏 (Chinese “.games”).
These were the first four new gTLDs with signed Registry Agreements. ICANN seems to be following the order contracts were signed, rather than the official prioritization number.
So what’s on the lists?
Gibberish
The first thing to note is that, as expected, ICANN has helpfully removed invalid strings (such as those with underscores) and gibberish Google Chrome strings from the lists, greatly reducing their size.
The block-lists are based on Day In The Life Of The Internet data, which recorded DNS root queries for applied-for gTLDs over 48-hour periods between 2006 and 2013.
According to ICANN, “a significant proportion” of the DITL queries were for the nonsense 10-character strings that Chrome generates and sometimes accidentally sends to the public DNS.
Because these “appear to present minimal risk if filtered from the block lists”, ICANN has made an effort to automatically remove as many as possible, while acknowledging it may not have caught them all. The human eye is good at spotting meaningless strings, software is not so adept.
All four lists still contain plenty of gibberish strings, according to this human eye, but mostly they’re not of 10 characters in length.
IDNs
All four lists published today are for non-Latin domain names and are presumably expecting their registries to be mostly populated with IDN.IDN domain names.
As such, the impact of their mostly Latin block-lists may be even smaller than it first appears.
For example, if we look at the list for .сайт, which has 680 strings to block, we discover that only 80 of them are IDNs (beginning with xn--). I assume they’re all, like the gTLD, in Cyrillic script.
I haven’t decoded all of these strings from Punycode and translated them from Russian, but the fact is there’s only 80 of them, which may not be unduly punitive on CORE Association’s launch plan.
At the other end of the spectrum, Donuts will only have to block 13 IDN strings from its .游戏 (Chinese .games) gTLD, and the ASCII strings on its list are mostly numeric or gibberish.
There’s very probably some potentially valuable generic strings on these lists, of course, which could impact the landrush purse, but it’s beyond this monoglot’s expertise to pick them out.
Trademarks
A small number of Latin-script brands appear on all four lists.
Donuts will have to block nokia.游戏, htc.游戏 and ipad.游戏 in its Chinese “.games”, for example. CORE will have to block iphone.сайт and brazzersnetwork.онлайн. DotShabaka Registry will have to block شبكة.redbull.
The impact of this on the registries could be minimal — a few fewer sunrise sales, assuming the brand owner intended to defensively register.
If the blocked brand was a potential launch partner it could be much more annoying and even a launch-delaying factor. It’s not yet clear how registries and brand owners will be able to get these names unblocked.
Bear in mind that registries are not allowed to activate these domains in any sense for any use — they must continue to return NXDOMAIN error responses as they do today.
I’m sure ipad.游戏 (“ipad.games”) could have some value to Apple — and to Donuts, in the unlikely event it managed to persuade Apple to be an anchor tenant — but it’s no longer available.
ICANN will deliver full mitigation plans for each gTLD, which may often include releasing blocked names to their ‘rightful’ owner, but that’s not expected for some months.
Generic terms
A number of generic dictionary terms are getting blocked, which may prove irksome for those registries with long lists. For example, CORE will have to block photo.сайт and forum.сайт.
So far, .онлайн has by far the longest list of ASCII generics to block — stuff like “football”, “drinks”, “poker” and “sex”. Even weirdness like “herpesdating” and “musclefood”.
As it’s an IDN, this might not be too painful, but once ICANN starts publishing lists for Latin gTLDs we might start seeing some serious impact on registries’ ability to sell and market premium domains.
Shurely shome mishtake
There are a few strings on these lists that are just weird, or are likely to prove annoying to registries.
All four of these gTLDs are going to have to block “www” at the second level, for example, which could impact their registry marketing — www.tld is regularly used by TLD registries.
It is going to be really problematic if “www” shows up on the block-lists for dot-brand registries — many applicants say “www.” is likely to be the default landing page for their dot-brand.
The only string that ICANN says it won’t put on any block-list is “nic”, which was once the standard second-level for every TLD’s registry web site but doesn’t really have mass recognition nowadays.
The block-lists also include two-letter strings, most of which correspond to ccTLDs and all of which are already banned by the base Registry Agreement for precisely that reason.
There’s no reason for these two-letter names to be on the lists, but I don’t see their presence causing any major additional heartaches for registries.
So is this good news or what?
As the four block-lists to be released so far are for IDN gTLDs, and because I don’t speak Chinese, Arabic or Russian, it’s a difficult call today to say how painful this is going to be.
There are plenty of reasons to be worried if you’re a new gTLD applicant, certainly.
Premium names will be taken out of play.
You may lose possible anchor tenants.
Your planned registry-use domain names may be banned.
If you’re a dot-brand, you’d better start thinking of alternatives to “www.”.
But the block-lists are expected to be temporary, pending permanent mitigation, and they’re so far quite small in terms of meaningful strings, so on balance I’d say so far it’s not looking too bad.
On the other hand, nothing on the published lists jumps out at me like a massive security risk, so the whole exercise might be completely pointless and futile anyway.

First new gTLD contracts signed

Donuts, an ARI Registry Services subsdiary and CORE this morning became the first new gTLD applicants to sign registry contracts with ICANN.
The ceremonial signing took place live on stage at the opening ceremony of ICANN 47, the week-long public meeting in Durban, South Africa.
ARI CEO Adrian Kinderis signed on behalf of شبكة. applicant International Domain Registry. The string is Arabic for “.web” and transliterates as “.shabaka”. It is 3 in the program’s evaluation queue.
In an ARI press release, Go Daddy CEO Blake Irving confirmed that Go Daddy will carry .shabaka.
Donuts CEO Paul Stahura signed for .游戏, the Chinese-language “.games”, which had prioritization number 40.
It was not immediately clear which contracts Iliya Bazlyankov, chair of CORE’s executive committee, signed. CORE has applied for three internationalized domain name gTLDs with high priority numbers.
(UPDATE: Bazlyankov has been in touch to say: “We signed the .сайт (site) and .онлайн (online) contracts which had numbers 6 and 9 in the priority”.)
Representatives of Go Daddy, MarkMonitor, Momentous, Mailclub and African registrar Kheweul.com also joined ICANN CEO Fadi Chehade on stage to sign the 2013 Registrar Accreditation Agreement.
The event marks the beginning of the contract signing phase of the new gTLD program, an important milestone.
For applicants without outstanding objections, contention or Governmental Advisory Committee advice, signing a contract means only pre-delegation testing and the final transition to delegation remains.

SportAccord picks CORE for .sport gTLD bid

SportAccord, an international association of sporting federations, has picked CORE as its registry services provider for its .sport generic top-level domain application.
The organization, which has International Olympic Committee backing, has also confirmed that it will be applying for .sport as a “community” gTLD.
Community applications can avoid a costly auction in the event that their chosen gTLD string is contested and the applicant can meet a rigorous set of community support criteria.
With over 100 international sporting organizations, covering everything from football to tug of war, comprising its membership, SportAccord’s bid should be good for a few points on the Community Priority Evaluation, but success is by no means assured.
The Lausanne, Switzerland-based organization announced its intention to apply for .sport, issuing an RFP, back in September 2011.
I’m aware of at least two other organizations that have publicly announced potential .sport applications.
CORE currently runs the back-end for the .cat and .museum gTLDs.

AOL loses ICANN accreditation

AOL, one of the first five companies to become an ICANN-accredited registrar, appears to have let its accreditation expire.
The former internet giant is no longer listed on ICANN’s Internic registrar page, and DotAndCo.net’s data shows it lost its .com, .net and .org accreditations on April 27.
It’s hardly surprising. AOL’s profits are falling and it has been reorganizing itself ever since Time Warner returned it to life as an independent company last year.
It’s noteworthy because AOL was one of the first five registrars to challenge Network Solutions’ monopoly, when ICANN introduced competition to the domain name market in 1999.
In April 1999, the company participated in ICANN’s limited registrar “test-bed” experiment, alongside CORE, France Telecom, Melbourne IT and Register.com.
But domain names were never a big deal at the company.
AOL peaked at about 150,000 domains a few years ago and tailed off to a little more than a dozen at the end of 2009. Apparently, the company has decided to let its accreditation simply expire.