Browsers identify transliteration of .com like web adress

[Dimkin]

Hello,
Yesterday noticed that browsers (checked in Chrome and Mozilla) identify transliteration of .com like web adress, and does not send to the search as it was before.
http://picturehosting.com/images/Dimkin/com.png

Maybe somebody have some updates?

[squirrel]

Browsers and some other apps use a regularly updated list of all tlds (http://data.iana.org/TLD/tlds-alpha-by-domain.txt) . Verisign recently signed its ICANN contracts which make .kom and the others "official". Thats probably what happened.

[Rubber Duck]

Sounds more like they may have been delegated, in which case we need the Collision List.

[andre]

Browsers and some other apps use a regularly updated list of all tlds (http://data.iana.org/TLD/tlds-alpha-by-domain.txt) . Verisign recently signed its ICANN contracts which make .kom and the others "official". Thats probably what happened.

ком xn--j1aef and קום xn--9dbq2a are not currently in http://data.iana.org/TLD/tlds-alpha-by-domain.txt

Thanks for the pointer to this file as I did not know about it:)

André 小山 Schappo

[squirrel]

They might be using Mozilla's public suffix list : https://publicsuffix.org/

my understanding however is that the new gTLD community wanted a list of its own, outside of the Mozilla foundation, for Universal TLD Acceptance. I assumed it was the IANA list but maybe I am wrong.