London-based software engineer James Williams ventured beyond commonly known domains like g.co and m.me.
However, it's worth noting that not all internet domains abide by the standard TLDs separated by one or more dots.
         
In theory, internet regulators could handle top-level domains (TLDs) like "com" and establish a valid DNS record on the server. If this were the case, users visiting https://net/ would be directed to the relevant web page.

I believe that eliminating dots would undermine the core principle of a decentralized DNS database.
For example, if you owned the domain .net and delegated me vasilisc.net, I could then delegate my own subdomains.
The naming structure from the root node (designated by the dot) to the end machine was formerly simple and elegant, but what would happen to this structure without dots?

Removing dots from internet domains would introduce major disruptions to the existing website architecture, leading potentially to confusion and inconsistencies in the naming of websites. It's fascinating to consider how such changes in the foundation of the internet could have profound effects on its functionality and design.

To maintain compatibility with old internet protocols, one could create a technical name such as smtp.example rather than the standard domain format. Alternatively, one could double up on the domain name for clarity, like example.example, with the first-level domain in use.

This workaround might function smoothly if the internet connection was always reliable. However, currently, users may encounter difficulties such as not understanding where to find a site's signature at the bottom of the page, or forgetting to include "www" in front of a domain. In some cases, this can lead to confusion and frustration, leading to the need for greater digital literacy across the web.

As for me, domain dots are more suitable for perception. Most likely it`s a matter of habit, but even slashes look cumbersome   And the opportunity to short the site name through a dot cannot but rejoice

ICANN's Security and Stability Committee holds the view that "dotless" domains should be prohibited due to their identification as a trusted host on local networks by many programs.
Furthermore, implementing domains without dots will pose challenges for newer browsers, such as Google Chrome, which integrate the search bar into the address bar. This could lead to confusion in situations where a user types "loreal" - it would be unclear whether this referred to the brand or the .GOOGLE domain.

The controversy surrounding "dotless" domains highlights the ongoing debate over how best to manage internet domains in order to ensure that they remain safe and easy to navigate. As technology continues to advance, internet governance bodies like ICANN will need to adapt to new threats and challenges posed by emerging domains and naming conventions.

Regarding your statement about internet regulators handling TLDs like "com" and establishing valid DNS records, this is indeed possible in theory. However, in practice, it's a bit more complicated. The Internet Corporation for Assigned Names and Numbers (ICANN) is the organization responsible for coordinating the management of the DNS Root Zone, which includes the delegation of top-level domains.
ICANN works with various registries and registrars to manage the allocation and registration of domain names across different TLDs. For example, Verisign is the registry operator for the .com and .net TLDs, while other organizations manage different TLDs.

In your hypothetical scenario, if ICANN were to establish a valid DNS record for the "net" TLD on the root servers, users visiting https://net/ would indeed be directed to the relevant web page. However, this would essentially create a new top-level domain, which is a significant undertaking that requires coordination with the global internet community, technical considerations, and adherence to established policies and procedures.

It's worth noting that the "net" TLD is already in use and operated by Verisign, the same registry that manages .com domains. So, while it's theoretically possible for internet regulators to handle TLDs like "com" and establish DNS records, it's a complex process that involves multiple stakeholders and follows established governance frameworks.