It' looks to me like ".home", ".corp", and ".mail" were reserved as "high-risk", and then they refused to approve any of them as gTLDs.
I see an argument that ".dev" should have been considered "high-risk", but it doesn't seem to have been on the list. So this isn't a reason to distrust ICANN when they say they won't be approving ".home", ".corp", and ".mail".
People were using .dev as an internal tld thinking that it'd never become a "real" tld, and they were using that for years. Now though it's a real tld and that opens up many conflicts.
I'd add that .dev was never a safe TLD, it just wasn't available yet.
Using .dev was a pretty foolish thing to do, and ICANN making it available shows how important it is to use proper TLDs for intranets. (That said, a case could be made for .dev being classified as high-risk.)
- HSTS forced by default by Chrome, sorry if you wanted to use http://yourdomain.dev, HSTS forces HTTPS.
- If you have a self signed cert (like Traefik or Caddy for local HTTPS dev), you will get the "not valid cert" browser warning, that one that in any other TLD you know more than your browser and click the "ignore warning and let me use the website", with .dev that button does not exist.
I've never seen .email in the wild or on a LAN. If it was for servers, wouldn't email-server.local, .lan, .home, .corp, etc. make more sense? And using it as a part of an address like me@server.email seems redundant.
Ref: https://www.icann.org/en/board-activities-and-meetings/mater...