We already provide access to the interpreted and beautified variants of a Domain name.
It would be nice to also include the following variants:
- Writing this issue quick and so I'll use imprecise technical language. Consider how the set of characters allowed in normalized ENS names is much larger than the set of characters allowed in DNS names. Therefore consider the case of a normalized ENS name that includes emojis for example. I believe such names need to be converted into Punycode form to be accessible within DNS. For a quick example of this idea, see: https://adraffy.github.io/ens-normalize.js/test/resolver.html#%F0%9F%85%B0%F0%9F%85%B1%F0%9F%85%B2%F0%9F%85%B3%F0%9F%85%B4%F0%9F%85%B5%F0%9F%85%B6%F0%9F%85%B7%F0%9F%85%B8%F0%9F%85%B9%F0%9F%85%BA%F0%9F%85%BB%F0%9F%85%BC%F0%9F%85%BD%F0%9F%85%BE%F0%9F%85%BF%F0%9F%86%80%F0%9F%86%81%F0%9F%86%82%F0%9F%86%83%F0%9F%86%84%F0%9F%86%85%F0%9F%86%86%F0%9F%86%87%F0%9F%86%88%F0%9F%86%89.eth
- A DNS-accessible name for accessing whatever content might be hosted at the domain via HTTP. For example, the domain
🅰🅱🅲🅳🅴🅵🅶🅷🅸🅹🅺🅻🅼🅽🅾🅿🆀🆁🆂🆃🆄🆅🆆🆇🆈🆉.eth is accessible via HTTP via https://xn--037hcdefghijklmnopqrstuvwxyz0a.eth.limo/ through the eth.limo gateway. While an ENS name that's not a subname of .eth or .reverse which are TLDs exclusive to ENS can return its name directly as its DNS-accessible name.
We already provide access to the
interpretedandbeautifiedvariants of a Domain name.It would be nice to also include the following variants:
🅰🅱🅲🅳🅴🅵🅶🅷🅸🅹🅺🅻🅼🅽🅾🅿🆀🆁🆂🆃🆄🆅🆆🆇🆈🆉.ethis accessible via HTTP via https://xn--037hcdefghijklmnopqrstuvwxyz0a.eth.limo/ through the eth.limo gateway. While an ENS name that's not a subname of .eth or .reverse which are TLDs exclusive to ENS can return its name directly as its DNS-accessible name.