Re: Unicode domain names issue (Encrypting a "fake" domain name)

A possible solution is one that I envisage has the following practical effects:

That if the name can appear valid in another character set (as xn--e1awd7f.com can be epic.com, and russian characters can be used for latin characters, etc.) that the specific name the certificate is for is detailed on the Browser as exampled in my edited screen shots below. 

Please review this possible approach in clarifying the exact nature of which URL is being certified by a TLS certificate. 

https://www.imageupload.co.uk/images/2017/04/19/certificated_example2.png

https://www.imageupload.co.uk/images/2017/04/19/certificated_example.png

Cheers