Jan 31, 2024 12:10:00

ICANN tentatively adopts '.internal' as private TLD for internal network, soliciting public comments

ICANN has decided to temporarily adopt the name '.internal' as the TLD for its internal network. Public comments are being solicited until March 21, 2024, and if there are no particular problems, the proposal will be officially adopted.

Proposed Top-Level Domain String for Private Use
https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01-2024

(PDF)Identification of a top-level domain for private use
https://itp.cdn.icann.org/en/files/root-system/identification-tld-private-use-24-01-2024-en.pdf

In September 2020, the Security and Stability Advisory Committee (SSAC ) (PDF) recommended reserving TLDs for private use on internal networks , and ICANN selected appropriate TLDs from among 35 candidates. We were in the process of choosing a name. In the end, two candidates remained, ``.internal'' and ``.private,'' but there were concerns that ``.private'' might give people a false sense of security, so ``.internal'' was chosen. has been confirmed.

However, at the time of writing the article, the adoption of '.internal' is provisional, and public comments are being accepted. They will review all comments submitted during the public comment period until March 21, 2024, and reconsider whether there are any problems. If there are no problems, '.internal' will be officially adopted as is.

If ``.internal'' is officially adopted, it will be confirmed that the TLD ``.internal'' will not be used in the global space in the future, and at the same time, confusingly similar TLDs may be prohibited.

At the time of writing this article, when accessing internal network devices such as routers in the home, it is necessary to directly enter an IP address such as '192.168.xx', but as '.internal' becomes more popular, it will become more readable by humans. It is expected that it will be accessible in an easy-to-use domain format.