Latest news of the domain name industry

Recent Posts

Brexit hell: .eu suspension plan put on hold

Kevin Murphy, October 23, 2019, Domain Registries

EURid’s policy to boot out Brits next week has been put on hold due to the current impasse in Brexit talks.

UK citizens had been told they would lose their .eu domains November 1, the first day the country was scheduled to no longer be a member of the European Union.

But the October 31 exit date appears increasingly unlikely, with the divorce plan agreed to by the EU and UK Prime Minister Boris Johnson still in UK parliamentary limbo.

So EURid posted today:

Following the recent developments in the UK withdrawal scenario, the entire plan outlined below is on hold. We will keep you informed as soon as we receive further instructions from the European Commission.

Under the suspended plan, EURid would have emailed all of its UK and Gibraltar-based registrants tomorrow to inform them that their domains were in jeopardy.

It would have closed down new registrations to Brits on November 1 and given existing registrants a two-month grace period to come into compliance — by transferring their names to addresses in eligible nations — before suspending the names.

A year later, the names would be deleted and returned to the available pool.

EURid said it will provide further guidance when it gets word from the European Commission.

Now you don’t have to live in the EU to register a .eu domain, but there’s a catch

Kevin Murphy, October 21, 2019, Domain Registries

Residents of countries outside the European Union are now able to register .eu domain names.

A new rule that kicked in at the weekend broadened eligibility from only residents of the EU and European Economic Area. Now, residency is irrelevant.

The catch is that you have to still have to be an EU citizen to qualify.

EURid, the .eu registry, said the change opens up the ccTLD to “millions of Europeans living around the world”.

In practice, it could open up the space to basically anyone.

While residency can fairly easily be checked by looking at the mailing address in a Whois record, demonstrating citizenship is a different kettle of fish.

There’s no indication that EURid is asking registrars to collect passport numbers at the point of sale, so it appears to be a post-registration enforcement regime.

.eu is also still open to non-EU citizens who live in the EU or EEA.

.eu had 3.6 million names under management at the last count, having declined by about 200,000 since the Brexit vote three years ago.

Let’s see if the new, liberalized regime has any impact.

Kafka turns in grave as ICANN crowbars “useless” Greek TLD into the root

Kevin Murphy, September 9, 2019, Domain Policy

ICANN has finally approved a version of .eu in Greek script, but it’s already been criticized as “useless”.

Yesterday, ICANN’s board of directors rubber-stamped .ευ, the second internationalized domain name version of the European Union’s .eu, which will be represented in the DNS as .xn--qxa6a.

There’s a lot of history behind .ευ, much of it maddeningly illustrative of ICANN’s Kafkaesque obsession with procedure.

The first amusing thing to point out is that .ευ is technically being approved under ICANN’s IDN ccTLD Fast Track Process, a mere NINE YEARS after EURid first submitted its application.

The “Fast Track” has been used so far to approve 61 IDN ccTLDs. Often, the requested string is merely the name of the country in question, written in one of the local scripts, and the TLD is approved fairly quickly.

But in some cases, especially where the desired string is a two-character code, a string review will find the possibility of confusion with another TLD. This runs the risk of broadening the scope of domain homograph attacks sometimes used in phishing.

That’s what happened to .ευ, along with Bulgaria’s Cyrillic .бг and Greece’s own .ελ, which were rejected on string confusion grounds back in 2010 and 2011.

Under pressure from the Governmental Advisory Committee, ICANN then implemented an Extended Process Similarity Review Panel, essentially an appeals process designed to give unsuccessful Fast Track applicants a second bite at the apple.

That process led to Bulgaria being told that .бг was not too similar to Brazil’s .br, and Greece being told that .ελ did not look too much like .EA, a non-existent ccTLD that may or may not be delegated in future, after all.

But the EU’s .ευ failed at the same time, in 2014. The appeals review panel found that the string was confusable with upper-case .EY and .EV.

Again, these are not ccTLDs, just strings of two characters that have the potential to become ccTLDs in future should a new country or territory emerge and be assigned those codes by the International Standards Organization, a low-probability event.

I reported at the time that .ευ was probably as good as dead. It seemed pretty clear based on the rules at the time that if a string was confusable in uppercase OR lowercase, it would be rejected.

But I was quickly informed by ICANN that I was incorrect, and that ICANN top brass needed to discuss the results.

That seems to have led to ICANN tweaking the rules yet again in order to crowbar .ευ into the root.

In 2015, the board of directors reached out to the GAC, the ccNSO and the Security and Stability Advisory Committee for advice.

They dutifully returned two years later with proposed changes (pdf) that seemed tailor-made for the European Union’s predicament.

A requested IDN ccTLD that caused confusion with other strings in only uppercase, but not lowercase (just like .ευ!!!) could still get delegated, provided it had a comprehensive risk mitigation strategy in place, they recommended.

The recommendation was quickly approved by ICANN, which then sent its implementation guidelines (again, tailor-made for EURid (pdf)) back to the ccNSO/SSAC.

It was not until February this year that the ccNSO/SSAC group got back to ICANN (pdf) to approve of its implementation plan and to say that it has already tested it against EURid’s proposed risk-mitigation plan (pdf).

Basically, the process in 2009 didn’t produce the desired result, so ICANN changed the process. It didn’t produced the desired result again in 2014, so the process was changed again.

But at least Greek-speaking EU citizens are finally going to get a meaningful ccTLD that allows them to express their EUishness in their native script, right?

WRONG!

I recently read with interest and surprise a blog post by domainer-blogger Konstantinos Zournas, in which he referred to .ευ as the “worst domain extension ever”.

Zournas, who is Greek, opened my eyes to the fact that “.ευ” is meaningless in his native tongue. It’s just two Greek letters that visually resemble “EU” in Latin script. It’s confusing by design, but with .eu, a ccTLD that EURid already manages.

While not for a moment doubting Zournas’ familiarity with his own language, I had to confirm this on the EU’s Greek-language web site.

He’s right, the Greek for “European Union” is “Ευρωπαϊκής Ένωσης”, so the sensible two-letter IDN ccTLD would be .ΕΈ (those are Greek characters that look a bit like Latin E).

That would have almost certainly failed the ICANN string similarity process, however, as .ee/EE is the current, extant ccTLD for Estonia.

In short (too late), it seems to have taken ICANN the best part of a decade, and Jesus H Christ knows how many person-hours, to hack its own procedures multiple times in order to force through an application for a TLD that doesn’t mean anything, can’t be confused with anything that currently exists on the internet, and probably won’t be widely used anyway.

Gratz to all involved!

“We’re Irish!” claim Brits as .eu shrinks yet again

Kevin Murphy, August 14, 2019, Domain Registries

British companies are moving their .eu domain names to their Irish branches in an effort to keep them after Brexit, according to the speculations of EURid.

.eu regs in Ireland grew 18% to 47,781 in the second quarter, according to the registry’s Q2 roundup. EURid said:

The high increase in Ireland could be related to the notice about UK withdrawal from the EU and its subsequence to UK .eu domain name holders. Some of the UK domain name holders may have had the chance to transfer the domain names to their branches in other countries of the EU and EEA, e.g. the neighboring Ireland.

Regs in the UK dropped by 13.9% compared to Q1 and by almost half — 46.7% — year over year. There are now 162,287 UK-based .eu domains.

Overall, .eu is still shrinking, partly as a result of this Brexit impact, which has been felt ever since the 2016 referendum.

There were 3,602,573 registered domains at the end of June, down from 3,661,899 at the end of March.

UK-based registrants have been told that they cannot continue to own .eu domains after Brexit, currently slated for October 31. It’s still a possibility that the date could change, or that Brexit may not happen at all.

Confusing matters, EU citizens living in the UK will still be eligible for .eu domains.

All this data, plus a whole lot more, can be read in the EURid Q2 report (pdf).

Revenue dips as Brexit whacks .eu in 2018

Kevin Murphy, April 16, 2019, Domain Registries

.eu saw its registrations sink substantially in 2018, largely due to Brexit, which affected its revenue and profit.

Registry EURid said yesterday that it was managing 3,684,750 .eu domains at the end of the year, down by 130,305 over the year.

It’s .eu’s lowest end-of-year domain count since 2012.

The UK, which voted to leave the EU in 2016 but has yet to follow through, sank from the fourth-largest .eu country to the sixth, now behind less populous countries Poland and Italy.

EURid and the UK government have warned UK-based registrants that they stand to lose their domains after Brexit is actually executed (if it ever is)

As Brits abandoned their .eu names by the tens of thousands, EURid also suspended over 36,000 domains for abuse, which affected its annual total.

The decline hit EURid’s revenue, which was down to €12.7 million, from €13.3 million in 2017. Profit was down from €1.7 million, from €2 million.

The data was published in the registry’s annual report (pdf), published yesterday.