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
nikontwView Comments
2015-10-14
2015-12-02Yes
nowtwView Comments
2015-10-14
2015-12-02View Mitigation

now 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
nrwtwView Comments
2015-10-14
2015-12-02View Mitigation

nrw 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
nyctwView Comments
2015-10-14
2015-12-02View Mitigation

nyc Mitigation

By The City of New York by and through the New York City Department of Information Technology & Telecommunications

Proposed Measure to Avoid Confusion

A brief explanation of the TLD
The .nyc is a geographic TLD representing the city of New York. The designated “Registry Operator” is The City of New York, a municipal corporation under the laws of the State of New York, by and through the New York City Department of Information Technology & Telecommunications. The .nyc TLD is open for registration to individuals or entities having a substantive and lawful connection to the city of New York. This requirement for “nexus” with the city of New York is strictly enforced and is described in our Nexus Policy which can be found at the following link: http://www.ownit.nyc/policies/nyc_nexus_policy.php. Further in order to ensure that we have complete Registrant information the .nyc TLD does not allow the use of proxy, private or anonymous domain name registrations. The .nyc TLD employs an algorithm to detect the inadvertent or intentional registration of proxy, anonymous and/or private domain name registrations, and enforces a Registrar’s obligation to not offer such services.

The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ai, bm, ci, cn, eg, hk, il, in, io, it, ky, me, ms, pt, sg, sh, tc and tw.

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 the government 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 Acceptable Use Policy for the .nyc TLD is the following text:
“1. By registering a name in the .nyc top-level domain (.NYC), you represent and warrant that you will not use that registration for any illegal purposes, including without limitation, to:
…
4. Infringe the intellectual property rights of any other person or entity including, without limitation, counterfeiting, piracy or trademark or copyright infringement;
5. Impersonate any person or entity, or submit information on behalf of any other person or entity, without their express prior written consent;…”

Should a Registrant fail to comply with the Acceptable Use Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted.

Thus all Registrants in the TLD have an obligation not to infringe any intellectual property rights nor to impersonate any person or entity, including the governments that are represented by these two letter country codes, and there are clear penalties in place for doing so.


2016-04-25

The City of New York by and through the New York City Department of Information Technology & TelecommunicationsNo
obitwView Comments
2015-10-14
2015-12-02View Mitigation

obi Mitigation

By OBI Group Holding SE & Co. KGaA

.obi is a closed top-level domain name for the sole and exclusive use of OBI Group Holding SE & Co. KGaA.

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


2016-04-25

OBI Group Holding SE & Co. KGaAYes
omegatwView Comments
2015-10-14
2015-12-02View Mitigation

omega Mitigation

By The Swatch Group Ltd

Provide a brief explanation of the TLD:
The Swatch Group Ltd has applied for .OMEGA to run a closed .brand environment.

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

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


2016-04-25

The Swatch Group LtdYes
onlinetwView Comments
2015-10-14
2015-12-02View Mitigation

online Mitigation

By Radix

Dear ICANN,

We are submitting these proposed measures to avoid confusion with specific country codes at the second level for each of our 8 TLDs, in relation to the individual Government objections that have been raised pertaining to the release of those specific two-character labels:

Protections

Radix understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:

1. Radix will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the relevant governments that have raised concerns about the release of specific two-character labels at the second level, and provide a written report in response; and

b. where, in Radix’s sole opinion, misuse has occurred, Radix will seek to work
with the sponsoring registrar and/or directly with the registrant to address the misuse.

c. In the event that misuse continues to occur, Radix may, in its sole discretion,
undertake direct action up to and including suspension or deletion of the domain name.

Thank you.


2016-04-25

RadixNo
oracletwView Comments
2015-10-14
2015-12-02Yes
orangetwView Comments
2015-10-14
2015-12-02View Mitigation

orange Mitigation

By Orange Brand Services Limited

Provide a brief explanation of the TLD:
Orange Brand Services Limited has applied for .ORANGE to run a closed .brand environment.

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

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


2016-04-25

Orange Brand Services LimitedYes
originstwView Comments
2015-10-14
2015-12-02Yes
osakatwView Comments
2015-10-14
2015-12-02No
paytwView Comments
2015-10-14
2015-12-02View Mitigation

pay 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
pettwView Comments
2015-10-14
2015-12-02View Mitigation

pet 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
pharmacytwView Comments
2015-10-14
2015-12-02View Mitigation

pharmacy Mitigation

By National Association of Boards of Pharmacy

Background

The National Association of Boards of Pharmacy® (NABP®), the impartial professional organization that supports state boards of pharmacy in protecting public health, is the exclusive Registry Operator for the .pharmacy Top-Level Domain (TLD). The .pharmacy TLD was established to provide a secure, verified, and trustworthy TLD where consumers around the globe can be sure the medications they buy online are safe. To that end, a global coalition of stakeholders, including NABP and the International Pharmaceutical Federation, developed policies and maintains standards to govern the .pharmacy TLD, ensuring those websites with a .pharmacy domain are safe and legal.

Implementation Plan to Avoid Confusion

To respond to the confusion concerns cited by several governments regarding the use of the second-level domains (SLDs) in the .pharmacy TLD, NABP notes that it currently implements a restricted registration policy for .pharmacy that recognizes the ongoing and critical need for patients’ medications to be managed by a licensed pharmacist and for their medications to be appropriately sourced in accordance with applicable standards of care. A copy of the policy can be found at http://safe.pharmacy/standards-policies. The very fact that .pharmacy verifies that each entity acquiring a .pharmacy SLD meets all applicable regulatory standards, including those addressing pharmacy licensure and valid prescription requirements, prior to allowing that entity to register a .pharmacy domain name avoids any potential confusion between the .pharmacy registration and a country code.

In order to ensure that there will be no confusion between any two character registrations and a country code sharing the same two letters, NABP will administer its verified registry operation in a manner that avoids potential confusion by:
• Continuing to implement a restricted registration policy for .pharmacy that verifies that each entity acquiring a .pharmacy SLD is an eligible member of the pharmacy community and meets all applicable regulatory standards to conduct pharmacy-related business.
• Continuing to implement a restricted registration policy that ensures website content is relevant to pharmacy services and drug information, which provides the opportunity for NABP to proactively identify any potential confusing use of the domain name with a corresponding country code.
• Maintaining, and continuing to create, ongoing “working relationship[s] with the relevant regulatory, or industry self-regulatory, bodies, including developing a strategy to mitigate as much as possible the risks of fraudulent, and other illegal, activities.” See Beijing GAC Communique. NABP will not issue a .pharmacy domain name in a given country until it has created a relationship with the appropriate health care regulators for a jurisdiction.
• Clearly publishing this registration policy on .pharmacy’s registry homepage.
• Including this registration policy in NABP’s Registry-Registrar Agreement with all accredited registrars for the .pharmacy TLD.
• Enforcing this registration policy and ensuring continued compliance. The process for obtaining a .pharmacy domain name is described here: http://www.safe.pharmacy/apply. More detailed instructions and information are available here: http://www.safe.pharmacy/apply/application-instructions.

NABP’s use of .pharmacy two-character domains would not, in and of itself and absent a verification process, cause any confusion with the corresponding two-letter country codes; nonetheless, NABP further contends that it avoids any potential confusion through its strenuous verification requirements and registration policies, which ensure only licensed and verified pharmacy-related entities are permitted to register and use .pharmacy domains.

Request to ICANN in Accordance With Specification 5 of the Registry Agreement

Based on public comments received, no government objecting to the release of its country code offered a specific explanation for the potential confusion arising from the use of a two-character SLD within a verified registry operation (as defined herein); therefore, based on the aforementioned proposal to avoid confusion as a verified registry operation and in accordance with Specification 5 of its Registry Agreement, NABP respectfully requests that Internet Corporation for Assigned Names and Numbers release the remainder of all second-level two-character country code domain names.


View Documents
2016-04-25

National Association of Boards of PharmacyNo
philipstwView Comments
2015-10-14
2015-12-02View Mitigation

philips 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
plustwView Comments
2015-10-14
2015-12-02View Mitigation

plus Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
pnctwView Comments
2015-10-14
2015-12-02Yes
porntwView Comments
2015-10-14
2015-12-02View Mitigation

porn 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
primetwView Comments
2015-10-14
2015-12-02View Mitigation

prime 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
progressivetwView Comments
2015-10-14
2015-12-02No
protectiontwView Comments
2015-10-14
2015-12-02No
questtwView Comments
2015-10-14
2015-12-02No
rentwView Comments
2015-10-14
2015-12-02View Mitigation

ren Mitigation

By Beijing Qianxiang Wangjing Technology Development Co., Ltd.

.REN Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the domains with the following:
1. not be used to imply that it is, or represents, the government；
2. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, and provide a written report in response; and
3. in Registry Operator’s sole opinion, if misuse has occurred or been reported, the domain name 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.


View Documents
2016-04-25

Beijing Qianxiang Wangjing Technology Development Co., Ltd.No
ruhrtwView Comments
2015-10-14
2015-12-02View Mitigation

ruhr Mitigation

By regiodot GmbH & Co. KG

Proposed Measures to avoid confusion


View Documents
2016-04-20

regiodot GmbH & Co. KGNo
runtwView Comments
2015-10-14
2015-12-02View Mitigation

run Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
rwetwView Comments
2015-10-14
2015-12-02View Mitigation

rwe Mitigation

By RWE AG

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

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

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


2016-04-25

RWE AGYes
saarlandtwView Comments
2015-10-14
2015-12-02No
sandviktwView Comments
2015-10-14
2015-12-02View Mitigation

sandvik Mitigation

By Sandvik AB

.sandvik is a closed top-level domain name for the sole and exclusive use of Sandvik AB.

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


2016-04-11

Sandvik ABYes
sandvikcoromanttwView Comments
2015-10-14
2015-12-02View Mitigation

sandvikcoromant Mitigation

By Sandvik AB

.sandvikcoromant is a closed top-level domain name for the sole and exclusive use of Sandvik AB.

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


2016-04-11

Sandvik ABYes
sanofitwView Comments
2015-10-14
2015-12-02View 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
sastwView Comments
2015-10-14
2015-12-02View Mitigation

sas 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. DayYes
savetwView Comments
2015-10-14
2015-12-02View Mitigation

save 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
saxotwView Comments
2015-10-14
2015-12-02View Mitigation

saxo Mitigation

By Saxo Bank A/S

.saxo is a closed top-level domain name for the sole and exclusive use of Saxo Bank A/S.

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


2016-04-08

Saxo Bank A/S Yes
sbstwView Comments
2015-10-14
2015-12-02View Mitigation

sbs Mitigation

By SPECIAL BROADCASTING SERVICE CORPORATION

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


2016-04-22

SPECIAL BROADCASTING SERVICE CORPORATIONYes
schmidttwView Comments
2015-10-14
2015-12-02View Mitigation

schmidt Mitigation

By SALM S.A.S.

.schmidt is a closed top-level domain name for the sole and exclusive use of Salm S.A.S.

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


2016-04-25

SALM S.A.S.Yes
schooltwView Comments
2015-10-14
2015-12-02View Mitigation

school Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
scortwView Comments
2015-10-14
2015-12-02View Mitigation

scor Mitigation

By SCOR SE

.scor is a closed top-level domain name for the sole and exclusive use of Scor SE.

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


2016-04-13

SCOR SEYes
securetwView Comments
2015-10-14
2015-12-02View Mitigation

secure 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
securitytwView Comments
2015-10-14
2015-12-02No
senertwView Comments
2015-10-14
2015-12-02View Mitigation

sener Mitigation

By Sener Ingeniería y Sistemas, S.A.

Provide a brief explanation of the TLD:
Sener Ingeniería y Sistemas, S.A. has applied for .SENER to run a closed .brand environment.

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

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


2016-04-25

Sener Ingeniería y Sistemas, S.A.Yes
seventwView Comments
2015-10-14
2015-12-02View Mitigation

seven Mitigation

By Seven West Media Ltd

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


2016-04-27

Seven West Media LtdYes
sextwView Comments
2015-10-14
2015-12-02View Mitigation

sex 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
shelltwView Comments
2015-10-14
2015-12-02View Mitigation

shell Mitigation

By Shell Information Technology International Inc

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

Provide a brief explanation of the TLD:

.SHELL TLD is a closed Brand new gTLD operated by Shell Information Technology International Inc

Protections:

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

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

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


2016-04-05

Shell Information Technology International IncYes
showtwView Comments
2015-10-14
2015-12-02View Mitigation

show Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
silktwView Comments
2015-10-14
2015-12-02View Mitigation

silk 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
sitetwView Comments
2015-10-14
2015-12-02View Mitigation

site Mitigation

By Radix

Dear ICANN,

We are submitting these proposed measures to avoid confusion with specific country codes at the second level for each of our 8 TLDs, in relation to the individual Government objections that have been raised pertaining to the release of those specific two-character labels:

Protections

Radix understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:

1. Radix will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the relevant governments that have raised concerns about the release of specific two-character labels at the second level, and provide a written report in response; and

b. where, in Radix’s sole opinion, misuse has occurred, Radix will seek to work
with the sponsoring registrar and/or directly with the registrant to address the misuse.

c. In the event that misuse continues to occur, Radix may, in its sole discretion,
undertake direct action up to and including suspension or deletion of the domain name.

Thank you.


2016-04-25

RadixNo
skitwView Comments
2015-10-14
2015-12-02View Mitigation

ski Mitigation

By Starting Dot


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

The proposed measure can be found in the file attached.


View Documents
2016-04-25

Starting DotNo
soccertwView Comments
2015-10-14
2015-12-02View Mitigation

soccer Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
sohutwView Comments
2015-10-14
2015-12-02View Mitigation

sohu Mitigation

By Sohu.com Limited

.SOHU Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the domains with the following:
1. not be used to imply that it is, or represents, the government；
2. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, and provide a written report in response; and
3. in Registry Operator’s sole opinion, if misuse has occurred or been reported, the domain name 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.


View Documents
2016-04-25

Sohu.com LimitedNo
spreadbettingtwView Comments
2015-10-14
2015-12-02View Mitigation

spreadbetting Mitigation

By dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]

Please find attached a document which outlines the Registry's plans to avoid confusion in respect of the below TLDs:

.Markets
.Trading
.Forex
.Broker
.Spreadbetting
.CFD


View Documents
2016-04-21

dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]No
starhubtwView Comments
2015-10-14
2015-12-02Yes
stctwView Comments
2015-10-14
2015-12-02No
stcgrouptwView Comments
2015-10-14
2015-12-02No
storetwView Comments
2015-10-14
2015-12-02View Mitigation

store Mitigation

By Radix

Dear ICANN,

We are submitting these proposed measures to avoid confusion with specific country codes at the second level for each of our 8 TLDs, in relation to the individual Government objections that have been raised pertaining to the release of those specific two-character labels:

Protections

Radix understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:

1. Radix will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the relevant governments that have raised concerns about the release of specific two-character labels at the second level, and provide a written report in response; and

b. where, in Radix’s sole opinion, misuse has occurred, Radix will seek to work
with the sponsoring registrar and/or directly with the registrant to address the misuse.

c. In the event that misuse continues to occur, Radix may, in its sole discretion,
undertake direct action up to and including suspension or deletion of the domain name.

Thank you.


2016-04-25

RadixNo
studiotwView Comments
2015-10-14
2015-12-02View Mitigation

studio Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
swatchtwView Comments
2015-10-14
2015-12-02View Mitigation

swatch Mitigation

By The Swatch Group Ltd

Provide a brief explanation of the TLD:
The Swatch Group Ltd has applied for .SWATCH to run a closed .brand environment.

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

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


2016-04-25

The Swatch Group LtdNo
swisstwView Comments
2015-10-14
2015-12-02View Mitigation

swiss Mitigation

By Swiss Confederation

Proposed Measure to Avoid Confusion — Restrictive registration policy for 2-letter .SWISS domain names

Brief explanation of the TLD:
The purpose of the .SWISS TLD is to serve the Swiss community, defined as the community of individuals, legal entities and public institutions with a bona fide presence in Switzerland.
Registration of domain names under the .SWISS TLD is restricted to members of the Swiss community and subject to the further requirement that the domain name registrant’s presence in Switzerland and the registrant’s use of the domain name must comply with Swiss law.
The government of the Swiss Confederation acts as the central representative body for the Swiss community with regard to the .SWISS TLD, in consultation with the members of the Swiss community.
The measures described below address the confusion concerns cited by the governments of Anguilla, Singapore and St. Helena as well as by the Organization of African Union regarding the use of the 2-letter codes ai, sg, sh and au at the second-level of the .SWISS TLD. In the context of the .SWISS TLD, those 2-letter codes have the following meaning:
ai : official 2-letter acronym for the Swiss Canton Appenzell-Innerrhoden (see www.ai.ch)
sg : official 2-letter acronym for the Swiss Canton St-Gallen (see www.sg.ch)
sh : official 2-letter acronym for the Swiss Canton Schaffhausen (see www.sh.ch)
au : official name of the Swiss political municipality Au (see www.au.ch)

Protections:
The Swiss Confederation, as Registry Operator, has already implemented a community-based registrations policy for the .swiss TLD with particularly strict rules for all 2-letter codes. These rules were promulgated in the Federal Ordinance on Domain Names (https://www.admin.ch/opc/en/classified-compilation/20141744/index.html) and eliminate any risk of confusion. They comprise the following protections relevant to 2-letter codes:
• Each of the 26 Swiss Cantons has a single official 2-letter acronym. The Swiss Canton 2-letter acronyms are long-established, widely used and generally accepted. For instance, they appear on Swiss car license plates and are harmonized by ISO 3166-2 standard. Besides these acronyms, three Swiss political municipalities have a 2-letter name: Au, Gy and Lü.
• Only 2-letter codes matching with the official 2-letter acronym designating a Swiss Canton or matching with the official name of a Swiss political municipality will be released for registration in .SWISS.
• The 2-letter codes .SWISS domains are reserved exclusively for the respective Swiss cantonal governments, respectively for the executive council of the political municipality hence confusion due to misuse is not possible;
• A clear context specific to Switzerland is implicit with the .SWISS TLD and enforced by way of the registration policy, hence confusion with the ISO-3166 territory is not possible;
• The registration policy applying to 2-letter codes .SWISS domains is part of the Swiss legislation on domain names and published on Registry Operator’s homepage.

Process and eligibility considerations:
• The first-come-first-served principle is not applied for the allocation of .swiss domain names. As a principle, every allocation of domain name is based on an evaluation. Once a .swiss domain name application is submitted, the Registry will examine if the requested domain name is available and if the application meet the syntax rules and the general eligibility requirements set forth in the registration policy.
• The community-based eligibility and name selection criteria of the .swiss registration policy described above would also prevent the governments of Anguilla, Singapore and St. Helena as well as the Organization of African Union from registering 2-letter codes domains in the .SWISS TLD.


2016-04-21

Swiss ConfederationNo
sydneytwView Comments
2015-10-14
2015-12-02View Mitigation

sydney Mitigation

By State of NSW, Department of Premier and Cabinet

Proposed Measure to Avoid Confusion

A brief explanation of the TLD:
.sydney is a geographic TLD for the city of Sydney, Australia and the State Government of New South Wales is the designated ‘Registry Operator’. While .sydney is an open TLD, registration of domain names is limited to New South Wales residents and businesses, and other entities with an interest in the state of New South Wales, Australia as described in the Registration Policy.

The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ai, bh, bm, ci, cn, eg, hk, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw

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 the government 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 Acceptable Use Policy for the .sydney TLD is the following text:

“…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 Acceptable Use Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-21

State of NSW, Department of Premier and CabinetNo
tabtwView Comments
2015-10-14
2015-12-02View Mitigation

tab Mitigation

By Tabcorp Holdings Limited

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


2016-04-22

Tabcorp Holdings LimitedYes
taipeitwView Comments
2015-10-14
2015-12-02No
tatamotorstwView Comments
2015-10-14
2015-12-02View Mitigation

tatamotors Mitigation

By Tata Motors Ltd

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

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

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


2016-04-25

Tata Motors LtdYes
taxtwView Comments
2015-10-14
2015-12-02View Mitigation

tax Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
taxitwView Comments
2015-10-14
2015-12-02View Mitigation

taxi Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
teamtwView Comments
2015-10-14
2015-12-02View Mitigation

team Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
techtwView Comments
2015-10-14
2015-12-02View Mitigation

tech Mitigation

By Radix

Dear ICANN,

We are submitting these proposed measures to avoid confusion with specific country codes at the second level for each of our 8 TLDs, in relation to the individual Government objections that have been raised pertaining to the release of those specific two-character labels:

Protections

Radix understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following:

1. Radix will commit to:

a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the relevant governments that have raised concerns about the release of specific two-character labels at the second level, and provide a written report in response; and

b. where, in Radix’s sole opinion, misuse has occurred, Radix will seek to work
with the sponsoring registrar and/or directly with the registrant to address the misuse.

c. In the event that misuse continues to occur, Radix may, in its sole discretion,
undertake direct action up to and including suspension or deletion of the domain name.

Thank you.


2016-04-25

RadixNo
tevatwView Comments
2015-10-14
2015-12-02View Mitigation

teva Mitigation

By Teva Pharmaceutical Industries Limited

.TEVA TLD is a closed Brand new gTLD operated by Teva Pharmaceutical Industries Limited

Protections:

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

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

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


2016-04-04

Teva Pharmaceutical Industries LimitedYes
theatertwView Comments
2015-10-14
2015-12-02View Mitigation

theater Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
theatretwView Comments
2015-10-14
2015-12-02No
tiroltwView Comments
2015-10-14
2015-12-02View Mitigation

tirol Mitigation

By punkt Tirol GmbH







.tirol Mitigation Measures to avoid confusion with specific Country codes


Please find attached the measures to avoid confusion for 2-letter SLDs that correspond with country codes of the .tirol TLD.


View Documents
2016-04-12

View Mitigation

tirol Mitigation

By punkt Tirol GmbH

Please find our measures to avoid confusion for 2-letter SLDs corresponding with country codes in the attached PDF document. The document refers to the domains: ac.tirol; bm.tirol; gb.tirol; gi.tirol; hk.tirol; il.tirol; in.tirol; io.tirol; it.tirol; kr.tirol; ky.tirol; ms.tirol; ng.tirol; pt.tirol; ru.tirol; sg.tirol; sh.tirol; su.tirol; tc.tirol; tw.tirol; uk.tirol; vn.Tirol
Best regards, .tirol Team


View Documents
2016-04-19

punkt Tirol GmbHNo
tokyotwView Comments
2015-10-14
2015-12-02View Mitigation

tokyo Mitigation

By GMO Registry

Mitigation Plan for .tokyo

About .tokyo

.tokyo is a GeoTLD for the city of Tokyo, Japan, operated by GMO Registry, Inc. (the “Registry Operator”) with the support of the Tokyo Metropolitan Government.
The purpose of .tokyo is to promote .tokyo 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, .tokyo 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 .tokyo 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 .TOKYO 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
tourstwView Comments
2015-10-14
2015-12-02View Mitigation

tours Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
towntwView Comments
2015-10-14
2015-12-02View Mitigation

town Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
tradingtwView Comments
2015-10-14
2015-12-02View Mitigation

trading Mitigation

By dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]

Please find attached a document which outlines the Registry's plans to avoid confusion in respect of the below TLDs:

.Markets
.Trading
.Forex
.Broker
.Spreadbetting
.CFD


View Documents
2016-04-21

dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]No
trusttwView Comments
2015-10-14
2015-12-02No
ubstwView Comments
2015-10-14
2015-12-02Yes
vegastwView Comments
2015-10-14
2015-12-02No
vigtwView Comments
2015-10-14
2015-12-02View Mitigation

vig Mitigation

By VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe

.VIG is a closed top-level domain name for the sole and exclusive use of VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe

Use of .VIG at the second level VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe as the Registry Operator for the .VIG TLD, VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe have selected the label .VIG to be reserved for registry operations as described in Section 3.2 of Specification 5 of our Registry Agreement. The domain name .VIG will be used exclusively by us for the promotion of the TLD, and we will act as the Registrant of the domain name. Protections Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. The domain name .VIG will:
a. be used exclusively by VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe to support and assist the promotion of its registry operations;
b. not be used to imply that it is, or represents, government of the corresponding Country Code; and
c. not be used to imply the government’s approval of Registry Operator’s operations or activities.

2. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of corresponding Country Code, and provide a written report in response; and
b. where, in VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe’s sole opinion, misuse has occurred, VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe 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, VIENNA INSURANCE GROUP AG Wiener Versicherung Gruppe may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-21

VIENNA INSURANCE GROUP AG Wiener Versicherung GruppeNo
vintwView Comments
2015-10-14
2015-12-02View Mitigation

vin Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
vistatwView Comments
2015-10-14
2015-12-02View Mitigation

vista Mitigation

By Vistaprint Limited

.vista is a closed top-level domain name for the sole and exclusive use of VISTAPRINT LIMITED.

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


2016-04-14

Vistaprint LimitedNo
vistaprinttwView Comments
2015-10-14
2015-12-02View Mitigation

vistaprint Mitigation

By Vistaprint Limited

.vistaprint is a closed top-level domain name for the sole and exclusive use of VISTAPRINT LIMITED.

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


2016-04-14

Vistaprint LimitedNo
vivatwView Comments
2015-10-14
2015-12-02No
waltertwView Comments
2015-10-14
2015-12-02View Mitigation

walter Mitigation

By Sandvik AB

.walter is a closed top-level domain name for the sole and exclusive use of Sandvik AB.

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


2016-04-11

Sandvik ABYes
wientwView Comments
2015-10-14
2015-12-02View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond with country codes - this is the document for .CI

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond with country codes - this is the document for .EG

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond with country codes - this is the document for .HK

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond with country codes - this is the document for .IL

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond with country codes - this is the document for .IN

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond to country codes - this is the document for .IT

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond to country codes - this is the document for .ME

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond to country codes - this is the document for .TW

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond to country codes - this is the document for .CN

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond to country codes - this is the document for .PT

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond to country codes - this is the document for .SG

best regards
Ronald


View Documents
2016-04-12

View Mitigation

wien Mitigation

By punkt.wien GmbH

Hello

please find attached our measures to avoid confusion for 2-letter SLDs that correspond with country codes (applicable to all 2-letter cc-SLDs)

best regards
Ronald


View Documents
2016-04-15

punkt.wien GmbHNo
winetwView Comments
2015-10-14
2015-12-02View Mitigation

wine Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
wmetwView Comments
2015-10-14
2015-12-02Yes
woodsidetwView Comments
2015-10-14
2015-12-02View Mitigation

woodside Mitigation

By Woodside Energy ltd

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


2016-04-22

Woodside Energy ltdYes
xn--czr694btwView Comments
2015-10-14
2015-12-02View 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--g2xx48ctwView Comments
2015-10-14
2015-12-02View 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--kcrx77d1x4atwView Comments
2015-10-14
2015-12-02View 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--ngbe9e0atwView Comments
2015-10-14
2015-12-02No
xn--ses554gtwView Comments
2015-10-14
2015-12-02No
xn--vuq861btwView Comments
2015-10-14
2015-12-02No
xn--w4r85el8fhu5dnratwView Comments
2015-10-14
2015-12-02No
xn--w4rs40ltwView Comments
2015-10-14
2015-12-02Yes
xperiatwView Comments
2015-10-14
2015-12-02View 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
xxxtwView Comments
2015-10-14
2015-12-02View 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
xyztwView Comments
2015-10-14
2015-12-02No
yokohamatwView Comments
2015-10-14
2015-12-02View 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
zappostwView Comments
2015-10-14
2015-12-02View 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
zuerichtwView Comments
2015-10-14
2015-12-02No

tw Comments

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

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

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

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

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