`.home`, `.corp` and `.mail` are on ICANN’s “high risk” list so won’t ever be gTLDs. So I use those gTLDs when setting up internal networks.
Ref: https://www.icann.org/en/board-activities-and-meetings/mater...
Ref: https://www.icann.org/en/board-activities-and-meetings/mater...
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".
Google did extreme evil with .dev, with the blessing of ICANN.
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.)
- 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.
[1] https://gtldresult.icann.org/applicationstatus/viewstatus
[2] https://gtldresult.icann.org/applicationstatus/applicationde...