Latest news of the domain name industry

Recent Posts

Some countries not paying ICANN for their IDNs

Kevin Murphy, December 16, 2010, Domain Registries

ICANN may have to fund some of its IDN ccTLD Fast Track program out of its own pocket, due to at least one country not paying its full fees, judging from information released this week.

ICANN had invoiced applicants for a total of $572,000, but only $106,000 had been received, according to briefing documents (pdf, page 114) presented at the ICANN board’s October 28 meeting.

The organization invoices registries $26,000 for each TLD string it evaluates, but the fees are not mandatory, for political reasons. As of October, it had presumably billed for 22 strings.

At least one country appears to have had its applications processed at a knock-down rate.

Sri Lanka, which was billed $52,000 for two strings, only paid $2,000, and the remaining $50,000 appears to have been written off as “uncollectable”.

Russia, Egypt, South Korea and Tunisia had paid their fees in full.

While the remaining 17 evaluated ccTLDs may not have paid up by October, that’s not to say they have not paid since or will not pay in future.

ICANN also plans to bill IDN ccTLDs 1-3% of annual revenue as a “contribution”, which also won’t be mandatory, but no registry has been live long enough to receive that bill yet.

Bulgarians step up ICANN protest

Kevin Murphy, December 2, 2010, Domain Policy

A domain name registrar association from Bulgaria is laying the groundwork to appeal ICANN’s rejection of the country’s proposed Cyrillic top-level domain.

Uninet has filed a Documentary Information Disclosure Policy request, asking ICANN to publish its reasons for turning down the .бг (.bg) application and the criteria it used.

The domain, which had the backing of the Bulgarian government and people, was rejected in May on the grounds that it is “confusingly similar to an existing TLD”, believed to be Brazil’s .br.

In order to prepare for a future appeal, the Uninet organization wants ICANN to release:

1. The DNS Stability panel working criteria (or parts of it) that were applied to evaluate and subsequently reject the Bulgarian application.
2. The decision of the DNS Stability panel, used to reject the Bulgarian application.

While the ICANN panel’s decision isn’t exactly a state secret (even I have a copy), there seems to be a feeling in Bulgaria that ICANN may not have released all of its reasoning.

The document does not, for example, specify which TLD .бг is confusingly similar to.

It does, however, reveal just how strict ICANN is when it comes to evaluating IDN domains, including a default assumption that any two-letter string is confusing.

We note that two-character strings consisting of Unicode code points in the Latin, Greek, and Cyrillic script blocks are intrinsically confusable with currently defined or potential future country code TLD

We therefore apply a very conservative standard in our assessment of applied-for strings that consist of two Greek, Cyrillic, or Latin characters, including a default presumption of confusability to which exceptions may be made in specific cases.

Uninet said that the Bulgarian government plans to challenge the .бг decision if and when ICANN revises its existing IDN ccTLD Fast Track program to create an appeals process. It wrote:

Many people have criticized the lack of transparency and appeal options in this process, but after the ongoing public comment period we hope that it would be amended by the ICANN Board and the Bulgarian government (as a requester) will have the chance to apply for a re-evaluation of the proposed string.

In the meantime, the Bulgarian government’s IT ministry today started encouraging its citizens to write to ICANN to demand that its application is re-evaluated.

Several already have.

Rejected Bulgarians want ICANN appeal

Kevin Murphy, November 29, 2010, Domain Registries

A handful of Bulgarian internet users have asked ICANN for the right to appeal the rejection of .бг, the proposed Cyrillic country-code top-level domain.

ICANN has received five emails from from the country in the last week, all expressing frustration that .бг (.bg) was turned down with no public explanation and no right to reply.

The string was rejected in May due to what ICANN determined was its confusing visual similarity with Brazil’s ccTLD, .br.

Polls of the Bulgarian people have been unable to find consensus on a suitable alternative, and the government has repeatedly said it would like to apply again or appeal.

Whether to introduce a right of appeal for rejected applicants is one of the topics ICANN is currently soliciting comments on as part of the review of its IDN ccTLD Fast Track program.

Bulgarian freelance developer Stoyan Danev wrote in his comment:

The Bulgarian community has clearly demonstrated that selecting another string is unacceptable and if the proposed one is not approved, Bulgaria will remain WITHOUT an IDN ccTLD. This is really against the ICANN policy of making Internet accessible to everyone.

He questioned whether .бг really is confusable with .br, linking to the Unicode web site, which suggests that б can be confused with 6 but not b, to prove his point.

Another commenter suggested that that the .бг registry could make it a matter of policy to only accept registrations at the second level that include at least one uniquely Cyrillic character.

Will a Russian domain sell for more than Sex.com?

Kevin Murphy, November 25, 2010, Domain Sales

The scandal-hit Russian domain name market may yet produce some of the most expensive domain name sales of all time. Premium .рф generics are already attracting eight-figure bids.

Bids of $10 million have apparently been placed on at least two domains, квартиры.рф and бетон.рф (apartments.rf and concrete.rf), in the controversial quasi-landrush auction managed by RU-Center, the largest Russian registrar.

IDNblog.com is reporting the apartments.rf asking price, and a reader was kind enough to send me a screenshot of the concrete.rf auction.

If these bids are for real, and these auctions were to close, they would immediately occupy the number two and three slots on the league table of all-time biggest-ticket domain sales

Before sex.com sold for $13 million, DNJournal’s top twenty list had fund.com in the top spot, at $9,999,950, followed by porn.com at $9,500,000 and diamond.com at $7,500,000.

The RU-Center auctions may not close, however.

As I reported yesterday, the registrar and five others are being investigated on antitrust grounds by Russian competition authorities, after allegedly registering tens of thousands of domains to themselves.

The auctions are currently frozen and the .рф registry, Coordination Center for ccTLD, has made noises about applying “sanctions” to the registrars that could include de-accreditation.

RU-Center, which confusingly does business at nic.ru, has defended its position in at least two articles here and here (in Russian, naturally).

As far as I can tell, none of these auctions will close until the registrar and the registry resolve their differences and/or the Russian government probe concludes.

However, it’s pretty obvious that the demand for Cyrillic generic IDNs is enormous in Russia, and could easily challenge .com on the big-sale league tables.

Gaming scandal hits Russian domain launch

Kevin Murphy, November 24, 2010, Domain Registries

The launch of Russia’s .РФ country-code top-level domain, widely lauded as a runaway success story, has been tainted by a registrar gaming scandal.

Government antitrust authorities are investigating six registrars over claims that they registered tens of thousands of premium domains in order to auction them to end users, according to local reports.

The registrars in question are thought to have colluded, using each others’ services to register the names, hence the competition probe.

The largest registrar, Regional Network Information Center, aka RU-Center, is alleged to have registered 65,000 domains during the first days of the .РФ launch in order to profit from auctions.

These domains have been frozen pending resolution of the dispute. The registry, Coordination Center for TLD, is thinking about cancelling the registrars’ accreditations.

RU-Center is quoted as saying, laughably, that the premium domains were registered in order to prevent cybersquatting.

In a statement, the registry questions the public good of registering проститутки.рф, which apparently means “prostitute.rf” and is currently asking $190,000 at auction.

The investigation certainly takes the gloss off the launch, which has so far racked up well over 500,000 registered domains and was put forth as case study for internationalized domain names.

Review reveals ccTLD fast-track criticisms

Kevin Murphy, October 25, 2010, Domain Registries

ICANN has launched a review of its internationalized domain name fast-track process, revealing a number of criticisms its country-code domain applicants have apparently had.

The IDN ccTLD Fast Track Process is a way for ccTLD operators to quickly start selling fully non-Latin domains in their own local script.

It’s so far been successfully used to delegate IDN ccTLDs in Arabic, Chinese and Cyrillic scripts, among others.

ICANN now wants to know if it should make any improvements to the process and has opened a 60-day public comment period to solicit suggestions.

Because quite a lot of the Fast Track takes place behind closed doors, ICANN has also offered up a fairly revealing list of possible discussion topics.

It appears that the process has created new pressure points between ICANN and international governments, which are often formally affiliated with their ccTLDs.

For example, some governments dislike the fact that Fast Track requires the applicant to show support for its chosen string from its local community. ICANN reported:

Some [applicants] do not find it necessary to demonstrate community support for the string nor the manager. The reason being that such decisions can be made by government entities, and the need for support undermines the authority of the government in the country or territory.

There also appears to have been a bit of push-back from governments on the issue of “meaningfulness”, where applicants have to show their requested string adequately represents their territory’s name.

ICANN said:

Some requesters have stated that this requirement is not necessary in cases where the strings requested are agreed to by the government and otherwise seem obviously meaningful.

In a concession to governments with sovereignty or financial concerns, ICANN does not charge an up-front fee for handling IDN ccTLD requests under the Fast Track.

Instead, it “recommends” a processing fee of $26,000 per string, which it invoices toward the end of the process, plus an ongoing 1-3% of IDN registration revenue.

So far, it has received $106,000 (covering presumably four strings, accounting for exchange rates), indicating that there are 11 IDN ccTLDs currently in the root that have not yet been paid for.

It will be interesting to see how many ccTLDs ultimately choose to pay up, and how many are happy for ICANN’s costs to be covered by fees paid by gTLD registrants like me and you.

The Fast Track review may also cover the topic of disputes and appeals. Currently, there is no dedicated mechanism by which a ccTLD that has had its requested string rejected can ask for reconsideration.

ICANN asks whether this should be changed.

Earlier this year, Bulgaria had its request for .бг (.bg) declined on the grounds that it looks too much like Brazil’s Latin ccTLD, .br and said it planned to appeal.

The ICANN public comment period, with the full list of suggested discussion topics, can be found here.

Iran’s Arabic domain choice approved

Kevin Murphy, October 16, 2010, Domain Registries

Iran’s choice of Arabic-script top-level domain has passed the string approval stage of ICANN’s internationalized domain name process, making a delegation likely before long.

The manager of Iran’s existing Latin-script ccTLD, .ir, applied for ایران and ايران, which mean “Iran” in Persian. The two look identical to me, so I’m assuming they just use different Unicode code points.

In Punycode, the two strings are .xn--mgba3a4f16a and .xn--mgba3a4fra. Both have been given the stamp of approval, meaning Iran will now have to apply to IANA for delegation.

According to ICANN, there are currently 18 IDN ccTLD strings approved and awaiting delegation, belonging to Iran, India, Saudi Arabia, Qatar, Singapore, Syria and Taiwan.

Some of these countries, such as Saudi Arabia and Taiwan, already have IDNs live in the DNS root, but also have multiple backup variants that have been approved but not yet delegated.

So far, of the 33 strings that have been applied for, only two have been rejected. One of those was Bulgaria’s .бг, which was considered too confusingly similar to Brazil’s .br.

Will the internet get two new ccTLDs (and lose one)?

Kevin Murphy, October 12, 2010, Domain Registries

One country dropped off the map on Sunday, and two new countries were created. So does this mean we’re going to get two new country-code top-level domains?

The islands of Curacao and St. Maarten have reportedly become autonomous countries, after the dissolution of the Netherlands Antilles, a collection of former Dutch colonies off north-east coast of Venezuela.

The reorganization sees a number of other islands join the Netherlands as municipalities, while Curacao and St. Maarten become countries in the own right, albeit still tied politically tied to the motherland.

It seems quite possible that these two islands will now get their own ccTLDs, for two reasons.

First, both states are now reportedly as autonomous as fellow former Dutch Antilles territory Aruba, if not more so. Aruba acquired this status in 1986 and had .aw delegated to it by IANA in 1996.

Second, St Maarten shares a landmass with St Martin, a former French colony. The French northern side of the island is already entitled to its own ccTLD, .mf, although the domain has never been delegated.

ICANN/IANA does not make the call on what is and isn’t considered a nation for ccTLD purposes. Rather, it defers to the International Standards Organization, and a list of strings called ISO 3166-2.

The ISO 3166 Maintenance Agency in turn defers to the UN’s Statistics Division and its “Countries or areas, codes and abbreviations” list, which can be found here.

How long a new ccTLD delegation takes can vary wildly.

Montenegro, for example, declared its independence on June 3, 2006. It was added to the ISO 3166 list on September 26 that year, applied for a ccTLD on December 24, and received its delegation of .me following an ICANN board vote on September 11, 2007.

Finland’s Aland Islands got .ax less than six months after applying in 2006. North Korea, by contrast, received .kp on the same day as Montenegro got .me, but had first applied in 2004.

IANA treats the deletion of a ccTLD much more cautiously, due to the fact that some TLDs could have many second-level registrations already.

The removal of the former Yugoslavian domain, .yu, was subject to a three-year transition process under the supervision of the new .rs registry.

The Dutch Antilles has its own ccTLD, .an, which is in use and delegated to University of The Netherlands Antilles, based in Curacao.

Will we see a gradual phasing-out of .an, in favor of two new ccTLDs?

Arab League asks ICANN for recognition

Kevin Murphy, October 1, 2010, Domain Policy

The League of Arab States has called on ICANN to formally recognize the Arab region.

UPDATED: Read this correction.

.SO Registry copies .co launch policies

Kevin Murphy, September 20, 2010, Domain Registries

Somalia’s .SO Registry, which hopes to mimic a little of the success of .co when it starts accepting registrations in November, has adopted virtually identical launch policies.

The registry’s policy document (pdf), which appeared on its web site last week, does in fact appear to copy large chunks of text wholesale from .CO Internet’s equivalent paper (pdf).

(UPDATE: I’ve reason to believe this is because both documents share an author/editor)

For this reason, you can pretty much expect the same policies regarding the sunrise, landrush and general availability phases of the launch, which kicks off November 1.

It also means that .so domain names will be subject to the UDRP. The registry has evidently partnered with WIPO to administer these proceedings.

There are some differences between .co and .so, however.

Notably, .SO Registry has added a policy of allowing sunrise registrations for trademark typos, provided that the typo under another TLD has been won at UDRP or in court.

This basically appears to open the doors for any company that has won a .com domain in a UDRP case to register the equivalent .so, no matter how lunatic the UDRP decision was.

This is how the document describes the exception to the trademarks-only rule:

the Domain Name must be identical to a domain name which has been recovered by the Applicant or its authorized licensee in the context of a court, UDRP or other alternative dispute resolution procedure relating to that domain name in another top-level domain.

It’s followed by a comment, one of several apparently made by one of the document’s editors, that probably shouldn’t have been published on a public web site:

Comment Bart: we need to look at the allocation model here (rather hypothetical, but you never know): will they also go into auction if there are two applicants for the same domain name: one having the identical mark, and the other having the variant?)

Other differences include the fact that, unlike their Columbian counterparts, Somalians do not appear to get any special privileges, such as grandfathering or a priority sunrise phase.

There also does not to be a provision for a Specially Protected Marks list like the one .CO Internet used.

The registry’s policies will be governed by the laws of Japan, rather than Somalia (which, let’s face it, doesn’t have much in the way of a functional legal infrastructure).

.SO’s back-end is being handled by GMO Registry, the Japanese company that plans to apply for .shop and is working with Canon on its proposed .canon application.

I’ve previously reported on the roll-out time-line and pricing for the .so domain, here.