Skip to main content
Resources

Two-Character Letter/Letter Label Comments and Mitigation Measures

As of 13 December 2016, this page is no longer active. Please visit here for more information.

For comments submitted before 6 October 2015, view the archive of comments received.

Download Excel
TLD  Two
Characters  		Comments from GovernmentLast
updated  		RO Mitigation PlanRO NameBRAND TLD
jcpruView Comments
2016-08-15
2016-08-15Yes
quebecruView Comments
2016-08-15
2016-08-15No
totalruView Comments
2016-08-15
2016-08-15Yes
wtcruView Comments
2016-08-15
2016-08-15Yes
babyinView Comments
2016-08-05
2016-08-05No
bloginView Comments
2016-08-05
2016-08-05No
caminView Comments
2016-08-05
2016-08-05No
doctorinView Comments
2016-08-05
2016-08-05No
fujixeroxinView Comments
2016-08-05
2016-08-05Yes
gamesinView Comments
2016-08-05
2016-08-05No
gdninView Comments
2016-08-05
2016-08-05No
ikanoinView Comments
2016-08-05
2016-08-05Yes
jcpinView Comments
2016-08-05
2016-08-05Yes
jnjinView Comments
2016-08-05
2016-08-05Yes
quebecinView Comments
2016-08-05
2016-08-05No
shopinView Comments
2016-08-05
2016-08-05No
totalinView Comments
2016-08-05
2016-08-05Yes
wtcinView Comments
2016-08-05
2016-08-05Yes
acotwView Comments
2016-01-04
2016-08-03View Mitigation

aco Mitigation

By ACO Severin Ahlmann GmbH & Co. KG

.ACO mitigation measures apply across all two character labels

.ACO TLD is a closed Brand new gTLD operated by ACO Severin Ahlmann GmbH & Co. KG

Protections
ACO Severin Ahlmann GmbH & Co. KG for the .ACO TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that ACO Severin Ahlmann GmbH & Co. KG will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .ACO is identical to a qualifying registered trademark;

2. .ACO is not a Generic String, as this is defined in Specification 11;

3. .ACO TLD has developed and implemented a closed registration policy for .ACO that requires that all domain names in the .ACO TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;

4. As required under the Registry Agreement, the .ACO TLD is clearly publishing this registration policy;

5. .ACO TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .ACO TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ACO TLD is a proprietary space in which all second-level domains in the TLD are being operated by ACO Severin Ahlmann GmbH & Co. KG, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this ACO Severin Ahlmann GmbH & Co. KG confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-19

ACO Severin Ahlmann GmbH & Co. KGYes
auditwView Comments
2016-01-04
2016-08-03View Mitigation

audi Mitigation

By Audi Aktiengesellschaft

.audi is a closed Brand TLD for the sole and exclusive use of Audi Aktiengesellschaft.

Protections
Audi Aktiengesellschaft (Registry Operator) for the .audi TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.audi is identical to a qualifying registered trademark;
.audi is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .audi that requires that all domain names in the .audi TLD be registered only by Audi Aktiengesellschaft, its Affiliates, and its Trademark Licensees.

As required under the Registry Agreement, the Registry Operator published this registration policy on its website.

Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .audi TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

By this submission Audi Aktiengesellschaft confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Audi AktiengesellschaftYes
audiotwView Comments
2016-01-04
2016-08-03No
blackfridaytwView Comments
2016-01-04
2016-08-03No
bugattitwView Comments
2016-01-04
2016-08-03View Mitigation

bugatti Mitigation

By Bugatti International SA

.bugatti is a closed Brand TLD for the sole and exclusive use of Bugatti International SA.

Protections
Bugatti International SA (Registry Operator) for the .bugatti TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.bugatti is identical to a qualifying registered trademark;
.bugatti is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .bugatti that requires that all domain names in the .bugatti TLD be registered only by Bugatti International SA, its Affiliates, and its Trademark Licensees.

As required under the Registry Agreement, the Registry Operator published this registration policy on its website.

Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .bugatti TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

By this submission Bugatti International SA confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Bugatti International SAYes
christmastwView Comments
2016-01-04
2016-08-03No
clicktwView Comments
2016-01-04
2016-08-03No
csctwView Comments
2016-01-04
2016-08-03View Mitigation

csc Mitigation

By Alliance-One Services, Inc.

.CSC gTLD Confusion Avoidance Plan
Alliance-One Services, Inc., a wholly-owned subsidiary of Computer Sciences Corporation, and the Registry Operator for the .CSC gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Alliance-One Services, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .CSC is identical to a qualifying registered trademark;
2. .CSC is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. Alliance-One Services, Inc. has developed and will implement a closed registration policy for .CSC that requires that all domain names in the .CSC gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Alliance-One Services, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .CSC will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement.
Compliance with Specification 13 prohibits the .CSC gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .CSC gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Alliance-One Services, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.
With this submission, Alliance-One Services, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-26

Alliance-One Services, Inc.Yes
diettwView Comments
2016-01-04
2016-08-03No
flowerstwView Comments
2016-01-04
2016-08-03No
foxtwView Comments
2016-01-04
2016-08-03View Mitigation

fox Mitigation

By FOX Registry, LLC

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.FOX TLD is a closed Brand new gTLD operated by FOX Registry, LLC

Protections:

FOX Registry, LLC for the .FOX TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that FOX Registry, LLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .FOX is identical to a qualifying registered trademark;
2. .FOX is not a Generic String, as this is defined in Specification 11;
3. .FOX TLD has developed and will implement a closed registration policy for .FOX that requires that all domain names in the .FOX TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .FOX TLD will clearly publish this registration policy;
5. .FOX TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .FOX TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .FOX TLD is a proprietary space in which all second-level domains in the TLD are being operated by FOX Registry, LLC, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this FOX Registry, LLC confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

FOX Registry, LLCYes
gametwView Comments
2016-01-04
2016-08-03No
geatwView Comments
2016-01-04
2016-08-03View Mitigation

gea Mitigation

By GEA Group Aktiengesellschaft

.GEA Mitigation

.GEA mitigation measures apply across all two character labels
By GEA Group Aktiengesellschaft

.GEA TLD is a closed Brand new gTLD operated by GEA Group Aktiengesellschaft.

Protections
GEA Group Aktiengesellschaft for the .GEA TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that GEA Group Aktiengesellschaft will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .GEA is identical to a qualifying registered trademark;

2. .GEA is not a Generic String, as this is defined in Specification 11;

3. .GEA TLD has developed and implement a closed registration policy for .GEA that requires that all domain names in the .GEA TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;

4. As required under the Registry Agreement, the .GEA TLD is clearly publishing this registration policy;

5. .GEA TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .GEA TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .GEA TLD is a proprietary space in which all second-level domains in the TLD are being operated by GEA Group Aktiengesellschaft, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this GEA Group Aktiengesellschaft confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.






2016-04-19

GEA Group AktiengesellschaftYes
gifttwView Comments
2016-01-04
2016-08-03No
graingertwView Comments
2016-01-04
2016-08-03View Mitigation

grainger Mitigation

By Grainger Registry Services, LLC

.GRAINGER gTLD Confusion Avoidance Plan

Grainger Registry Services, LLC, the Registry Operator for the .GRAINGER gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Grainger Registry Services, LLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .GRAINGER is identical to a qualifying registered trademark;
2. .GRAINGER is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. Grainger Registry Services, LLC has developed and will implement a closed registration policy for .GRAINGER that requires that all domain names in the .GRAINGER gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Grainger Registry Services, LLC submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .GRAINGER will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement.

Compliance with Specification 13 prohibits the .GRAINGER gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .GRAINGER gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Grainger Registry Services, LLC, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

With this submission, Grainger Registry Services, LLC confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Grainger Registry Services, LLCYes
guitarstwView Comments
2016-01-04
2016-08-03No
helptwView Comments
2016-01-04
2016-08-03No
hiphoptwView Comments
2016-01-04
2016-08-03No
hostingtwView Comments
2016-01-04
2016-08-03No
juegostwView Comments
2016-01-04
2016-08-03No
lamborghinitwView Comments
2016-01-04
2016-08-03View Mitigation

lamborghini Mitigation

By Automobili Lamborghini S.p.A.

.lamborghini is a closed Brand TLD for the sole and exclusive use of Automobili Lamborghini S.p.A.

Protections
Automobili Lamborghini S.p.A. (Registry Operator) for the .lamborghini TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.lamborghini is identical to a qualifying registered trademark;
.lamborghini is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .lamborghini that requires that all domain names in the .lamborghini TLD be registered only by Automobili Lamborghini S.p.A., its Affiliates, and its Trademark Licensees.

As required under the Registry Agreement, the Registry Operator published this registration policy on its website.

Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .lamborghini TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

By this submission Automobili Lamborghini S.p.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Automobili Lamborghini S.p.A.Yes
lanxesstwView Comments
2016-01-04
2016-08-03View Mitigation

lanxess Mitigation

By LANXESS Corporation

Provide a brief explanation of the TLD:
LANXESS Corporation has applied for .LANXESS to run a closed .brand environment.

Protections
LANXESS Corporation for the .LANXESS TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the LANXESS Corporation will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .LANXESS is identical to a qualifying registered trademark;
2. .LANXESS is not a Generic String, as this is defined in Specification 11;
3. .LANXESS TLD has developed and will implement a closed registration policy for .LANXESS that requires that all domain names in the .LANXESS TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .LANXESS TLD will clearly publish this registration policy;
5. .LANXESS TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .LANXESS TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .LANXESS TLD is a proprietary space in which all second-level domains in the TLD are being operated by LANXESS Corporation, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter LANXESS Corporation confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

LANXESS CorporationYes
lefraktwView Comments
2016-01-04
2016-08-03View Mitigation

lefrak Mitigation

By LeFrak Organization, Inc.

Provide a brief explanation of the TLD: [Registry Operator] has applied for .[TLD] to run a closed .brand environment.
Protections
[REGISTRY OPERATOR] for the .[TLD] TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the [Registry Operator] will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .[TLD] is identical to a qualifying registered trademark;
2. .[TLD] is not a Generic String, as this is defined in Specification 11;
3. .[TLD] TLD has developed and will implement a closed registration policy for .[TLD] that requires that all domain names in the .[TLD] TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .[TLD] TLD will clearly publish this registration policy;
5. .[TLD] TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .[TLD] TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .[TLD] TLD is a proprietary space in which all second-level domains in the TLD are being operated by [REGISTRY OPERATOR], its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator.
By this [LETTER] [REGISTRY OPERATOR] confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-19

LeFrak Organization, Inc.Yes
linktwView Comments
2016-01-04
2016-08-03No
loltwView Comments
2016-01-04
2016-08-03No
matteltwView Comments
2016-01-04
2016-08-03View Mitigation

mattel Mitigation

By Mattel Sites, Inc.

.MATTEL gTLD Confusion Avoidance Plan

Mattel Sites, Inc., a wholly-owned subsidiary of Mattel, Inc. and the Registry Operator for the .MATTEL gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Mattel Sites, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .MATTEL is identical to a qualifying registered trademark;
2. .MATTEL is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. Mattel Sites, Inc. has developed and will implement a closed registration policy for .MATTEL that requires that all domain names in the .MATTEL gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Mattel Sites, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .MATTEL will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement.

Compliance with Specification 13 prohibits the .MATTEL gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .MATTEL gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Mattel Sites, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

With this submission, Mattel Sites, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


View Documents
2016-04-19

Mattel Sites, Inc.Yes
momtwView Comments
2016-01-04
2016-08-03No
moscowtwView Comments
2016-01-04
2016-08-03No
mtrtwView Comments
2016-01-04
2016-08-03View Mitigation

mtr Mitigation

By MTR CORPORATION LIMITED

To minimize the possibility of confusion for lables, ai, bh, bm, ci, cn, eg, gb, il, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw and uk, we have reserved those names at the second level of .mtr. In other words, no one can register and activate those domain names at the second level unless we received consent from ICANN and the relevant government body.

For label(s) pertaining to confusion but ICANN allows us to offer for registration and activation at the second level (e.g. in), it will not be used in a way causing confusion. In fact, .mtr is a brand TLD, the registrant of .mtr will not be people in the general public. The use of it can be easily controlled. In case of receiving comment from the relevant government, we can react at a quick and direct manner.


2016-03-24

MTR CORPORATION LIMITEDYes
phototwView Comments
2016-01-04
2016-08-03No
picstwView Comments
2016-01-04
2016-08-03No
propertytwView Comments
2016-01-04
2016-08-03No
redumbrellatwView Comments
2016-01-04
2016-08-03No
rmittwView Comments
2016-01-04
2016-08-03View Mitigation

rmit Mitigation

By Royal Melbourne Institute of Technology

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Royal Melbourne Institute of Technology has applied for .RMIT to run a closed .brand environment.
Protections
Royal Melbourne Institute of Technology for the .RMIT TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Royal Melbourne Institute of Technology will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .RMIT is identical to a qualifying registered trademark;
2. .RMIT is not a Generic String, as this is defined in Specification 11;
3. .RMIT has developed and will implement a closed registration policy for .RMIT that requires that all domain names in the .RMIT TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .RMIT TLD will clearly publish this registration policy;
5. .RMIT TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .RMIT TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .RMIT TLD is a proprietary space in which all second-level domains in the TLD are being operated by Royal Melbourne Institute of Technology - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, Royal Melbourne Institute of Technology confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-22

Royal Melbourne Institute of TechnologyYes
safetytwView Comments
2016-01-04
2016-08-03View Mitigation

safety Mitigation

By Safety Registry Services, LLC

Safety Registry Services, LLC, the Registry Operator for the .SAFETY TLD, is operating .SAFETY as a restricted TLD where only credible and verified individuals or organizations are eligible to register and use domain names in .SAFETY. As such, .SAFETY will clearly only include registrants and domains related to the safety community.

To address the confusion concerns cited by government representatives regarding the use of second-level domains in the .SAFETY gTLD, Safety Registry Services, LLC will implement a restricted registration policy for .SAFETY that mitigates the potential confusion. To this end, Safety Registry Services, LLC commits to the following:

1. Developing and implementing a restricted registration policy for .SAFETY that adheres to the values of the safety community;
2. Clearly publishing this registration policy on Registry Operator’s homepage for .SAFETY;
3. Including this registration policy in Registry Operator’s Registry-Registrar Agreement with all contracted registrars for the .SAFETY TLD; and
4. Enforcing of this registration policy and ensuring continued compliance with the TLD’s credibility standards.

This registration and usage policy would prevent national governments and their representatives from registering domains in the .SAFETY TLD, because the only possible registrants allowed under the registration policy will be members of the .SAFETY community. Safety Registry Services, LLC will clearly designate to users that .SAFETY is a restricted space in which all second-level domains were registered by and for members of the safety community.


2016-04-25

Safety Registry Services, LLCNo
sexytwView Comments
2016-01-04
2016-08-03No
suckstwView Comments
2016-01-04
2016-08-03View Mitigation

sucks Mitigation

By Vox Populi Registry Ltd.

Proposed Measure to Avoid Confusion—Phased Allocation

dotSucks is designed to help consumers find their voices and allow companies to find the value in criticism. Each dotSucks domain has the potential to become an essential part of every organization’s customer relationship management program.

Phased Allocation - Upon the release of the letter/letter combination corresponding to the following objected to country codes (ai, bh, bm, ci, cn, eg, gb, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk), Registry Operator will provide an exclusive thirty (30) day period in which registration of such letter/letter combination will be made only available to the applicable country code manager as listed at: http://www.iana.org/domains/root/db/

This type of phased allocation has been previously approved by ICANN as an acceptable and complete measure to avoid confusion with applicable country codes.

For example, .TRAVEL included the following in its RSEP on 18 May 2009:
“In seeking to minimize any confusion with county codes, Tralliance will initially place all two-letter country code names, as listed in the ISO 31-66 list, in the RFP allocation round and will seek expressions of interest from all country code managers for their respective two-character names. Tralliance will allocate two letter country codes to any corresponding country code managers (as listed at: http://www.iana.org/domains/root/db/) that desire to register their name, with no restriction other that payment of normal registration fees and a commitment to use the registered name.”

The Board approved the change via a resolution on 5 August 2010: https://www.icann.org/resources/board- material/resolutions-2010-08-05-en.

At that time, the amendment to the .TRAVEL Registry Agreement permitted release of 2 characters through a Phased Allocation Program https://www.icann.org/resources/unthemed-pages/travel-appendix-7-2010-08-23-en).

.TRAVEL has subsequently entered into a new gTLD Registry Agreement with ICANN and carried over the previous Board- approved release of two-characters through its phased allocation program. Current .TRAVEL Specification 5 language:
“All single-character and two-character labels that were previously reserved by the Registry Operator prior to the Effective Date of this Registry Agreement may be allocated through ICANN-accredited registrars according to a phased allocation program (“Phased Allocation Program”). The domain names included within the scope of the Phased Allocation Program shall be limited to a single and two-character labels. Registry Operator reserves the right to not allocate all single and two-character labels. Pursuant to the Phased Allocation Program, Registry Operator may elect to allocate labels by applying one or more of the following processes: 1) request for proposals and allocation based on evaluation criteria; 2) auction; or 3) first come, first serve registration.”

Similar Phased Allocation Programs have been approved by ICANN as an implementation of measures to avoid confusion with corresponding country codes in .BIZ, .INFO, .ORG, and .JOBS.


2016-04-22

Vox Populi Registry Ltd.No
tattootwView Comments
2016-01-04
2016-08-03No
travelerstwView Comments
2016-01-04
2016-08-03Yes
travelersinsurancetwView Comments
2016-01-04
2016-08-03No
trvtwView Comments
2016-01-04
2016-08-03No
volkswagentwView Comments
2016-01-04
2016-08-03View Mitigation

volkswagen Mitigation

By Volkswagen Group of America Inc.

.volkswagen is a closed Brand TLD for the sole and exclusive use of Volkswagen Group of America Inc.

Protections
Volkswagen Group of America Inc. (Registry Operator) for the .volkswagen TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.volkswagen is identical to a qualifying registered trademark;
.volkswagen is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .volkswagen that requires that all domain names in the .volkswagen TLD be registered only by Volkswagen Group of America Inc., its Affiliates, and its Trademark Licensees.

As required under the Registry Agreement, the Registry Operator published this registration policy on its website.

Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .volkswagen TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

By this submission Volkswagen Group of America Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Volkswagen Group of America Inc.Yes
warmantwView Comments
2016-01-04
2016-08-03View Mitigation

warman Mitigation

By Weir Group IP Limited

Provide a brief explanation of the TLD:
Weir Group IP Limited has applied for .WARMAN to run a closed .brand environment.

Protections
Weir Group IP Limited for the .WARMAN TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Weir Group IP Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .WARMAN is identical to a qualifying registered trademark;
2. .WARMAN is not a Generic String, as this is defined in Specification 11;
3. .WARMAN TLD has developed and will implement a closed registration policy for .WARMAN that requires that all domain names in the .WARMAN TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .WARMAN TLD will clearly publish this registration policy;
5. .WARMAN TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .WARMAN TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WARMAN TLD is a proprietary space in which all second-level domains in the TLD are being operated by Weir Group IP Limited, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Weir Group IP Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Weir Group IP LimitedYes
weirtwView Comments
2016-01-04
2016-08-03View Mitigation

weir Mitigation

By Weir Group IP Limited

Provide a brief explanation of the TLD:
Weir Group IP Limited has applied for .WEIR to run a closed .brand environment.

Protections
Weir Group IP Limited for the .WEIR TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Weir Group IP Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .WEIR is identical to a qualifying registered trademark;
2. .WEIR is not a Generic String, as this is defined in Specification 11;
3. .WEIR TLD has developed and will implement a closed registration policy for .WEIR that requires that all domain names in the .WEIR TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .WEIR TLD will clearly publish this registration policy;
5. .WEIR TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .WEIR TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WEIR TLD is a proprietary space in which all second-level domains in the TLD are being operated by Weir Group IP Limited, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Weir Group IP Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Weir Group IP LimitedYes
wowtwView Comments
2016-01-04
2016-08-03View Mitigation

wow Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .WOW TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. ARSI further proposes the following measures to avoid confusion with the corresponding country codes.

ARSI will commit to:
1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code:
a. the use in the .WOW TLD of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

ARSI’s Acceptable Use Policy for the .WOW TLD will require registrants of a domain name in the .WOW TLD to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above.



2016-04-25

Amazon Registry Services, Inc.No
xn--3oq18vl8pn36atwView Comments
2016-01-04
2016-08-03View Mitigation

xn--3oq18vl8pn36a Mitigation

By Volkswagen (China) Investment Co., Ltd.

.大众汽车 is a closed Brand TLD for the sole and exclusive use of Volkswagen (China) Investment Co., Ltd.

Protections
Volkswagen (China) Investment Co., Ltd. (Registry Operator) for the .大众汽车 TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

.大众汽车 is identical to a qualifying registered trademark;
.大众汽车 is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and will implement a closed registration policy for .大众汽车 that requires that all domain names in the .大众汽车 TLD be registered only by Volkswagen (China) Investment Co., Ltd., its Affiliates, and its Trademark Licensees.

As required under the Registry Agreement, the Registry Operator will publish this registration policy on its website.

Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .大众汽车 TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators.

By this submission Volkswagen (China) Investment Co., Ltd. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

Volkswagen (China) Investment Co., Ltd.Yes
xn--80adxhkstwView Comments
2016-01-04
2016-08-03No
xn--gk3at1e twView Comments
2016-01-04
2016-08-03View Mitigation

xn--gk3at1e  Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .xn--gk3at1e TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. ARSI further proposes the following measures to avoid confusion with the corresponding country codes.

ARSI will commit to:
1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code:
a. the use in the .xn--gk3at1e TLD of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

ARSI’s Acceptable Use Policy for the .xn--gk3at1e TLD will require registrants of a domain name in the .xn--gk3at1e TLD to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above.


2016-04-25

Amazon Registry Services, Inc.No
bmstwView Comments
2016-02-16
2016-08-03View Mitigation

bms Mitigation

By Bristol Myers Squibb

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: BRISTOL-MYERS SQUIBB COMPANY has applied for .BMS to run a closed .brand environment.
Protections
BRISTOL-MYERS SQUIBB COMPANY, for the .BMS TLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that BRISTOL-MYERS SQUIBB COMPANY will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .BMS is identical to a qualifying registered trademark;
2. .BMS is not a Generic String, as this is defined in Specification 11;
3. .BMS has developed and will implement a closed registration policy for .BMS that requires that all domain names in the .BMS TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .BMS TLD will clearly publish this registration policy;
5. .BMS TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .BMS TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .BMS TLD is a proprietary space in which all second-level domains in the TLD are being operated by BRISTOL-MYERS SQUIBB COMPANY. - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, BRISTOL-MYERS SQUIBB COMPANY confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-20

Bristol Myers SquibbYes
freetwView Comments
2016-02-16
2016-08-03No
insurancetwView Comments
2016-02-16
2016-08-03View Mitigation

insurance Mitigation

By fTLD Registry Services, LLC

Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes.


View Documents
2016-04-20

fTLD Registry Services, LLCNo
junipertwView Comments
2016-02-16
2016-08-03Yes
latrobetwView Comments
2016-02-16
2016-08-03View Mitigation

latrobe Mitigation

By Latrobe University

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: La Trobe University has applied for .LATROBE to run a closed .brand environment.
Protections
La Trobe University for the .LATROBE TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that La Trobe University will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .LATROBE is identical to a qualifying registered trademark;
2. .LATROBE is not a Generic String, as this is defined in Specification 11;
3. .LATROBE has developed and will implement a closed registration policy for .LATROBE that requires that all domain names in the .LATROBE TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .LATROBE TLD will clearly publish this registration policy;
5. .LATROBE TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .LATROBE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .LATROBE TLD is a proprietary space in which all second-level domains in the TLD are being operated by La Trobe University - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator.
By this letter, La Trobe University confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-26

Latrobe UniversityYes
lupintwView Comments
2016-02-16
2016-08-03Yes
nationwidetwView Comments
2016-02-16
2016-08-03Yes
onyoursidetwView Comments
2016-02-16
2016-08-03Yes
rexrothtwView Comments
2016-02-16
2016-08-03View Mitigation

rexroth Mitigation

By Robert Bosch GMBH

Provide a brief explanation of the TLD:
Robert Bosch GMBH has applied for .REXROTH to run a closed .brand environment.

Protections
Robert Bosch GMBH for the .REXROTH TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Robert Bosch GMBH will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .REXROTH is identical to a qualifying registered trademark;
2. .REXROTH is not a Generic String, as this is defined in Specification 11;
3. .REXROTH TLD has developed and will implement a closed registration policy for .REXROTH that requires that all domain names in the .REXROTH TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .REXROTH TLD will clearly publish this registration policy;
5. .REXROTH TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .REXROTH TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .REXROTH TLD is a proprietary space in which all second-level domains in the TLD are being operated by Robert Bosch GMBH, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Robert Bosch GMBH confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Robert Bosch GMBHYes
shangrilatwView Comments
2016-02-16
2016-08-03Yes
wolterskluwertwView Comments
2016-02-16
2016-08-03View Mitigation

wolterskluwer Mitigation

By Wolters Kluwer N.V.

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)

Provide a brief explanation of the TLD:

.WOLTERSKLUWER TLD is a closed Brand new gTLD operated by Wolters Kluwer N.V.

Protections:

Wolters Kluwer N.V. for the .WOLTERSKLUWER TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Wolters Kluwer N.V. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

1. .WOLTERSKLUWER is identical to a qualifying registered trademark;
2. .WOLTERSKLUWER is not a Generic String, as this is defined in Specification 11;
3. .WOLTERSKLUWER TLD has developed and will implement a closed registration policy for .WOLTERSKLUWER that requires that all domain names in the .WOLTERSKLUWER TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .WOLTERSKLUWER TLD will clearly publish this registration policy;
5. .WOLTERSKLUWER TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .WOLTERSKLUWER TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WOLTERSKLUWER TLD is a proprietary space in which all second-level domains in the TLD are being operated by Wolters Kluwer N.V., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Wolters Kluwer N.V. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-05

Wolters Kluwer N.V.Yes
xn--5su34j936bgsgtwView Comments
2016-02-16
2016-08-03Yes
amicatwView Comments
2016-03-28
2016-08-03Yes
apptwView Comments
2016-03-28
2016-08-03No
emersontwView Comments
2016-03-28
2016-08-03Yes
farmerstwView Comments
2016-03-28
2016-08-03Yes
gmbhtwView Comments
2016-03-28
2016-08-03View Mitigation

gmbh Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
lidltwView Comments
2016-03-28
2016-08-03No
locustwView Comments
2016-03-28
2016-08-03Yes
promotwView Comments
2016-03-28
2016-08-03No
schwarztwView Comments
2016-03-28
2016-08-03No
statefarmtwView Comments
2016-03-28
2016-08-03Yes
toraytwView Comments
2016-03-28
2016-08-03Yes
webertwView Comments
2016-03-28
2016-08-03Yes
abbvietwView Comments
2016-05-05
2016-08-03Yes
axatwView Comments
2016-05-05
2016-08-03Yes
beautytwView Comments
2016-05-05
2016-08-03No
bestbuytwView Comments
2016-05-05
2016-08-03Yes
contacttwView Comments
2016-05-05
2016-08-03No
dhltwView Comments
2016-05-05
2016-08-03Yes
eposttwView Comments
2016-05-05
2016-08-03Yes
extraspacetwView Comments
2016-05-05
2016-08-03Yes
feedbacktwView Comments
2016-05-05
2016-08-03No
fordtwView Comments
2016-05-05
2016-08-03Yes

ru Comments

By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation

Dear ICANN,
With regards to public consultation process to the draft criteria proposed by ICANN’s GDD Russia would like to use the opportunity to address our concerns about confusion with two-letter country/territory codes at the second level under New gTLDs.
First of all, we also have the same problem as some governments and had already pointed out that it may create confusion with particular ccTLDs and the risk of misleading of Internet users.
In order to avoid any unintended consequences in future, Russia would like to reiterates our request towards ICANN to put on hold any existing requests and not to proceed with releasing Russian country codes and names at the second level under all New gTLDs.
Secondly, we in general agree that there would be useful to establish a list of clear measures that a gTLD registry must implement in order to release from reservation currently reserved two-letter second-level domains and we are prepared to discuss potential mitigation measures to avoid confusion and/or any unintended consequences with the corresponding country code. However, we oppose to allow currently reserved two-letter second-level domains to be released for all gTLD registries at this particular stage.
Further study in all aspects on the advantages and disadvantages respectively is required. We believe that the proposed measures are not quite effective and adequate in addressing the issue of confusion with two-letter country/territory codes at the second level since do not consider the whole picture with corresponding risks and all possible concerns.
Last but not least, we cannot recognize that the proposed measures are consistent with appropriate GAC advice and proposed measures and the actions recommended by the GAC at its Helsinki Communiqué (30th June, 2016).

in Comments

By T SANTHOSH, Scientist E, Ministry of Electronics & IT

“India is not favoring the release of Two-Character ASCII Labels “in”, “ln” , “1n” and deceptively similar to “.in” as the ccTLD at the second level. ICANN is requested that India’s objection on release of Two-Character ASCII Labels “in”, “ln” and “1n” at the second level should apply to all current and future requests from new gTLDs.”

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

tw Comments

By Lin, Mao-Shong, Deputy Director, Ministry of Transportation and Communications

I’m writing hereby to submit Taiwan government’s comments on the release of the “tw” label under the New gTLDs.

We object to the release of “tw” as SLD under all the above-mentioned New gTLDs for their registration by the corresponding Registry operators. We reserve the right to change position in this regard in the future.

The rationale of our objections are below:
Since “tw” label is the country code for Taiwan, the use of “tw” as SLD under these diverse New gTLDs would create confusion or concerns at multiple levels on our part, which include, but not limited to, ”dwarfing national dignity”, “violation of public order or good social custom”, “affecting the rights of domestic enterprises”, and “being prone to produce perplexity to our disadvantage”.

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."