It’s no secret that the Internet is largely a place where the English language is used, and that’s to be expected. Air travel is in English, most technology is; virtually everything to do with computers is in English. So, why not all aspects of the Internet? Well, that may be fine for most websites, but as the Internet truly becomes global, domain names have to shift into non-English names. This is what is known as IDN (an Internationalized Domain Name).
Most domain names make use of ASCII characters; what are known as American Standard Code for Information Interchange. Essentially, this is the English alphabet, numbers and symbols. For most languages, this is fine. But, if you are trying to do a domain name in Arabic, Hebrew, Chinese, Hindi or Russian, ASCII does not support their alphabets. To allow for these types of domain names, the IDN system was proposed back in 1996, and finally implemented two years later using what came to be known as IDNA: Internationalizing Domain Names in Applications. This thus allows domain names to contain non-ASCII characters. Yet, there was still a problem: email and web browsers; both of them were still unable to support such characters. It wasn’t until a few years after 2000 – into ’04, 05’ and ’07 that browsers were developed to handle these other languages.
The actual mechanism for the handling of these non-ASCII letters and symbols are complex computer algorithms, but the steps they take are quite straightforward. A domain name is divided into labels, and then each is translated. As an example, look at the website Bucher.ch (with two little dots over the “u”; in German this is what is known as an umlaut). Now, the “.ch” is the country code for Switzerland, and it is straight ASCII; so it does not get changed. But, the German word, as it contains that single non-ASCII character has to be converted. It gets changed to xn-bcher-kva! Not the most appealing domain name, but it works.
A problem with this type of conversion is that it leaves the domain owner wide open to someone “squatting” on their original name. If someone simply registers the domain name Bucher.ch – without the umlaut over the “u”, they can snag the website, and it is all perfectly legal. As a result, if you are looking to set up a non-English domain name, you would be well advised to get the name translated to English and then also register that domain name as well. Also, if you domain name makes use of a word (or words) like the example, you should also register it that form. Even though “Bucher” without the umlaut is not a valid German word, non-German speakers might still type it in. Unfortunately, many Americans are woefully ignorant of other languages, and they know next to nothing of the proper letters and grammar of non-English alphabets.
As recently as 2008, the Internet Corporation for Assigned Names and Numbers (ICANN) was still debating a means of protecting non-English domain names. Each generation of the web browsers and the conversion algorithms improve the domain names, but the same problems still remain.
Sounds like some sort of snack or something, doesn’t it? In fact, what it really refers to is when a company will register a domain name, but not truly want the name; at least not when they initially register it. Instead, they are sort of “testing the waters” on the name. Once they have it registered, they will do a market analysis to see if the name can truly work for their company. The Internet Corporation for Assigned Names and Numbers (ICANN) allows people and companies to register a domain name, and then they have what is known as the AGP (the Add Grace Period), a five-day time period within which they can change their mind about keeping the name. If it turns out that the name does not work for them, they can cancel it, and they do not owe any money.
Now, if this happens on a small scale, it is not a problem. However, some firms will register hundreds (if not thousands) of domain names, and then end up only making use of a handful of them; those that they deem as being viable domain names that hold good potential for making money. The ICANN has received numerous complaints about this practice over the last several years, and some changes to the system have been proposed. In reviewing their records, ICANN found that only two million domain names were actually purchased during April of 2006. Yet, the total number that had initially been registered over that month was around thirty-five million! And, this was not an isolated incident. Less than a year later, in February of 2007, GoDaddy.com reported four million domain names out of 55.1 million actually being registered. Over time, several hundred thousand of those were eventually abandoned.
In January of 2008, the first option was to end the exemption on the transaction costs for the five-day grace period. A year later, no decision had been made, and an alternative was suggested. Rather than just a blanket abolishment of the grace period, it has been proposed that the AGP not apply to any applicant who deletes more than ten percent of their proposed domain names or fifty domains, whichever is higher. Many people consider this a far fairer system; it allows a small firm or a person with a limited budget to try out a domain name, yet prevents large firms from merely scooping up a huge number of names and then not making use of them.
There’s also another practice that’s very similar to domain tasting, known as domain kiting. In this case, a firm will register a domain name and then delete it during the five-day grace period, and then register it again right away; thus they get another five-day grace period. By continuously doing this, a person or company can effectively get a domain name, and yet never paying for it. Domain kiting is illegal, and can result in real trouble for any firm attempting to do it.
In terms of the domain tasting, no official decision has been made by the governing board of the ICANN, but they continue to debate a solution. It remains to be seen as to what they may – or will – do.
This website uses cookies that are necessary to its functioning and required to achieve the purposes illustrated in the privacy policy. By accepting this OR scrolling this page OR continuing to browse, you agree to our Privacy Policy