And why have I not seen loads an loads of .py domains for python? Paraguay is a stable enough country for this purpose. Do they limit domain names to residents?
>Structure: Registrations are at third level beneath second-level labels
[0] https://en.wikipedia.org/wiki/.tk
wget https://iso639-3.sil.org/sites/iso639-3/files/downloads/iso-639-3.tab
grep -xFf <(grep -o ^... iso-639-3.tab) /usr/share/dict/british-english
woo yes, any fun car has the big dry cat, and thy ads are zen too; bye!
A more controversial example is .io for the Chagos Islands which was assigned .io because at various times it has been referred to by its colonialist name the British Indian Ocean Territory. As a place it is full of ugly history including the British forcefully exiling big parts of the native population to help the US build a military base there. The registrar in charge of .io is a British company and the money has almost never benefited the natives or residents of the Chagos Islands. But it became the "hip" tech company TLD because it looks like input/output. There have been multiple awareness campaigns trying to get tech companies to offset this colonial bias in internet infrastructure with donations to useful charities.
> The Chagossians are a mix of African, South Asian, and Malay descent. The French brought some to the Chagos Islands as slaves from Mauritius in 1776. Others arrived as fishermen, farmers, and coconut plantation workers during the 19th century. Under international law, they are the indigenous peoples of the Chagos archipelago, as they are descended from the earliest human settlers of the islands.
Eventually though, the UK government came back again, and forcefully removed these people who weren't natives before, but essentially because of forced re-population by colonizers became the natives. Now they want access to the land they were forcefully migrated to, after being removed from it.
Consider .uk vs .gb
.aq for Antarctica
.ax is part of Finland (.fi)
and so on.
Do we count .su?
It was and is the conventional extension for the Perl programming language, and Perl was most popular for server side (CGI) scripts for some time.
At same time the idea that webserver and user agent should negotiate the most suitable form of content was all the rage. Little of that survived (compression algorithm) but it used to be used for language as well.
Apache had the convention to use the two letter language code as file extension to encode the language. For example it shipped with collection of error messages in many languages, e.g. 404.html.pl.
Since this conflicted with Perl CGI scripts, Perl got .plx for Perl Executable in Apache and it was proposed as the official Perl extension, but did not stick.