Home / News

Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand

The arrival IE 7, Firefox 2.0 and other browsers that offer built-in support for IDNs could open the floodgates to IDN sales and usage. ...VeriSign says more than 600,000 IDNs have been registered in .com and .net, and that these names are "experiencing double-digit growth in new registrations and high renewal rates," according to its Domain Name Industry Brief published in August. 

Read full story: Digit Magazine

By CircleID Reporter – CircleID's internal staff reporting on news tips and developing stories. Do you have information the professional Internet community should be aware of? Contact us. Visit Page

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Co-designer of the TCP/IP Protocols & the Architecture of the Internet


Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Jothan Frakes  –  Oct 31, 2006 11:32 am PDT

From statistical registration data presented at the Domain Roundtable in April this year, there were direct corrolations between IDN registration increases and each incremental release of IE7.  Firefox has had support since its early versions.

The final release of IE7 with its IDN support and OS integrations are a huge win for the global internet community from a perspective of offering a wider base of core native language character sets in domain names.

IDN is the new hot registration driver.


Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By The Famous Brett Watson  –  Oct 31, 2006 6:47 pm PDT

I wonder what portion of overall IDN registrations will be attributable to phishing and typo-squatting in the long run. I don't mean to imply anything negative about IDN in saying this, but I suspect that phishers in particular will take a very active interest in it.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Edward Lewis  –  Nov 01, 2006 7:14 am PDT

With change and innovation comes risk.  Criminals are not risk adverse but a lot of legitimate businesses are.  If in the early phases of IDN there are a lot of registrations for suspected phishing activity this shouldn't discourage IDN.  As the technology gets used with the legitimate early adopters showing the way, I'm sure suspected legitimate use will rise.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Jothan Frakes  –  Nov 06, 2006 2:00 pm PDT

One thing that I saw in demonstration of the IDN capabilities inherent to IE7 was that the IDNA layer of translation identifies mixed scripts and displays the domain in the location bar as the punicode version versus the native characters when this occurs.  This is progress, at least, as it helps reduce the amount of homonym phishing sites being mistaken for actual sites by trusting the location bar's listed domain.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Jaeyoun Kim  –  Nov 16, 2006 10:19 pm PDT

MS Korea launched a Korean-language version of IE 7.0 on the 15th November.

Not only NIDA(.kr Registry) but also many domain squatters were very excited about the launch of Korean IE 7.0 in that it provides IDN support.

Although several browsers already support IDNs, 99% of Korean Internet users have been using only MS IE so that Korean IDNs was not popular for Korean Internet users.

Many Korean Internet users actually prefer Korean Keyword service (provide by Netpia and DigitalNames) to Korean IDNs due to its simplicity and convenience.

I hoped that many ordinary Internet users will have an interest in Korean IE 7.0 and its IDN support, yet I realize that most Internet users are still only interested in other features such as tabbed browsing.

Now, Korean Keyword service does not work in IE 7.0. If we type Korean Keyword directly into the address bar, IE 7.0 shows the search results of the Korean Keyword from the user-configured search engine.

Netpia is the one who is really upset about this and feels that it would threaten the existence of its Keyword service. Netpia is now taking legal steps against MS.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Suresh Ramasubramanian  –  Nov 17, 2006 12:36 am PDT

My heart bleeds for netpia, I'm sure.  Unless netpia had some kind of contract with Microsoft where Microsoft committed itself to supporting keywords, I don't see on what grounds they can sue Microsoft for bringing out a browser version that doesn't support keywords.

Banking the future of an entire business on a nonstandard feature that can at any time become redundant with future versions of a browser doesnt sound like a very brilliant move to me.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Keynes  –  Nov 17, 2006 11:47 am PDT

I think we can take Sureh's comments even further: until we have full ICANN-sanctioned IDN extensions, these "intermediate" IDNs are really only speculative placeholders; the movement to full IDNs will change the shape of the game.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Suresh Ramasubramanian  –  Nov 18, 2006 7:57 pm PDT

I just remembered something about "netpia" and "legal action against microsoft".  They've been talking about this since at least 2005.

There was this post on circleid from "Jason S", who posted some really vague sounding "concerns" about IDNs, praised keywords as a really usable alternative, suggested that keyword providers like Netpia et al would take legal action against Microsoft if they implemented IDNs on IE .. this article was dated May 3 2005


Quoting "Jason S" -

Microsoft had sore experience of security instability problem on their IE. Also, they could fall into yet another law suit from multilingual keyword providers like Netpia, 3721 and JWord if they implement the IDN service on IE. Well, time will tell what the next move of Microsoft is.

Only thing Jason didn't bother to mention was that he worked for Kangsik Cheon, Netpia's COO, and the WGIG member who according to James Seng was responsible for this WGIG paper on multilingualization / IDNs - http://wgig.org/docs/WP-Multilingualization.pdf

James Seng has some commentary on the WP-Multilingualization paper - http://james.seng.sg/archives/2005/02/04/wgig_papers.html

James Seng writes on his blog :

I already taken a quick look at the Multilingualization paper and I am shock! shock shock shock! What a piece of bias BS! Written from a very Korean-centric position where in fact, Korean keyword is an exemption experience then the norm.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By David Wrixon  –  Nov 19, 2006 5:31 am PDT

@Bradley E.

Place holders they may be, but you can be 99.9% sure that if you get the ASCII ccTLD you will also end up with the IDN version. In Dot CN you already get both in the price!

With Dot Com, it has to be admitted that there is a slight increase in risk. If the NS solution is proved viable and implemented for gTLD, then there is a theoretical risk of the establishment of alternative registeries. If the DNAME solution is adopted for gTLD which is much more likely then there isn't even that theoretical risk is much diminished.

The big problem for those who think Dot Com won't migrate to IDN.IDN is that Countries and Governments don't and never have had a monopoly on Languages. It would be very unwise for the US Government to accept that position as they might have to hand over everything to the British! It always amazes me how much fuss Americans make over Trade Marks and then their systems allow the registration of marks like Pilsner!

If you are going place languages under the local control of Governments then the rules for one have to apply for all. If you can even begin to explain how that is going to work in the case of Urdu, then I will concede the argument here and now.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By Keynes  –  Nov 20, 2006 5:28 am PDT

@D. Wrixon:

Certainly there is no level of certainty in terms of the future of IDN.IDN: I concede that we may see a natural migration for .com holders, but I also maintain that there is still a moderately high level of risk that this will not happen - either way, the uncertainty increases the risk in investing in "first gen" IDNs.  In terms of the public policy with respect to language, the relationship of the Department of Commerce and ICANN is increasingly migrating into the sphere of international law, and granting localized IDN rights to ccTLDs doesn't necessarily require absolute authority to national registries.  Contrariwise, such a system could remain under the auspices of ICANN (the merits of which I won't discuss at this point), while moving toward a more formal IDN.IDN system (which is inevitable, if not necessary.) The issue is not absolute control over a given language in the IDN structure, but, rather, a more flexible internationalized IDN system.  Given your example — Urdu is an Indo-European language, which is officially the national language of Pakistan, and also is one of India's 23 official languages.  There are a number of options which ICANN could utilize in this case, including a trans-national IDN, variants of ccTLD IDNs or a subdomain system (G-d help us in that case.) In short, I'm not making an absolute claim regarding holders of .com IDNs, bur rather making a relative claim about the levels of risk inherent in such investments — they are real, and should be fully incorporated into our understanding of the nascent IDN market.

Re: Release of IE7, Firefox 2.0 Will Drive Significant IDN Demand By David Wrixon  –  Nov 20, 2006 7:37 am PDT

OK, I accept that but it has to be measured against the risk of missing the boat. Even in the after market these domains are still very cheap, but the final solution certainly won't be.

Add Your Comments

 To post your comments, please login or create an account.



New TLDs

Sponsored byAfilias


Sponsored byWhoisXML API

Domain Names

Sponsored byVerisign


Sponsored byThreat Intelligence Platform

DNS Security

Sponsored byAfilias


Sponsored byVerisign

Brand Protection

Sponsored byAppdetex