24hr IDNwiki Report – What Do the User Stats Look Like?

by Tina Dam on October 16, 2007

The IDNwikis were released at 4.10am PDT 15 October 2007 (UTC – 7hours). While the primary reason for the IDNwikis is to evaluate fully localized domain names in different applications, I thought it might be interesting with some user stats and related information from here.

There was immediate traffic on all wikis, with the area with English content having the lowest traffic.

Discussions also started very quickly, being lead by the Arabic, Hindi, and Russian IDNwikis.

When reading the statistics and making comparisons below please take into consideration the time of day that the wikis were released as in some regions it was already late in the day. It is also necessary to keep in mind that there are many local language communities across the world that participated as well. With this in mind it is hard to compare statistics after such a short time. I will submit the same set of statistics when a full week have passed for easier comparison.

Page Requests and Users:

For the remaining time of the launch day (PDT time) there was approximately 16.000 unique users visiting the sites – with a total of 45.692 page requests served. That is, an average of about 3 pages per user.

Divided among the 11 IDN wikis this looks as follows:

Script Language %-share
Cyrillic Russian 52.69
IDN Main Gateway   19.06
Arabic Arabic 8.14
Greek Greek 3.31
Arabic Persian 3.60
Kanji, Hiragana, Katakana Japanese 3.16
Devanagari Hindi 2.62
Hangul Korean 2.06
Tamil Tamil 1.90
Chinese Chinese 1.73
Hebrew Yiddish 1.73
Total   100.00

Referral URLs:

There have been a lot of news articles online the past few weeks about the IDNwikis and evaluation forums being underway, and it is nice to see that visitors came directly from some of these articles. There is a long list of the referral URLs, but here is the top list of where the users came from:



Browser vendors:

Several browser developers have provided information on the IDNwikis about how to use IDNs and how to for example set your local user configuration to display one or more languages/scripts that you intend to use. In addition the IDNwikis also holds general and basic information about IDNs. We are currently talking to the IDNwiki moderators about translating this material, but combined this should help users get the best experience of IDNs as possible as well as provide them with a good platform for testing things out.

The top 10 browser vendors used by the wiki visitors as of Tuesday, 16 October 2007 10:00PDT, are divided as follows:

page requests

4879 MSIE
4671 Firefox
2290 Opera
1849 Netscape (compatible)
498 Baiduspider+(+http:
282 Safari
249 Mozilla
86 Konqueror
27 Camino
24 Apache

Taking a closer look at the individual IDNwikis the division looks as follows:
Arabic/Arabic Script IDNwiki:

page requests

385 MSIE
190 Firefox
156 Netscape (compatible)
56 Opera
12 Safari

Greek/Greek IDN wiki:

page requests

112 MSIE
109 Firefox
43 Opera
35 Netscape (compatible)
12 Safari

IDNwiki gateway:

page requests

1662 MSIE
1632 Firefox
270 Netscape (compatible)
149 Safari
98 Opera

Hindi/Devanagari Script IDNwiki:

page requests

73 Firefox
55 Netscape (compatible)
32 Opera
6 Mozilla

Japanese/ Kanji, Hiragana, Katakana Script IDNwiki:

page requests

111 MSIE
69 Firefox
34 Opera
16 Netscape (compatible)
8 WordPress

Korean/ Hangul IDNwiki:

page requests

155 MSIE
44 Firefox
21 Netscape (compatible)
19 Opera
3 Konqueror

Persian/Arabic Script IDNwiki:

page requests

223 MSIE
140 Firefox
108 Netscape (compatible)
23 Opera
6 Mozilla

Russian/Cyrillic Script IDNwiki:

page requests

2032 Firefox
1809 Opera
1431 MSIE
113 Mozilla
91 Netscape (compatible)

Tamil/Tamil Script IDNwiki:

page requests

79 Firefox
63 Opera
56 Netscape (compatible)
11 Mozilla

Chinese/ Traditional and Simplified Script IDNwiki:

page requests

961 Netscape (compatible)
569 MSIE
488 Baiduspider+(+http:
246 Firefox
86 Opera

Yiddish/Hebrew Script IDNwiki:

page requests

961 Netscape (compatible)
569 MSIE
488 Baiduspider+(+http:
246 Firefox
86 Opera


life_here 10.18.07 at 9:34 pm

Please check Chinese / Yiddish stats, could not be exactly the same

reyrtdudri 10.19.07 at 11:02 pm

Tina Dam 10.21.07 at 10:25 pm

You are off course correct. The yiddish were in fact about double.

The 1-weeks stats will be correct. Sorry about the mistake and inconvenience.


Anonymous 10.23.07 at 3:44 am

Simple Chinese and traditional chinese example.test should link to the same web page. according to rfc3743, Simple Chinese and traditional chinese example.test are equal, and should belong to the same idn label package and should be owned by the same registrar.

Steve DelBianco 11.01.07 at 9:17 am

It’s great that ICANN is encouraging users to test native character domain names in their browsers, email software, and other applications. That’s essential to get IDN TLDs into users hands.

At the same time, ICANN should be cautioning new users about casually downloading plug-ins, patches or new applications to test IDNs. Let’s remind them to deal only with trusted websites and scan for viruses and malware. (let’s do that in multiple langauges and scripts, of course)

Otherwise, our “next billion” users could accidentally host the “next billion” bots capable of generating spam, phishing fraud, and denial-of-service attacks.

Kieren McCarthy 11.10.07 at 5:35 pm

It’s a good point Steve.

Will ponder how best to direct people.


Tina Dam 11.11.07 at 7:32 pm

Hi Steve, Kieren,

it is a good idea, however it is hard for ICANN to be able to say: this is a good plug-in and this is a bad one. We simply cannot check all applications and all plug-ins as there are too many of them around. In addition to the volume this is a grey-zone area for ICANN’s mandate.

However, if you have specific experience using some of these then you can start by adding the information on the wiki.

If you are merely talking about general warnings for users the this should not be related to IDNs only. Kieren, lets talk about this the week after next when im back in the office…there are many different channels in the ICANN community leading to end-users that I am sure would be available to help out further on this.


Comments on this entry are closed.