Back

16 Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string

gTLDFull Legal NameE-mail suffixDetail
.artDadotart, Inc.deviantart.comView
Q16 - Operational or Rendering Considerations with Regard to the gTLD String

The .ART Registry (and CORE Internet Council of Registrars as its technical provider) ensured that there are no known operational or rendering problems concerning the applied-for gTLD string ʺARTʺ.

Since the gTLD string ʺARTʺ is an ASCII-only string, it is safe to assume that, just like with existing ASCII-only TLD strings like .com, .net or .de, no operational or rendering problems may be expected. In particular, the name consists only of ASCII characters that are already used for existing top level domains; all the characters in the name are even used in the leftmost position of existing TLD labels. In order to confirm this, CORE Internet Council of Registrars conducted a thorough research regarding whether operational or rendering issues occurred for any existing ASCII-only top level domain in the past. The results of this research confirmed the assumption.

Since the registry does not support right-to-left scripts on the second level, bi-directional issues (like the ones described at http:⁄⁄stupid.domain.name⁄node⁄683) will not occur.

Moreover, the gTLD string exclusively uses characters from a single alphabet, does not contain digits or hyphens, and it contains characters that are not subject to homograph issues, which means there is no potential for confusion with regard to the rendering of other TLD strings.

Finally, CORE Internet Council of Registrars set up a testing environment for the .ART TLD using the CORE Registration System, including an EPP SRS, Whois and DNS servers, in order to conduct a series of tests involving typical use cases (like web site operation and e-mail messaging) for a TLD. The tests revealed no operational or rendering issues with any popular software (web browsers, e-mail clients) or operating systems.
gTLDFull Legal NameE-mail suffixDetail
.corsicaCollectivité Territoriale de Corsegmail.comView
Background checks were carried out by the technical operator for the .corsica TLD to ensure that there are no known operational or rendering problems concerning the applied-for ʺ.corsicaʺ gTLD string.

It was found that since the .corsica gTLD string is an ASCII-only string, it is safe to assume that, just as with existing ASCII-only TLD strings like .com, .net or .de, no operational or rendering problems are to be expected. The name consists entirely of ASCII characters that are already used for existing top-level domains. Moreover, all the characters in the name are used in the leftmost position of existing TLD labels. In order to confirm our assumption that there will be no operational or rendering problems, thorough research was conducted regarding whether such issues have occurred for any existing ASCII-only to- level domains in the past. They have not.

This means that bi-directional issues (like the ones described at http:⁄⁄stupid.domain.name⁄node⁄683) will not occur, also in view of the fact that the .corsica TLD string does not contain digits (whose behaviour in bi-directional contexts can lead to rendering issues).

As the registry supports right-to-left scripts at the second level, the respective IDN tables were carefully crafted according to IDNA2008 standards to ensure that no rendering issues occur left or right of the dot (ʺ.ʺ) character separating the top and second domain name labels (which are the only labels under the registryʹs control).

Moreover, the .corsica gTLD string is comprised of characters from a single alphabet, does not contain digits or hyphens, and it contains characters that are not subject to homograph issues, i.e. there is no potential for confusion with regard to the rendering of other TLD strings.

Finally, a testing environment for the .corsica TLD was set up using the target Registration System, including an EPP SRS, Whois and DNS servers, in order to conduct a series of tests involving typical use cases (like web site operation and e-mail messaging) for a TLD. The tests revealed no operational or rendering issues with any popular software (web browsers, e-mail clients) or operating systems.