@me agreed. I'm disappointed that they've only put one on the list in the end. I think this should be data driven and not language driven. It seems like their argument for not including the full list of candidates was because they could be misinterpreted in different ways. That to me is not the issue. To me the issue is that people use tlds and domains that they do not control and they leak data on the internet. To the root servers and anyone else watching. Adding special case for internal will help but it doesn't solve the problem.

@me 20 years ago smart people already knew they shouldn't hijack existing or possibly existing names, and just use an existing public name as internal suffix for all needs. Even if this `.internal` exists (`home.arpa` was also already sanctified for this use) that will never prevent people to continue using "fake TLD" internally, thinking there will never be a collision... and in a couple of years ICANN opens new round of new gTLDs, and a new `.dev` fiasco can occur again.

@pmevzek .dev kicked my butt too with a few clients - what a mess!

@me More and more TLDs will end up on HSTS preloading list and this is good. At least all Google TLDs will be, waiting for other registries to pick the trend...