What Does. Com Actually Mean? the Origin Story Most People Get Completely Wrong
By Robert Thorne
Before the mid-1980s, the internet did not have domains. Machines on the ARPANET communicated using numerical internet protocol addresses, mapped manually through a single text file named HOSTS.TXT. Whenever a university or defense research lab added a mainframe to the network, Stanford Research Institute’s Network Information Center updated the central file. Network administrators had to download that master text file via FTP to ensure their local systems knew how to find peer machines.
By 1983, host count expansion rendered the centralized file system unworkable. Names collided constantly, and bandwidth was wasted syncing static name maps. Computer scientist Paul Mockapetris engineered a solution: the hierarchical Domain Name System (DNS). Instead of a flat list, names would read like an inverted tree, moving from general categories on the right to specific host machines on the left.
In October 1984, internet pioneers Jon Postel and Joyce K. Reynolds published RFC 920, titled "Domain Requirements." This technical document laid down the structural foundation for top-level domains (TLDs). It dictated that general administrative domains must group organizations by functional category. At the top of that list sat the abbreviation meant to represent any conventional private business: commercial.
Robert Thorne covers electric vehicle innovations, autonomous driving systems, global mobility trends, and automotive engineering developments.
