# International domain name link is not clickable

**URL:** <https://meta.discourse.org/t/international-domain-name-link-is-not-clickable/63493>\
**Category:** Product Support\
**Created:** [28 במאי,‏ 2017,‏ 8:20am UTC](https://meta.discourse.org/t/international-domain-name-link-is-not-clickable/63493 "2017-05-28T08:20:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [29 במאי,‏ 2017,‏ 12:12am UTC](https://meta.discourse.org/t/international-domain-name-link-is-not-clickable/63493/2 "2017-05-29T00:12:55Z")

</div>

Correct, it isn’t clickable – because it isn’t a URL. The URL is the one with the punycode domain. User agents can, if they choose, make it more palatable to humans by interpreting the punycode into unicode code points, but as everyone keeps finding, that is a process fraught with security peril. Detecting homograph attacks is far from a solved problem, and I’m not entirely sure it _can_ be solved, properly. My entirely personal opinion is that, absent a paying customer requesting this, it’s unlikely that this will make it into core any time soon. It’s also not a great candidate for `pr-welcome`, IMO, because of the ongoing security maintenance burden. Every time someone comes up with a new homograph attack, we’d immediately get another round of H1 reports to pay out on and fix.

---

_[View the full topic](https://meta.discourse.org/t/international-domain-name-link-is-not-clickable/63493)._
