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
xn--fjq720asuView Comments
2015-12-07
2016-08-15View Mitigation

xn--fjq720a Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--g2xx48csuView Comments
2015-12-07
2016-08-15View 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--gckr3f0fsuView Comments
2015-12-07
2016-08-15View 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 suView Comments
2015-12-07
2016-08-15View 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--hxt814esuView Comments
2015-12-07
2016-08-15View 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--io0a7isuView Comments
2015-12-07
2016-08-15No
xn--jvr189msuView Comments
2015-12-07
2016-08-15View 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--kcrx77d1x4asuView Comments
2015-12-07
2016-08-15View 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--ngbe9e0asuView Comments
2015-12-07
2016-08-15No
xn--q9jyb4csuView Comments
2015-12-07
2016-08-15View 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--rovu88bsuView Comments
2015-12-07
2016-08-15View 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--ses554gsuView Comments
2015-12-07
2016-08-15No
xn--unup4ysuView Comments
2015-12-07
2016-08-15View Mitigation

xn--unup4y Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--vermgensberater-ctbsuView Comments
2015-12-07
2016-08-15No
xn--vermgensberatung-pwbsuView Comments
2015-12-07
2016-08-15No
xn--vhquvsuView Comments
2015-12-07
2016-08-15View Mitigation

xn--vhquv Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
xn--vuq861bsuView Comments
2015-12-07
2016-08-15No
xn--w4r85el8fhu5dnrasuView Comments
2015-12-07
2016-08-15No
xn--w4rs40lsuView Comments
2015-12-07
2016-08-15Yes
xperiasuView Comments
2015-12-07
2016-08-15View 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
xxxsuView Comments
2015-12-07
2016-08-15View 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
xyzsuView Comments
2015-12-07
2016-08-15No
yachtssuView Comments
2015-12-07
2016-08-15View 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
yahoosuView Comments
2015-12-07
2016-08-15View 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
yamaxunsuView Comments
2015-12-07
2016-08-15View 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
yodobashisuView Comments
2015-12-07
2016-08-15View 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
yogasuView Comments
2015-12-07
2016-08-15View 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
yokohamasuView Comments
2015-12-07
2016-08-15View 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
yousuView Comments
2015-12-07
2016-08-15View 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
youtubesuView Comments
2015-12-07
2016-08-15View 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
zappossuView Comments
2015-12-07
2016-08-15View 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
zarasuView Comments
2015-12-07
2016-08-15View 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
zerosuView Comments
2015-12-07
2016-08-15View 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
zonesuView Comments
2015-12-07
2016-08-15View Mitigation

zone Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
zuerichsuView Comments
2015-12-07
2016-08-15No
amicasuView Comments
2016-03-22
2016-08-15Yes
appsuView Comments
2016-03-22
2016-08-15No
axasuView Comments
2016-03-22
2016-08-15Yes
bmssuView Comments
2016-03-22
2016-08-15View Mitigation

bms Mitigation

By Bristol Myers Squibb

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


2016-04-20

Bristol Myers SquibbYes
emersonsuView Comments
2016-03-22
2016-08-15Yes
extraspacesuView Comments
2016-03-22
2016-08-15Yes
farmerssuView Comments
2016-03-22
2016-08-15Yes
freesuView Comments
2016-03-22
2016-08-15No
gmbhsuView Comments
2016-03-22
2016-08-15View Mitigation

gmbh Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
groupsuView Comments
2016-03-22
2016-08-15View Mitigation

group Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
insurancesuView Comments
2016-03-22
2016-08-15View Mitigation

insurance Mitigation

By fTLD Registry Services, LLC

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


View Documents
2016-04-20

fTLD Registry Services, LLCNo
lidlsuView Comments
2016-03-22
2016-08-15No
locussuView Comments
2016-03-22
2016-08-15Yes
ltdsuView Comments
2016-03-22
2016-08-15View Mitigation

ltd Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
lupinsuView Comments
2016-03-22
2016-08-15Yes
mcdsuView Comments
2016-03-22
2016-08-15Yes
mcdonaldssuView Comments
2016-03-22
2016-08-15Yes
mensuView Comments
2016-03-22
2016-08-15View Mitigation

men Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, 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

Famous Four Media LimitedNo
promosuView Comments
2016-03-22
2016-08-15No
racingsuView Comments
2016-03-22
2016-08-15View Mitigation

racing Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, 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

Famous Four Media LimitedNo
realtorsuView Comments
2016-03-22
2016-08-15No
salonsuView Comments
2016-03-22
2016-08-15View Mitigation

salon Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
schwarzsuView Comments
2016-03-22
2016-08-15No
stadasuView Comments
2016-03-22
2016-08-15Yes
statefarmsuView Comments
2016-03-22
2016-08-15Yes
toraysuView Comments
2016-03-22
2016-08-15Yes
webersuView Comments
2016-03-22
2016-08-15Yes
williamhillsuView Comments
2016-03-22
2016-08-15Yes
wolterskluwersuView Comments
2016-03-22
2016-08-15View Mitigation

wolterskluwer Mitigation

By Wolters Kluwer N.V.

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

Provide a brief explanation of the TLD:

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

Protections:

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

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

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


2016-04-05

Wolters Kluwer N.V.Yes
camsuView Comments
2016-08-15
2016-08-15No
doctorsuView Comments
2016-08-15
2016-08-15No
fujixeroxsuView Comments
2016-08-15
2016-08-15Yes
gamessuView Comments
2016-08-15
2016-08-15No
gdnsuView Comments
2016-08-15
2016-08-15No
ikanosuView Comments
2016-08-15
2016-08-15Yes
jcpsuView Comments
2016-08-15
2016-08-15Yes
quebecsuView Comments
2016-08-15
2016-08-15No
totalsuView Comments
2016-08-15
2016-08-15Yes
wtcsuView Comments
2016-08-15
2016-08-15Yes
aarpruView Comments
2015-12-07
2016-08-15View Mitigation

aarp Mitigation

By AARP

.AARP gTLD Confusion Avoidance Plan

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

1. .AARP is identical to a qualifying registered trademark;
2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .AARP 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 .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

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


View Documents
2016-04-25

AARPYes
abbruView Comments
2015-12-07
2016-08-15View 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
abbottruView Comments
2015-12-07
2016-08-15View Mitigation

abbott Mitigation

By Abbott Laboratories, Inc.

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

1. .ABBOTT is identical to a qualifying registered trademark;
2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement;
3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and
5. .ABBOTT 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 .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

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


2016-04-22

Abbott Laboratories, Inc.Yes
abogadoruView Comments
2015-12-07
2016-08-15View Mitigation

abogado 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
academyruView Comments
2015-12-07
2016-08-15View Mitigation

academy Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
accentureruView Comments
2015-12-07
2016-08-15View Mitigation

accenture Mitigation

By Accenture plc

Proposed Measure to Avoid Confusion—Brand TLD (Specification 13)
Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment.

Protections

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


2016-04-20

Accenture plcYes
accountantruView Comments
2015-12-07
2016-08-15View Mitigation

accountant Mitigation

By Famous Four Media Limited

By Famous Four media Limited.

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

2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants.

3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, 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

Famous Four Media LimitedNo
accountantsruView Comments
2015-12-07
2016-08-15View Mitigation

accountants Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
acoruView Comments
2015-12-07
2016-08-15View 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
actorruView Comments
2015-12-07
2016-08-15View Mitigation

actor Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
adultruView Comments
2015-12-07
2016-08-15View Mitigation

adult 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
aegruView Comments
2015-12-07
2016-08-15View Mitigation

aeg Mitigation

By Aktiebolaget Electrolux

Provide a brief explanation of the TLD:
Aktiebolaget Electrolux has applied for .[TLD] to run a closed .brand environment.

Protections
Aktiebolaget Electrolux for the .[TLD] TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Aktiebolaget Electrolux 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 Aktiebolaget Electrolux, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator.
By this letter Aktiebolaget Electrolux confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Aktiebolaget ElectroluxYes
agencyruView Comments
2015-12-07
2016-08-15View Mitigation

agency Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
aigruView Comments
2015-12-07
2016-08-15View Mitigation

aig Mitigation

By American International Group, Inc.

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


2016-04-20

American International Group, Inc.Yes
airforceruView Comments
2015-12-07
2016-08-15View Mitigation

airforce Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
allfinanzruView Comments
2015-12-07
2016-08-15View Mitigation

allfinanz Mitigation

By Allfinanz Deutsche Vermögensberatung Aktiengesellschaft

Please find Allfinanz Deutsche Vermögensberatung Aktiengesellschaft's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.ALLFINANZ” attached.


View Documents
2016-04-23

Allfinanz Deutsche Vermögensberatung AktiengesellschaftNo
allyruView Comments
2015-12-07
2016-08-15Yes
amsterdamruView Comments
2015-12-07
2016-08-15View Mitigation

amsterdam Mitigation

By City of Amsterdam

For the top level domain .AMSTERDAM we would like to use two letter domains and we propose the following measures to avoid confusion.

A brief explanation of the TLD:
.amsterdam is a geographic TLD for the City of Amsterdam; the City of Amsterdam is the designated Registry Operator. The toplevel domain is open, anyone in the world can register domain names.

Proposed measures to avoid confusion
The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ci, cn, eg, hk, il, in, it, me, pt and sg.

Protections
The Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:
• Registry Operator will commit to investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and
• where, in Registry Operator's sole opinion, misuse has occurred, cause the domain name's records to be removed from the DNS.

Policy measures
Contained within our Acceptable Use Policy for .amsterdam is the following text:
".Abuse in the context of this Policy shall be defined as an action that causes actual and substantial harm, or is a material predicate of such harm, or is illegal, illegitimate, or otherwise contrary to this Policy, including, but not limited to, the following:
...
h. Violation of any applicable local, state, national or international law or regulation by use of a Domain Name;
i . The confusing use of a 2character domain name that corresponds to a country code as described in the ISO 3166 alpha 2 standard with the corresponding country code...”

Should a Registrant fail to comply with the Acceptable Use Policy, the registry has the right to lock, transfer or cancel any offending domain name. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and the City of Amsterdam has clear penalties for any failure to do so.


View Documents
2016-05-09

City of AmsterdamNo
analyticsruView Comments
2015-12-07
2016-08-15View Mitigation

analytics Mitigation

By Karen L. Day

Please see the attached documents outlining our registry's plans to avoid confusion with certain 2 character labels as previously requested.


View Documents
2016-05-06

Karen L. DayNo
androidruView Comments
2015-12-07
2016-08-15View Mitigation

android 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
anzruView Comments
2015-12-07
2016-08-15View 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
apartmentsruView Comments
2015-12-07
2016-08-15View Mitigation

apartments Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
appleruView Comments
2015-12-07
2016-08-15Yes
aquarelleruView Comments
2015-12-07
2016-08-15Yes
archiruView Comments
2015-12-07
2016-08-15View Mitigation

archi Mitigation

By Starting Dot

The proposed measure to avoid confusion for .ARCHI applies across all two-character labels.

The proposed measure can be found in the file attached.


View Documents
2016-04-25

Starting DotNo
armyruView Comments
2015-12-07
2016-08-15View Mitigation

army Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No

su Comments

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

Russia objects the release of Two-Character combination “.su” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

su Comments

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

Russia objects the release of Two-Character combination “.su” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with the country code ccTLD creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests. However, we are prepared to discuss potential mitigation measures to avoid confusion and/or any unintended consequences with the corresponding country code if any to be proposed.

su Comments

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

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

ru Comments

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

Russia objects the release of Two-Character combination “.ru” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

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