Skip to main content
Resources

Registries

Back to CCT Metrics Reporting page

These metrics are drawn from data sources from IANA root zone data of delegated TLDs, executed Registry Agreements, and registry websites. [Updated Monthly]

2.4 TLDs Using IDN Scripts

The number of Internationalized Domain Name (IDN) top-level domains (TLDs) delegated into the Internet's root zone. [Updated Monthly] [As of: – 1 December, 2017]

Language*** Count
Arabic 12
Chinese 53
German 2
Hebrew 1
Hindi 3
Japanese 11
Korean 3
Persian 1
Russian 8
Thai 1

 

Script Type*** Count
Arabic 13
Cyrillic 8
Devanagari 3
Han 55
Hangul 2
Hebrew 1
Japanese* 2
Katakana 6
Latin Script* 2
Thai 1

*Note: The two German IDNs are counted in the Latin script category due to the inclusion of IDN characters in the string
**(Alias for Han + Hiragana + Katakana)
***Note: Language and script type are defined as those specified by the applicant in questions 14C1 and 14D1 of the new gTLD application, respectively.

Source: gTLD applications
CCT Review Category: Consumer Choice

2.7 Legal Regimes Where New gTLD Registry Operators are Based

The number of legal regimes where new gTLD registry operators are based. The legal regime is determined using the identification of the parties specified in the Registry Agreement. The Registry Agreements can be found here. [Updated Monthly] [As of: – 1 December, 2017]

ISO Code Count of New gTLDs Count of Legacy gTLDs
AE 14
AT 6
AU 32
BE 3
BH 2
BM 5
BR 11
CA 9
CH 41 1
CN 29
CO 1
DE 48
DK 6
ES 13 1
FI 4
FR 32 1
GB 36
GI 17
HK 25 1
IE 21 2
IM 1
IN 15
IQ 1
IT 12
JP 59
KR 5
KW 2
KY 73
LU 22
MX 2
NL 15
NO 2
NZ 1
PH 1
PT 2
QA 1
RU 7
SA 4
SC 1
SE 10
SG 5 11
TH 1
TR 7
TW 3
UK 6
US 576
UY 4 1
VG 1
ZA 4
European Economic Interest Grouping (EEIG) 1
Intergovernmental Organization 1

 

Region Code Count of New gTLDs Count of Legacy gTLDs
AF 7
AP 209 1
AQ 0
EUR 405 6
LAC 17
NA 588 11
IGO 1

Source: gTLD applications
CCT Review Category: Consumer Choice

*This data is categorized using the ICANN Geographic Regions list.
**The ISO codes are based on the ISO 3166-2 standard.

3.1 Quantity of TLDs

The total number of TLDs before and after expansion of the Domain Name System as a result of the New gTLD Program. [Updated Monthly]

Baseline Quantity of all TLDs (includes ccTLDs)* Total Quantity of Delegated TLDs Post-October 2013 [As of: – 1 December, 2017]
306 1527

Source: IANA Root Zone database
CCT Review Category: Competition

3.2 Quantity of gTLDs

The total number of gTLDs under contract with ICANN before and after expansion. [Updated Monthly]

Baseline Quantity of Legacy gTLDs* Total Quantity of Delegated gTLDs Post October 2013 [As of: – 1 December, 2017]
18 1221

Source: ICANN gTLD Delegated Strings List and IANA Root Zone Database
CCT Review Category: Competition

*Note: This metric considers the following as legacy gTLDs: '.com' '.net' '.org' '.aero' '.asia' '.museum' '.xxx' '.pro' '.cat' '.mobi' '.jobs' '.coop' '.name' '.biz' '.info' '.tel' '.travel', '.post'

3.2.a Quantity of gTLDs Removed from the Root Zone

The gTLDs '.doosan,' '.flsmidth,' 'mutuelle,' 'iinet,' 'mtpc,' and 'orientexpress' were removed from the Root Zone as of May 2017. They therefore have been removed from the total number of gTLDs.

3.3 Unique gTLD Registry Operators

The number of unique* gTLD registry operators before and after expansion. [Updated Monthly]

Baseline Quantity of Unique* Registry Operators Total Quantity of Unique* Registry Operators [As of: – 1 December, 2017]
15 775

Source: Registry Agreement
CCT Review Category: Competition

*Note: The term 'Registry Operator' refers to the entity holding the registry contract with ICANN. A registry operator is also responsible for providing registry services, some or all of which may be outsourced. A 'Unique Registry Operator,' however, is considered one that is not already operating a delegated gTLD.

3.4 Unique gTLD Registry Service Providers

The number of unique* gTLD Registry Service Providers before and after expansion. Registry Service Providers (RSPs) were identified based on data in new gTLD applications. [Updated Monthly]

Total Quantity of Unique* gTLD Registry Service Providers [As of: – 1 December, 2017]
49

Source: gTLD Applications
CCT Review Category: Competition

*Note: The term 'Registry Service Provider' refers to an entity providing certain technical operations for a Registry Operator. This term is not meant to include an Emergency Back End Registry Operator (EBERO). A 'Unique Registry Service Provider,' however, is considered one that is not already providing registry services to a delegated gTLD.

3.6 New gTLDs Operated by 'New Entrants'

The relative share of new gTLDs operated by 'new entrants;' Registry Operators* that did not operate a gTLD prior to the expansion of the Domain Name System as a result of the New gTLD Program. [Updated Monthly] [As of: – 1 December, 2017]

Share Operated by 'New Entrants' Share Operated by 'Legacy*' Registry Operators
77.7% (1189 gTLDs) 2.5% (38 gTLDs)

Source: gTLD Applications
CCT Review Category: Competition

*Note: This metric considers the following as 'legacy' gTLDs: '.com' '.net' '.org' '.aero' '.asia' '.museum' '.xxx' '.pro' '.cat' '.mobi' '.jobs' '.coop' '.name' '.biz' '.info' '.tel' '.travel'
**Note: The term 'Registry Operator' refers to the entity holding the registry contract with ICANN. A registry operator is also responsible for providing registry services, some or all of which may be outsourced. A 'Unique Registry Operator', however, is considered one that is not already operating a delegated gTLD.

7.1 Registry Privacy Policies

The number of gTLD registries with privacy policies that are clearly and easily accessible by end users. The baseline worksheet in the attached file compares the availability of these policies on legacy gTLD registries' webpages. The second worksheet provides a more detailed comparison of various policies for the top 30 new gTLD registries by registration numbers, as of Q1, 2016. This policy comparison was compiled at the request of the CCT Review Team's Competition and Consumer Choice sub team.

Metrics 7.1-7.3 Excel File [XLSX, 36 KB] [Baseline Data]

CCT Review Category: Consumer Trust

7.2 Registry Allocation Policies

The number of gTLD registries with allocation policies that are clearly and easily accessible by end users. The baseline worksheet in the attached file compares the availability of these policies on legacy gTLD registries' webpages. The second worksheet provides a more detailed comparison of various policies for the top 30 new gTLD registries by registration numbers, as of Q1, 2016. This policy comparison was compiled at the request of the CCT Review Team's Competition and Consumer Choice sub team.

Metrics 7.1-7.3 Excel File [XLSX, 36 KB] [Baseline Data]

CCT Review Category: Consumer Trust

7.3 Registry Codes of Conduct

The number of registries that disclose end-user information regarding their codes of conduct for sub-domain owners/operators. The baseline worksheet in the attached file compares the availability of these policies on legacy gTLD registries' webpages. The second worksheet provides a more detailed comparison of various policies for the top 30 new gTLD registries by registration numbers, as of Q1, 2016. This policy comparison was compiled at the request of the CCT Review Team's Competition and Consumer Choice sub team.

Metrics 7.1-7.3 Excel File [XLSX, 36 KB] [Baseline Data]

CCT Review Category: Consumer Trust

Back to CCT Metrics Reporting page

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."