Also very important to point out; this same standardisation is missing on the TLD level.
Both for safeguarding internal use, and making a global TLD reserved on the global DNS zones.
You'll find organisations using in production .local .dev (Taken by Google on 2014-11-20, followed by .app in 2015) *.zone (Taken by a LLC on 2014-01-09 ) as internal domains, with potential conflicts with the Internet's DNS resolution.
More importantly .dev [1] and .zone [2] are now valid TLDs, so watch out people!
IMO, a lot of these vanity TLDs are stupid and harmful to the web.
macOS has been using .app as its application extension for decades. Now when you want to search for a specific app on the browser you'll have to be more careful.
The fact that they allowed .dev, which is a fairly common TLD for development, is pretty unbelievable.
I haven't seen any evidence that by allowing companies to register these TLDs we've brought forth some kind of improvement or benefit to users.
There's a recent issue with TLDs that makes me particularly angry. There's ongoing work on this homenet spec. Originally it proposed using .home to route exclusively within the local network. But since .home is already used by a large number of people for private purposes, they changed it to .home.arpa. How the heck have we gotten to the point where we can justify allowing .google as a TLD, but we can't reserve something nice and short for non-companies?
Both for safeguarding internal use, and making a global TLD reserved on the global DNS zones. You'll find organisations using in production .local .dev (Taken by Google on 2014-11-20, followed by .app in 2015) *.zone (Taken by a LLC on 2014-01-09 ) as internal domains, with potential conflicts with the Internet's DNS resolution.
More importantly .dev [1] and .zone [2] are now valid TLDs, so watch out people!
[1] https://www.iana.org/domains/root/db/dev.html
[2] https://www.iana.org/domains/root/db/zone.html