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
worldukView Comments
2015-12-08
2015-12-08View Mitigation

world Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
wowukView Comments
2015-12-08
2015-12-08View 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
wtfukView Comments
2015-12-08
2015-12-08View Mitigation

wtf Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xboxukView Comments
2015-12-08
2015-12-08View Mitigation

xbox Mitigation

By Microsoft Corporation

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

Provide a brief explanation of the TLD:

.XBOX TLD is a closed Brand new gTLD operated by Microsoft Corporation

Protections:

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

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

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


2016-04-05

Microsoft CorporationYes
xeroxukView Comments
2015-12-08
2015-12-08View Mitigation

xerox Mitigation

By Xerox DNHC LLC

.XEROX gTLD Confusion Avoidance Plan
Xerox DNHC LLC, the Registry Operator for the .XEROX gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Xerox DNHC LLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .XEROX is identical to a qualifying registered trademark;
2. .XEROX is not a Generic String, as the term is defined in Specification 11 of the Registry
Agreement;
3. Xerox DNHC LLC has developed and will implement a closed registration policy for
.XEROX that requires that all domain names in the .XEROX gTLD be registered ONLY by
Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Xerox DNHC LLC submitted this policy as part
of its application for Specification 13 and has clearly published this registration policy;
and
5. .XEROX 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 .XEROX gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .XEROX gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Xerox DNHC LLC, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.
With this submission, Xerox DNHC LLC confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


View Documents
2016-04-21

Xerox DNHC LLCYes
xinukView Comments
2015-12-08
2015-12-08View Mitigation

xin Mitigation

By Elegant Leader Limited

A Proposal to Minimize the Potential Likelihood of Confusion in Connection with the Allocation of Specific Two Character Domain Names

The .XIN gTLD wishes to help establish a trusted and reliable namespace for the Chinese market.

Protections
Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:
1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct involving a two character domain name associated with the corresponding government and provide a written report in response
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.
Furthermore, contained within our Acceptable Use Policy for the .XIN TLD is the following text:

“Registry operator reserves the right at its sole discretion to deny, cancel, or transfer any registration or transaction, or place any domain name(s) on registry lock, hold, or similar status, that it deems necessary: (1) to protect the integrity and stability of the registry; (2) to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process; (3) to avoid any liability, civil or criminal, on the part of registry operator, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) per the terms of the registration agreement and this Anti-Abuse Policy, or (5) to correct mistakes made by registry operator or any registrar in connection with a domain name registration. Registry operator also reserves the right to place upon registry lock, hold, or similar status a domain name during resolution of a dispute.



View Documents
2016-04-25

Elegant Leader LimitedNo
xn--1ck2e1bukView Comments
2015-12-08
2015-12-08View Mitigation

xn--1ck2e1b Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--3bst00mukView Comments
2015-12-08
2015-12-08No
xn--3ds443gukView Comments
2015-12-08
2015-12-08No
xn--3oq18vl8pn36aukView Comments
2015-12-08
2015-12-08View 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--45q11cukView Comments
2015-12-08
2015-12-08View Mitigation

xn--45q11c Mitigation

By Zodiac Registry

This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs:

Registry Operator TLD English translation
Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王"
Zodiac Aquarius Limited .商城 (xn--czru2d) .mall
Zodiac Taurus Limited .网店(xn--hxt814e) .web store
Zodiac Gemini Limited .八卦(xn--45q11c) .gossip

All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country.

As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise.

Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion.

Protections

1. Registry Operator will commit to:

a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use:

“Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law”
…
“Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion:

a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;”

Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term:

“Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.”

This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted.


2016-04-22

Zodiac RegistryNo
xn--55qx5dukView Comments
2015-12-08
2015-12-08No
xn--6frz82gukView Comments
2015-12-08
2015-12-08View Mitigation

xn--6frz82g Mitigation

By Afilias

Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion.


2016-04-20

AfiliasNo
xn--6qq986b3xlukView Comments
2015-12-08
2015-12-08No
xn--80adxhksukView Comments
2015-12-08
2015-12-08No
xn--bck1b9a5dre4cukView Comments
2015-12-08
2015-12-08View Mitigation

xn--bck1b9a5dre4c Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--cck2b3bukView Comments
2015-12-08
2015-12-08View Mitigation

xn--cck2b3b Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--czr694bukView Comments
2015-12-08
2015-12-08View Mitigation

xn--czr694b Mitigation

By HU YI GLOBAL INFORMATION RESOURCES (HOLDING) COMPANY. HONGKONG LIMITED

Please see the attached file that details ". 商标" (dot Trademark) (xn--czr694b)
Registry's implementation plan to avoid confusion with corresponding country codes.


View Documents
2016-04-25

HU YI GLOBAL INFORMATION RESOURCES (HOLDING) COMPANY. HONGKONG LIMITEDNo
xn--czrs0tukView Comments
2015-12-08
2015-12-08View Mitigation

xn--czrs0t Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--czru2dukView Comments
2015-12-08
2015-12-08View Mitigation

xn--czru2d Mitigation

By Zodiac Registry

This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs:

Registry Operator TLD English translation
Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王"
Zodiac Aquarius Limited .商城 (xn--czru2d) .mall
Zodiac Taurus Limited .网店(xn--hxt814e) .web store
Zodiac Gemini Limited .八卦(xn--45q11c) .gossip

All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country.

As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise.

Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion.

Protections

1. Registry Operator will commit to:

a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use:

“Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law”
…
“Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion:

a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;”

Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term:

“Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.”

This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted.


2016-04-22

Zodiac RegistryNo
xn--eckvdtc9dukView Comments
2015-12-08
2015-12-08View Mitigation

xn--eckvdtc9d Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--fct429kukView Comments
2015-12-08
2015-12-08View Mitigation

xn--fct429k Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--fiq228c5hsukView Comments
2015-12-08
2015-12-08No
xn--fiq64bukView Comments
2015-12-08
2015-12-08No
xn--fjq720aukView Comments
2015-12-08
2015-12-08View Mitigation

xn--fjq720a Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--g2xx48cukView Comments
2015-12-08
2015-12-08View Mitigation

xn--g2xx48c Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
xn--gckr3f0fukView Comments
2015-12-08
2015-12-08View Mitigation

xn--gckr3f0f Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--gk3at1e ukView Comments
2015-12-08
2015-12-08View 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
xn--hxt814eukView Comments
2015-12-08
2015-12-08View Mitigation

xn--hxt814e Mitigation

By Zodiac Registry

This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs:

Registry Operator TLD English translation
Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王"
Zodiac Aquarius Limited .商城 (xn--czru2d) .mall
Zodiac Taurus Limited .网店(xn--hxt814e) .web store
Zodiac Gemini Limited .八卦(xn--45q11c) .gossip

All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country.

As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise.

Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion.

Protections

1. Registry Operator will commit to:

a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and

b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use:

“Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law”
…
“Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion:

a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;”

Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term:

“Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.”

This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted.


2016-04-22

Zodiac RegistryNo
xn--io0a7iukView Comments
2015-12-08
2015-12-08No
xn--jvr189mukView Comments
2015-12-08
2015-12-08View Mitigation

xn--jvr189m Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--kcrx77d1x4aukView Comments
2015-12-08
2015-12-08View Mitigation

xn--kcrx77d1x4a Mitigation

By Koninklijke Philips N.V.

Registry Operator will not register two letter SLDs that are equal to ccTLDs under its gTLD, unless:
- the corresponding country has given general consent to register these SLDs, or
- that Registry Operator has obtained authorization of the competent authority of that corresponding country to register the two letter SLD under its TLD..

Registry Operator will not register two letter SLDs under its TLD that are equal to ccTLDs when the corresponding country has objected to these registrations.


2016-03-08

Koninklijke Philips N.V.Yes
xn--ngbe9e0aukView Comments
2015-12-08
2015-12-08No
xn--q9jyb4cukView Comments
2015-12-08
2015-12-08View Mitigation

xn--q9jyb4c Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)No
xn--rovu88bukView Comments
2015-12-08
2015-12-08View Mitigation

xn--rovu88b Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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--ses554gukView Comments
2015-12-08
2015-12-08No
xn--unup4yukView Comments
2015-12-08
2015-12-08View Mitigation

xn--unup4y Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--vermgensberater-ctbukView Comments
2015-12-08
2015-12-08No
xn--vermgensberatung-pwbukView Comments
2015-12-08
2015-12-08No
xn--vhquvukView Comments
2015-12-08
2015-12-08View Mitigation

xn--vhquv Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--vuq861bukView Comments
2015-12-08
2015-12-08No
xn--w4r85el8fhu5dnraukView Comments
2015-12-08
2015-12-08No
xn--w4rs40lukView Comments
2015-12-08
2015-12-08Yes
xperiaukView Comments
2015-12-08
2015-12-08View Mitigation

xperia Mitigation

By Sony Mobile Communications AB

Provide a brief explanation of the TLD:
Sony Mobile Communications AB has applied for .XPERIA to run a closed .brand environment.

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

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


2016-04-25

Sony Mobile Communications ABYes
xxxukView Comments
2015-12-08
2015-12-08View Mitigation

xxx Mitigation

By ICM Registry

Protections

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any governments, and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

Furthermore, we have the following Anti-Abuse Policy:

Registry has the right, pursuant to its Registry-Registrant Agreement, to immediately deny, cancel, terminate, suspend, lock, hold, or transfer any domain name and/or registration to ensure registrant’s compliance with the following Anti-Abuse Policy.

1. Accurate Registration Information
Registrant represents and warrants to have provided current, complete, and accurate information in connection with its registration and agrees to correct and update this information to ensure that it remains current, complete, and accurate throughout the term of any resulting registration in a TLD. Registrant’s obligation to provide current, accurate, and complete information is a material element of the Registry-Registrant Agreement, and the registry reserves the right to immediately deny, cancel, terminate, suspend, lock, or transfer any registration if it determines, in its sole discretion, that the information is materially inaccurate.

2. Child Protection Labeling
Registrant understands that Registry Operator may label the sites in the TLD and any site to which such sites are automatically redirected irrespective of the top-level domain for child protection purposes; registrant consents to such labeling.

3. Prohibition on Child Abuse Images and Conduct or Content Designed to Suggest the Presence of Child Abuse Images
The term “child abuse images” is defined as any photograph, film, video, picture, or computer or computer-generated image or picture, whether made or produced by electronic, mechanical, or other means, depicting child sexual abuse as stated in the United Nations Convention on the Rights of the Child. Registrant’s sites in the TLD shall not display any child abuse images. Registrant’s sites in the TLD shall not engage in practices that are designed to suggest the presence of child abuse images, including, without limitation, the use of meta-tags for that purpose. Registry Operator will refer any sites in a TLD that are reported to the Registry Operator to be in violation of this policy to child safety hotlines like the National Center for Missing and Exploited Children (NCMEC), the Internet Watch Foundation (IWF), or the International Association of Internet Hotlines (INHOPE).

4. Prohibition on Abusive Registrations
No registrant may register an abusive second-level domain name in the TLD including, without limitation, domain names that infringe the intellectual property rights of a third party, including common law trademark rights; domain names that are obvious variants of well-known trademarks not belonging to the registrant; or domain names that suggest the presence of child abuse images.

5. Prohibition on Malicious Conduct
No registrant shall use or permit use of a domain name in the TLD for or in connection with email spoofing, phishing, spam, or other forms of malicious behavior.

6. Ongoing Best Practices Policies
Registry Operator will revise this Anti-Abuse Policy or the Registry-Registrant Agreement to include commercially reasonable best practices policies developed by the International Foundation for Online Responsibility (IFFOR) that are designed to promote responsible business practices related to (i) combating online child abuse images, (ii) facilitating user choice and parental control regarding access to online adult entertainment, (iii) protecting free expression rights, and/or (iv) protecting the privacy, security, and consumer rights of consenting adult consumers of online adult entertainment goods and services; registrant consents to adhere to such policies.

The Registrant of a domain name, as recorded in the Registry Service, will be responsible for:
a. the use of their domain name;
b. ensuring that the use of the domain name, where that domain name is a two letter Label that corresponds to a country code described in the ISO 3166-1 alpha-2 standard, avoids confusion with the corresponding country code;”

Should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-19

ICM Registry No
xyzukView Comments
2015-12-08
2015-12-08No
yachtsukView Comments
2015-12-08
2015-12-08View Mitigation

yachts Mitigation

By DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)

See attached document


View Documents
2016-04-26

DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)No
yahooukView Comments
2015-12-08
2015-12-08View Mitigation

yahoo Mitigation

By Yahoo! Domain Services Inc.

.YAHOO TLD is a closed Brand new gTLD operated by Yahoo! Domain Services Inc.

Protections:

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

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

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


2016-04-12

Yahoo! Domain Services Inc.Yes
yamaxunukView Comments
2015-12-08
2015-12-08View Mitigation

yamaxun Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .YAMAXUN TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw.

ARSI has applied for and been granted an exemption to the Registry Operator Code of Conduct under Specification 9 to the Registry Agreement. This Code of Conduct exemption already contractually requires ARSI to apply measures which, by their very nature, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely the following:

• Developing and implementing a registration policy for .YAMAXUN that requires that all domain names in the .YAMAXUN TLD be registered to, and maintained by, ARSI for the exclusive use of ARSI or its Affiliates;
• Before any domain names other than are registered in the .YAMAXUN TLD, publishing this registration policy on ARSI’s website for the .YAMAXUN TLD; and
• Ensuring continued compliance with the registration policy through annual certification of the .YAMAXUN TLD’s qualification for an exemption to the Registry Operator Code of Conduct.

The .YAMAXUN registration policy prevents governments from registering .YAMAXUN domain names. It clearly states that all domain names in the .YAMAXUN TLD will be registered to, and maintained by, ARSI for the exclusive use of ARSI or its Affiliates, not to any governments. Accordingly, there will be no basis on which a .YAMAXUN domain name could be confused with the country codes corresponding to the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw.


2016-04-25

Amazon Registry Services, Inc.No
yodobashiukView Comments
2015-12-08
2015-12-08View Mitigation

yodobashi Mitigation

By YODOBASHI CAMERA CO.,LTD.

2 Letter Codes Mitigation Plan for YODOBASHI TLDs
(.yodobashi .goldpoint)

To address the confusion concerns cited by governments regarding the use of the second-level domains in the YODOBASHI TLDs,
YODOBASHI CAMERA CO.,LTD. will implement a closed registration policy for YODOBASHI TLDs that mitigates the potential confusion. To these ends, YODOBASHI CAMERA CO., LTD. commits to the following:

・Developing and implementing a closed registration policy for YODOBASHI TLDs that requires that all domains name in the TLDs be registered and used by YODOBASHI CAMERA CO.,LTD., its affiliates, or its trademark licensees;

・Clearly publishing this registration policy on Registry Operator`s homepage for the YODOBASHI TLDs at “nic.yodobashi”, and “nic.goldpoint”.

・Referring to this registration policy in registry Operator`s Registry-Registrar Agreement with all appointed preferred registrars for the YODOBASHI TLDs.

・Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of YODOBASHI TLDs` qualification for Specification 13; and

・Using all domain names in the YODOBASHI TLDs in association with YODOBASHI`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the YODOBASHI TLDs. It would therefore clearly designate to the public that YODOBASHI TLDs were proprietary spaces in which all second-level domains in the TLDs were being operated by YODOBASHI CAMERA CO., LTD. and not governments.


2016-04-25

YODOBASHI CAMERA CO.,LTD.Yes
yogaukView Comments
2015-12-08
2015-12-08View Mitigation

yoga Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
yokohamaukView Comments
2015-12-08
2015-12-08View Mitigation

yokohama Mitigation

By GMO Registry

About .YOKOHAMA

.YOKOHAMA is a GeoTLD for the city of Yokohama, Japan, operated by GMO Registry, Inc. The purpose of .YOKOHAMA is to promote .YOKOHAMA and provide an opportunity for citizens, businesses and community groups to link their identities to the city’s brand. By bringing together quality and informative content, .YOKOHAMA provides a platform to effectively deliver city information to Internet users both locally and globally. It is also an important goal for the Registry that .YOKOHAMA is operated as a trusted, safe, secure, relevant and enjoyable namespace

Protections
Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:
1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the governments of a related country-code and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.
Furthermore, contained within our Domain Name Registration Policy for the .YOKOHAMA TLD is the following text:

All Applicants, all Domain Name Registrants, and any party submitting a Domain Name registration request represents and warrants that:
− to its knowledge, the registration of the Domain Name mentioned in the Application
or Domain Name Registration Request will not infringe upon or otherwise violate the
rights of any third party;
− will not register a domain name for the purpose of distributing malware, abusively
operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent
or deceptive practices, counterfeiting or otherwise engaging in activity contrary to
applicable laws or regulations;

Should a Registrant fail to comply with the Acceptable Use Policy, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

GMO RegistryNo
youukView Comments
2015-12-08
2015-12-08View Mitigation

you Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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
youtubeukView Comments
2015-12-08
2015-12-08View Mitigation

youtube Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)Yes
zapposukView Comments
2015-12-08
2015-12-08View Mitigation

zappos Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw.

ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely:

1. Each of the .Brand TLDs is identical to a qualifying registered trademark;
2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11;
3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates;
4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and
5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs.

Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above.


2016-04-25

Amazon Registry Services, Inc.Yes
zaraukView Comments
2015-12-08
2015-12-08View Mitigation

zara Mitigation

By INDITEX, S.A.

.ZARA TLD is a closed Brand new gTLD operated by Inditex S.A.

Protections:

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

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

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


2016-04-20

INDITEX, S.A.Yes
zeroukView Comments
2015-12-08
2015-12-08View Mitigation

zero Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. 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, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs 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 TLDs will require registrants of a domain name in each of the TLDs 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
zoneukView Comments
2015-12-08
2015-12-08View Mitigation

zone Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
zuerichukView Comments
2015-12-08
2015-12-08No
abbjoView Comments
2015-12-17
2015-12-17View Mitigation

abb Mitigation

By ABB Ltd

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

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

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


2016-04-25

ABB LtdYes
acojoView Comments
2015-12-17
2015-12-17View 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
anzjoView Comments
2015-12-17
2015-12-17View Mitigation

anz Mitigation

By Australia and New Zealand Banking Group Limited

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


2016-04-22

Australia and New Zealand Banking Group LimitedYes
artejoView Comments
2015-12-17
2015-12-17View Mitigation

arte Mitigation

By Association Relative à la Télévision Européenne G.E.I.E.

Provide a brief explanation of the TLD:
Association Relative à la Télévision Européenne G.E.I.E. has applied for .ARTE to run a closed .brand environment.

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

Compliance with Specification 13 prohibits the .ARTE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ARTE TLD is a proprietary space in which all second-level domains in the TLD are being operated by Association Relative à la Télévision Européenne G.E.I.E., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Association Relative à la Télévision Européenne G.E.I.E. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Association Relative à la Télévision Européenne G.E.I.E.Yes
audijoView Comments
2015-12-17
2015-12-17View 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
audiojoView Comments
2015-12-17
2015-12-17No
blackfridayjoView Comments
2015-12-17
2015-12-17No
bugattijoView Comments
2015-12-17
2015-12-17View 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
christmasjoView Comments
2015-12-17
2015-12-17No
clickjoView Comments
2015-12-17
2015-12-17No
cscjoView Comments
2015-12-17
2015-12-17View 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
dietjoView Comments
2015-12-17
2015-12-17No
flowersjoView Comments
2015-12-17
2015-12-17No
foxjoView Comments
2015-12-17
2015-12-17View 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
gamejoView Comments
2015-12-17
2015-12-17No
geajoView Comments
2015-12-17
2015-12-17View 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
giftjoView Comments
2015-12-17
2015-12-17No
graingerjoView Comments
2015-12-17
2015-12-17View 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
guitarsjoView Comments
2015-12-17
2015-12-17No
helpjoView Comments
2015-12-17
2015-12-17No
hiphopjoView Comments
2015-12-17
2015-12-17No
hostingjoView Comments
2015-12-17
2015-12-17No
juegosjoView Comments
2015-12-17
2015-12-17No
lamborghinijoView Comments
2015-12-17
2015-12-17View 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
lanxessjoView Comments
2015-12-17
2015-12-17View 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
lefrakjoView Comments
2015-12-17
2015-12-17View 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
linkjoView Comments
2015-12-17
2015-12-17No
loljoView Comments
2015-12-17
2015-12-17No
matteljoView Comments
2015-12-17
2015-12-17View 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
momjoView Comments
2015-12-17
2015-12-17No
moscowjoView Comments
2015-12-17
2015-12-17No
mtrjoView Comments
2015-12-17
2015-12-17View 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
photojoView Comments
2015-12-17
2015-12-17No
picsjoView Comments
2015-12-17
2015-12-17No
pncjoView Comments
2015-12-17
2015-12-17Yes
propertyjoView Comments
2015-12-17
2015-12-17No
redumbrellajoView Comments
2015-12-17
2015-12-17No
rmitjoView Comments
2015-12-17
2015-12-17View 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
safetyjoView Comments
2015-12-17
2015-12-17View 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
sanofijoView Comments
2015-12-17
2015-12-17View Mitigation

sanofi Mitigation

By Sanofi

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

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

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


2016-04-25

SanofiYes
sexyjoView Comments
2015-12-17
2015-12-17No

uk Comments

By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport

In order to avoid the potential for confusion, and any unintended consequences, the UK government wish to be notified of all registry requests to use the two characters of its country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.

jo Comments

By Jowin V Pattamukkil, Student, Technical

I need Jo.win
Under .win domains
For technical website purposes.

It will not be confused with any other govt or other agencies.. It locked only becoz of icann policy of two letter domain reserved... And it is on release option..I need it it urgently.. Becoz of my company needs.. Kindly allow me to register..

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