Living in an umlaut country like Germany umlaut domains are sometimes requested.
But: Umlaut domains resp. Internationalized Domain Names (IDN) are problematic.
My main pain points were these:
- Browsers tend to convert the unicode representations to ASCII Compatible Encoding (ACE) with punycode representations for security reasons when copying the url.
So you will get a nice surprise when pasting the url somewhere:
F.e. having https://hürth-blüht.de/ in the browsers address bar will get you https://xn--hrth-blht-q9ag.de/ on copy/paste.
This punycode representation is very unfamiliar to normal users and will keep them from clicking the url because it looks suspicious.
The security issue the browsers have is a so called homograph attacks:
Attackers use similar looking chars for f.e. phishing domains.
For example, the Latin “a” looks a lot like the Cyrillic “а”, so someone could register http://ebаy.com (using Cyrillic “а”)From: https://chromium.googlesource.com/chromium/src/+/master/docs/idn.md
There are also more detailed technical informations on how browsers mitigate those attacks.
- Umlaut domains will not work in ssh since DNS does not support unicodes.
Ssh will require the punycode domain.
The error message is not very helpful on first sight.
ssh user@hürth.dewill say:
Could not resolve hostname h\303\274rth.de: Name or service not known
So use the punycode instead:
- Htaccess Apache Redirects also need punycode
Also on Apache redirects in the .htaccess you will need to use the punycode urls:
A good Article (in german language though) thats describes even more problems like emails, missing legacy system support, SEO or requiring a specific keyboard layout is this: