Home / Blogs

IDN and Email: The Harsh Reality

There has been a lot of talk about IDNs here and elsewhere but what does the reality look like for a plain user?

As a test, I randomly choose 28 domains from Alexa's top 100 Sites and tried to create a user account with the email address user@宫殿.com.

The bleak result: only wikipedia.org accepted the IDN - and later on failed to send a verification ping - all other rejected the email address.

IDN domains have standardized since March 2003 (RFC 3490) but as far as I know only one major email provider actually supports IDNs flawlessly…

The tested domains in alphabetic order were: adobe.com, amazon.com, bing.com, blogger.com, cnet.com, cnn.com, conduit.com, craigslist.org, dailymotion.com, deviantart.com, ebay.com, facebook.com, hi5.com, imageshack.us, imdb.com, linkedin.com, live.com, livejournal.com, mediafire.com, megaupload.com, mininova.org, myspace.com, nytimes.com, photobucket.com, twitter.com, wikipedia.org, wordpress.com, youtube.com

By Th. Kühne

Related topics: DNS, Domain Names, Email, Multilinguism, Top-Level Domains

 
   

Don't miss a thing – get the Weekly Wrap delivered to your inbox.

Comments

Good idea, wrong test. IDN & Email James Seng  –  Nov 21, 2009 7:28 AM PDT

Good idea, wrong test. IDN & Email is still under standardization

http://www.ietf.org/dyn/wg/charter/eai-charter.html

Even RFC 5336 is still only experimental, not full standard yet.

It's complicated Patrick Vande Walle  –  Nov 23, 2009 3:10 AM PDT

James,

Actually, it is a bit more complicated than that. the EAI WG works on how a SMTP server and POP3/IMAP4 server deals with Unicode, mostly on the left hand side of the e-mail address.

I understand from the original posting that the test was more on how forms on web sites accept and process IDNized e-mail addresses. I had a similar post, related to the fact that web forms validate e-mail addresses according to software routines, and that many of these have not been updated for some time. Just google for "email address validation javascript" and you will see what I mean. My concern was more related to the acceptance of new TLDs, but obviously this is also true at the second level.

I guess the result of the test would have been quite different if Th. Kühne had submitted user@xn--3bt078a.com, rather than user@宫殿.com.

This will be a major issue and showstopper for the wide adoption of IDN TLDs in my opinion.

Patrick, noted the differences.But I disagree it James Seng  –  Nov 23, 2009 3:16 AM PDT

Patrick, noted the differences.

But I disagree it is a show-stopper.

It is a chicken and egg problem. Do programmers of the website fixed their javascript and backend first before we deploy or do we deploy and let them encounter problem so they can be fixed?

The issue here is most people don't even realize they have a problem until they encounter it. Afterall, IDN isn't that widely used in most of the US sites.

This is also somewhat true for a lot of Asian website but I will bet they will get fixed faster, once people started using IDN.

IDN's and Internet Protocols Keith Teare  –  Nov 23, 2009 2:17 PM PDT

I agree with James Seng that the inability of a piece of software to support an IDN should be a show-stopper. However there is a more complex discussion of the relationship between a DNS address and a protocol.

When RealNames introduced country and language namespaces back in 1999 we explicitly focused on the browser address bar as an input mechanism and nationally specific and language specific namespaces as an modus operadi. Our reasons for doing so were multiple:

1. The browser sends country and language settings in its header, allowing us to be intelligent about user-inputs and our responses.
2. The ability to set namespace level rules was important to us. Korean, Chinese, Japanese etc all want to maintain their own rules governing how to behave in various circumstances.
3. We wanted to focus on the http protocol, which is a big win as a first-to-market feature, even though we knew adoption for various other protocols would be slower.

When we partnered with veriSIgn in 2000-2001 over IDN v1, http was certainly the target and the most asked for protocol.

So...that said, I think that as IDNs are rolled out, being smart about disclosing issues and focusing on what works now versus what will work later is a key take-away from our experience.

Best
Keith Teare

Oops Keith Teare  –  Nov 25, 2009 9:26 AM PDT

Typo above. I mean that I agree with James that the inability of a piece of software to support an IDN should NOT be a show stopper.

To post comments, please login or create an account.

Related Blogs

Related News

Explore Topics

Dig Deeper

Afilias

DNS Security

Sponsored by Afilias
Afilias Mobile & Web Services

Mobile Internet

Sponsored by Afilias Mobile & Web Services
Verisign

Cybersecurity

Sponsored by Verisign

Promoted Posts

Now Is the Time for .eco

.eco launches globally at 16:00 UTC on April 25, 2017, when domains will be available on a first-come, first-serve basis. .eco is for businesses, non-profits and people committed to positive change for the planet. See list of registrars offering .eco more»

Industry Updates – Sponsored Posts

.brands Spotlight: Banking and Finance Industries

Google Buys Business.Site Domain for 'Google My Business'

Radix Announces Global Web Design Contest, F3.space

Global Domain Name Registrations Reach 330.6 Million, 1.3 Million Growth in First Quarter of 2017

.TECH Gets Its Big Hollywood Break

Why the Record Number of Reverse Domain Name Hijacking UDRP Filings in 2016?

UDRP: Better Late than Never - ICA Applauds WIPO for Removing Misguided 'Retroactive Bad Faith'

The Rise and Fall of the UDRP Theory of 'Retroactive Bad Faith'

.PRESS Supports Press Freedom Day for 3rd Consecutive Year

5 Afilias Top Level Domains Now Licensed for Sale in China

Radix Announces Largest New gTLD Sale with Casino.Online

2016 Year in Review: The Trending Keywords in .COM and .NET Domain Registrations

Global Domain Name Registrations Reach 329.3 Million, 2.3 Million Growth in Last Quarter of 2016

A Look at How the New .SPACE TLD Has Performed Over the Past 2 Years

Neustar to be Acquired by Private Investment Group Led by Golden Gate Capital

Startup League Reports from WebSummit, Lisbon

.SPACE Becomes the Choice of the First Ever Space Nation Asgardia

Government Guidance for Email Authentication Has Arrived in USA and UK

ValiMail Raises $12M for Its Email Authentication Service

MarkMonitor Supports Brand Holders' Efforts Regarding .Feedback Registry