Domain Name with unicode Pitfalls <p>According to yahoo and stackoverflow.com they advise having a static content site that you don't assign cookies to. <a href="http://developer.yahoo.com/performance/rules.html#cookie_free" rel="nofollow">http://developer.yahoo.com/performance/rules.html#cookie_free</a> http://sstatic.net</p> <p>Based of the desire for a static only domain name I though it would be cool to have the domain name made up of unicode characters. From what I understand pitfalls of unicode characters include: difficulty to type and automatic punycode conversation due to the paypal.com innocent. </p> <p>For example if I wanted to link my stylesheet.</p> <pre><code>&lt;link rel=stylesheet href=☺.com/s.css&gt; .... &lt;script src=☺.com/s.js&gt;&lt;/script&gt; </code></pre> <p>Considering I only plan to link to static content, are there are issues or pitfalls?</p> <p>Do all browsers natively support unicode -> punycode conversation? It has been unclear to me if internet explorer less than 7 supports punycode. Also would IE display a notice if you are simply linking to server content in unicode format. </p> <p><strong>Bonus:</strong> Also is there any place to find a list of legal url unicode url characters? Supposedly some characters aren't permitted?! Or would a url containing non permitted characters simply be translated to punycode immediately therefore not effecting my situation?</p>