Skip to main content
All CollectionsManaging Domains
Why do emoji domains begin with "xn--*" strings?
Why do emoji domains begin with "xn--*" strings?
Namebase avatar
Written by Namebase
Updated over a week ago

The xn--5p9h above is the punycode representation of the 🀝 emoji.

Domain names can only contain a limited set of characters so emoji and foreign character domains are puny encoded β€” when you type an emoji into a browser, it will look up the punycode of that emoji. In other words, the punycode xn--* string is the actual domain name, and not the emoji rendering.

Before purchasing an emoji or unicode domain, we highly recommend you do your own homework on punycodes and unicode homoglyphs.
​
We recommended the following sites to test your punycode/unicode conversion against:
​https://www.punycoder.com/

How Namebase renders Punycode

Invalid Domain Characters
If invalid domain characters are encountered, the Punycode will not be rendered. For example, "xn--c0a" (A) is considered invalid because uppercase characters are not allowed in domain names according to the IDNA2008 standard.
​
​Multiple zero-width-joiners (ZWJ)
Domains with multiple zero-width joiners (ZWJ) will be handled in two ways:

  • Rendered Normally: Some domains will render fine, such as "xn--1uga057cv713cia75dea" (πŸ‘©πŸΌβ€β€β€πŸ‘©πŸ½). Basically the browser decides how to render these.

  • Rendered with Indication: In other cases, the ZWJ will be rendered as "οΏ½", for example, "xn--1uga10057a" (�🧝�). This prevents confusion with similar domains that do not contain a ZWJ, like "xn--nv9h" (🧝).

If you believe we should render a punycode differently please contact our support.

Did this answer your question?