Company wants to fix error in one of its new top level domain applications.

Verisign has responded to Domain Name Wire’s inquiry regarding an error in its application for a Hebrew internationalized domain name (IDN) for a transliteration of .com:

Verisign is aware of the administrative error that resulted in the inclusion of a variant character in the Verisign Sàrl application for the Hebrew transliteration of .com and is working with ICANN to address the error.

ICANN is currently working on guidelines for when and how a new TLD applicant can change its final application.

I’m currently working to fix a UTF8 problem on Domain Name Wire. When that’s finished I’ll post thoughts from the IDN community about VeriSign’s selection of .com and .net transliterations.

Advertisers no longer have to show ASCII URLs in their ads.

A couple weeks ago I missed an announcement from Google AdWords that it now supports internationalized domain names (IDN) for display and destination URLs on Google ads.

This means advertisers will no longer have to show a non-ASCII ad followed by an ASCII domain name.

AdWords clients can enter unicode characters for the URLs and Google will verify that it works correctly in both unicode and punycode.

The display URL will only show up only in cases where the language matches that of the user’s Google interface, otherwise it will render in punycode.

(Hat tip: Patrick C)

India gets seven IDN ccTLDS and more good news for IDN domain name supporters.

One thing I learned on my trip to India earlier this month is that there are a lot of local languages.

This week ICANN approved delegation of seven (yes, seven) internationalized county code domain names to National Internet Exchange of India. The delegated ccTLDs include भारत (“Bharat”), encoded as “xn--h2brj9c”; بھارت “Bharat”), encoded as “xn--mgbbh1a71e”; భారత్ (“Bharat”), encoded as “xn--fpcrj9c3d”; ભારત (“Bharat”), encoded as “xn--gecrj9c”; ਭਾਰਤ (“Bharat”), encoded as “xn--s9brj9c”; இந்தியா (“Bharat”), encoded as “xn--xkc2dl3a5ee0h”; and ভারত (“Bharat”), encoded as “xn--45brj9c.

Also getting the nod this week: a Korean ccTLD for Republic of Korea, Chinese and Tamil ccTLDs for Singapore, and an Arabic ccTLD for the Syrian Arab Republic.

In other good news for IDN supporters, it looks like new gTLDs may actually move forward at March’s ICANN meeting, opening up the door for internationalized “equivalents” of existing top level domain names.

New York City event will educate about Internationalized Domain Names (IDNs).

Few topics have received greater attention this year than IDNs. So it’s fitting that the first ever “IDN Event and Auction” will take place October 30, 2010 at the Haru Restaurant in New York City at 7 pm. The event is organized by IDNTools and will be sponsored by Register.com, Moniker and SnapNames.

The goal of the event is to educate domain registrants about IDNs, their value proposition, how to register them, the value of developing IDNs, the importance of connecting with local audiences, and we will also hold an IDN auction.

Although the agenda is not yet set, speakers include DotAsia CEO Edmon Chung, Elliot Silver, and Associated Cities Executive Director Patrick Carleton.

Early bird registration through October 1 is $99. After October 1 registration prices increase to $275.

by Aaron Krawitz, Gary Males & Patrick Carleton

[This article explores the latest with IDN ccTLDs such as .рф and .日本. Aaron Krawitz of IDNBlog and Gary Males of IDNDemystified co-own IDNDroplist, IDNTools and IDNNewsletter. Patrick Carleton is Executive Director of Associated Cities. -Andrew]

Change is afoot in the world of IDN ccTLDs.

Just a few days ago, we learned that the registry, JPRS, was the only one to apply to manage the .日本 IDN ccTLD (meaning “.Japan” in Japanese). JPRS is the current .JP registry and has previously spoke out in favor of aliasing or unlocking .JP in an IDN equivalent. As such, the practical implication of the above application is that we will likely soon see owners of IDN.JP domains owning IDN.日本 names as well.

Hiro Hotta the Director of Corporate Planning at JPRS previously stated: “In my opinion, the registrant of IDN.jp should automatically have the right to register IDN.日本 . . . [i]t is relatively easy for [the] .JP registry (JPRS) to implement this aliasing.”

Meanwhile, the release of .рф IDN ccTLD (meaning “.RF” in Russian) is on track. The sunrise period is currently open to trademark holders, with a number of .рф sites already having gone live, and landrush is to follow this fall.

Awareness

There are several material implications of the IDN ccTLD progress, the first of which is greater awareness of IDNs in general. As IDNs are in the news on a daily basis, investors, developers and end-users are realizing that IDN.com domains exist now, IDN.IDN-ccTLD names will exist soon and these foreign language domains are great platforms to use in order to engage users in their native languages.

Extension Question

Though the publicity of IDN ccTLDs are having a positive effect on the awareness and value of IDN.com names, such new ccTLDs also pose a competitive threat. In the world of IDNs, to many it seems like buying an IDN.com is the intuitive choice as .COM is already a global brand. However, in many markets, new IDN ccTLDs will be available long before an internationalized IDN.com-in-IDN domain will be available, and such IDN ccTLDs will at times have the advantage of being the first IDN.IDN in a certain region.

Consequently, it is anyone’s guess as to whether the new IDN ccTLDs, ASCII .COM, or the future IDN .COM alias becomes the extension of choice for IDNs in a given country and the prudent investor should buy both.

Opportunities Overlooked

Lastly, amidst the blockbuster releases of IDN ccTLDs for Japan and Russia, smaller countries tend to get overlooked even though they too are releasing IDN ccTLDs. IDN opportunities will surely abound in these smaller markets as well.