"There can be a Joe & Sons hardware company in Bangor, Maine, and a Joe & Sons fish restaurant in San Francisco.
But there can only be one joeandsons.com."

Directory of Joe and Sons* registrations

In this example, only the link with a colored background would require a browser extension or mobile app with multiplexing functionality to work in native fashion.

- - -

More realistic examples - multiplexed Johnson registrations:

In the directory list below, the first four links lead to real addresses and work with a standard browser - we have employed redirecting for *1 thru *3.

The Johnson sites *4 through *8 are fictitious - the list was created only for demonstration and does not represent real companies.

Note the johnson.com domain, created in 1997 but parked for many years, blocks all other potential users of that common name under the .com TLD.  Other 'real' johnson registrations - .biz, .net, .org, .info, and .us have also been parked for many years.

Since users have largely rejected ICANN's ngTLDs, we should identify name monopolization as an attack on Internet growth and development.

Developments in AI may return 'content' to its predominant place and relegate domain names to footnotes.

Notes:

1. Any public or third party directory would presumably list domain names in the name*number format, but redirect the names in HTML to the 'native' registration format.  This would allow anyone, with any browser, to select any name from the list to access a site - there would be no inaccessible 'colored background' names.
   The combined URL address line/search field in modern browsers already supports the Multiplexed Name concept.
   Typing names into the browser address line in 'name*number.tld' format would require a browser upgrade, extension, or app.
   If you don't have the necessary software, you can always type the 'native' address format into your browser address line.
   The native format used for this demonstration is 'mlx--[name]--[number]'
2. The address to site: www.johnson*8.com would actually be http://www.mlx--johnson--8.com.
3. An edge application translates this into the 'name*number' format that is shorter and easier to handle.
4. Logically the identity of the original (non-enumerated) registrant should be considered [name]*0.tld.  This means the browser should identify johnson*0.com as johnson.com.
5. Web sites for our two multiplexed JoeAndSons sites are fictitious and used for demonstration purposes only.
6. The table information provided for each fictitious domain name is also fictitious (of course) but demonstrates a reasonable extension of the search (which Johnson) concept.
   A standardized registration format and name repetition make it relatively simple to create name-based directories.
   Current browser address line functions automatically present a 'directory' list, allowing users to search for 'which Johnson' or validate site ownership while browsing.
   'Anonymous' or 'not given' may be legitimate entries since they also give the user pertinent information.
7. Telephone area codes may be preferable to full numbers to help users search for a company or service while protecting the listed company from telephone overload – one reason for publishing a web site to begin with.  In the tables 'St.' means State and 'CC' means Country Code, the country where the business is headquartered.

This is a test

Our solution is not offered as a supported product, we want to demonstrate how the Internet domain name system can evolve to eliminate the current, unnecessary naming restrictions.  Similar functionality could be added to any browser.

Last updated August 1, 2023
W. Kenneth Ryan