About ICANN
- Academic Engagement
- Acronyms and Terms
- Courses and Learning
- ICANN for Beginners
- Participate
- President's Corner
- ICANN Management Organization Chart
- Staff
- Careers
- In Focus
- Media Resources
Board Activities and Meetings
Accountability
- Accountability Mechanisms
- Reviews
  - Organizational Reviews
  - Specific Reviews
- Expected Standards of Behavior
- Employee Practices and Resources
- Enhancing ICANN Accountability – Work Stream 2 Implementation
Governance
- Governance Documents
- Evolving ICANN’s Multistakeholder Model
- Agreements
- Annual Reports
- Financials
- Planning
  - Strategic Plan
  - Operating Plan
- Presentations
- RFPs
- Litigation
- Newsletter
- Correspondence
  - 2026
  - 2025
  - 2024
  - 2023
  - 2022
  - 2021
  - 2020
  - 2019
  - 2018
  - 2017
  - 2016
  - 2015
  - 2014
  - 2013
  - 2012
  - 2011
  - 2010
  - 2009
  - 2008
  - 2007
  - 2006
  - 2005
  - 2004
  - 2003
  - 2002
  - 2001
  - 2000
  - 1999
  - 1998
- Quarterly Reports
Groups
- 2023 ICANN CEO Search Committee
- RSSAC
  - Charter
- SSAC
- GAC
- At-Large
- ASO
- ccNSO
- GNSO
- Technical Liaison Group
  - Technical Experts Group (TEG)
- NomCom
  - Past NomComs
- Customer Standing Committee
- Root Zone Evaluation Review Committee (RZERC)
Business
Civil Society
Complaints Office
- Complaints Report
Domain Name System Abuse
Contractual Compliance
- About
- Enforcement of DNS Abuse Obligations
- Formal Enforcement Notices
  - Archive
- Contractual Compliance Metrics
- Blogs
- Contractual Compliance Audit Program
- Notice of Bankruptcy, Convictions and Security Breaches
- Contractual Compliance Reports
- gTLD Registry Compliance
- Accredited Registrar Compliance
- General Questions
- Outreach
Contracted Parties (Registry Operators and Accredited Registrars)
Domain Name Registrants
- About Domain Names
- ICANN Policies
- Registration Data Policies
  - WHOIS and Registration Data Directory Services
    - The Domain Name Registration Process
      - Using Domain Name Registration Data
      - Keeping Registration Data Accurate
    - Access and the Evolution of the WHOIS System
- Domain Name Industry
- Registering Domain Names
- Managing Domain Names
  - Contact Information and WDRP
  - Securely Managing Your Domain Name
- Transferring Domain Names
- Renewing Domain Names
- Rights and Responsibilities
- Spam, Phishing, and Website Content
- Trademark Infringement
GDS Metrics
Identifier Systems Security, Stability and Resiliency (OCTO-SSR)
ccTLDs
- Background Materials
- Agreements
- Delegation
- Root Zone Database
- Model MOU
- Workshops
- ICANN and ISO
Internationalized Domain Names
- Root Zone Label Generation Rules (LGR)
- IDN Variant TLD Implementation
- LGR Toolset
- IDN ccTLD Fast Track
- IDN Implementation Guidelines
- Second-Level LGR Reference
- Resources
- Announcements and Blogs Posts
New gTLD Program
Universal Acceptance Initiative
- Make your systems UA-ready
- UA Training
- UA Day
- UA Readiness Evaluations
- UA Initiatives
- Announcements and Blogs Posts
Policy
- Policy Mission
- Policy Staff Goals
- Presentations
- Global Addressing
- Policy Updates
Operational Design Phase (ODP)
Implementation
Public Comment
- Open
- Upcoming
- Archive
Root Zone KSK Rollover
Technical Functions
- Tech Day Archive
ICANN Locations
- Report Security Issues
- PGP Keys
- Certificate Authority
- Registry Liaison
- Ombudsman
I Need Help
- Dispute Resolution
- Domain Name Dispute Resolution
- Name Collision
- Registrar Problems
- Whois Data Correction
- Independent Review Process
- Request for Reconsideration
- Document

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.

TLDs

RO Names

TLD	Two Characters	Comments from Government	Last updated	RO Mitigation Plan	RO Name	BRAND TLD
town	ng	View Comments 2015-12-04	2015-12-05	View Mitigation town Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
toys	ng	View Comments 2015-12-04	2015-12-05	View Mitigation toys Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
trade	ng	View Comments 2015-12-04	2015-12-05	View Mitigation trade Mitigation By Famous Four Media Limited By Famous Four media Limited. Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants. 3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	Famous Four Media Limited	No
trading	ng	View Comments 2015-12-04	2015-12-05	View 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
training	ng	View Comments 2015-12-04	2015-12-05	View Mitigation training Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
travelers	ng	View Comments 2015-12-04	2015-12-05			Yes
travelersinsurance	ng	View Comments 2015-12-04	2015-12-05			No
trust	ng	View Comments 2015-12-04	2015-12-05			No
trv	ng	View Comments 2015-12-04	2015-12-05			No
tui	ng	View Comments 2015-12-04	2015-12-05	View Mitigation tui Mitigation By TUI AG Please find TUI AG's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.TUI” TLD attached. View Documents 2016-04-25	TUI AG	Yes
tunes	ng	View Comments 2015-12-04	2015-12-05	View Mitigation tunes 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
tushu	ng	View Comments 2015-12-04	2015-12-05	View Mitigation tushu 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
ubs	ng	View Comments 2015-12-04	2015-12-05			Yes
university	ng	View Comments 2015-12-04	2015-12-05	View Mitigation university Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
uno	ng	View Comments 2015-12-04	2015-12-05			No
uol	ng	View Comments 2015-12-04	2015-12-05	View Mitigation uol Mitigation By UBN Internet Ltda. .uol is a brand TLD for the UOL online brand owned by Universo Online S/A. UBN INTERNET Ltda. [UBN], a subsidiary of Universo Online S/A, for the .uol gTLD[TLD], has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the [UBN] will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .uol is identical to a qualifying registered trademark; 2. .[uol] is not a Generic String, as defined in Specification 11; 3. .uol TLD has developed and implemented a closed registration policy for .uol that requires that all domain names in .uol to be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .uol TLD will keep a published registration policy, already available at http://nic.uol; 5. .uol will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .uol TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .uol is a proprietary space in which all second-level domains in the TLD are being operated by [UBN], its Affiliates and Trademark Licensees and not any government or the corresponding country code operator. By this plan [UBN] confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-22	UBN Internet Ltda.	Yes
vacations	ng	View Comments 2015-12-04	2015-12-05	View Mitigation vacations Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
vegas	ng	View Comments 2015-12-04	2015-12-05			No
ventures	ng	View Comments 2015-12-04	2015-12-05	View Mitigation ventures Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
versicherung	ng	View Comments 2015-12-04	2015-12-05			No
vet	ng	View Comments 2015-12-04	2015-12-05	View Mitigation vet Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
viajes	ng	View Comments 2015-12-04	2015-12-05	View Mitigation viajes Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
video	ng	View Comments 2015-12-04	2015-12-05	View Mitigation video Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
vig	ng	View Comments 2015-12-04	2015-12-05	View 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 Gruppe	No
villas	ng	View Comments 2015-12-04	2015-12-05	View Mitigation villas Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
vin	ng	View Comments 2015-12-04	2015-12-05	View Mitigation vin Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
vip	ng	View Comments 2015-12-04	2015-12-05	View Mitigation vip 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 GmbH	No
vision	ng	View Comments 2015-12-04	2015-12-05	View Mitigation vision Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
vista	ng	View Comments 2015-12-04	2015-12-05	View 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 Limited	No
vistaprint	ng	View Comments 2015-12-04	2015-12-05	View 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 Limited	No
viva	ng	View Comments 2015-12-04	2015-12-05			No
vodka	ng	View Comments 2015-12-04	2015-12-05	View Mitigation vodka 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 GmbH	No
volkswagen	ng	View Comments 2015-12-04	2015-12-05	View Mitigation volkswagen Mitigation By Volkswagen Group of America Inc. .volkswagen is a closed Brand TLD for the sole and exclusive use of Volkswagen Group of America Inc. Protections Volkswagen Group of America Inc. (Registry Operator) for the .volkswagen TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: .volkswagen is identical to a qualifying registered trademark; .volkswagen is not a Generic String, as this is defined in Specification 11; Registry Operator has developed and implemented a closed registration policy for .volkswagen that requires that all domain names in the .volkswagen TLD be registered only by Volkswagen Group of America Inc., its Affiliates, and its Trademark Licensees. As required under the Registry Agreement, the Registry Operator published this registration policy on its website. Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .volkswagen TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators. By this submission Volkswagen Group of America Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-21	Volkswagen Group of America Inc.	Yes
vote	ng	View Comments 2015-12-04	2015-12-05			No
voto	ng	View Comments 2015-12-04	2015-12-05			No
voyage	ng	View Comments 2015-12-04	2015-12-05	View Mitigation voyage Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
walter	ng	View Comments 2015-12-04	2015-12-05	View 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 AB	Yes
wang	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wang Mitigation By Zodiac Registry This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs: Registry Operator TLD English translation Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王" Zodiac Aquarius Limited .商城 (xn--czru2d) .mall Zodiac Taurus Limited .网店(xn--hxt814e) .web store Zodiac Gemini Limited .八卦(xn--45q11c) .gossip All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country. As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise. Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion. Protections 1. Registry Operator will commit to: a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use: “Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law” … “Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion: a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;” Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term: “Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.” This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted. 2016-04-22	Zodiac Registry	No
wanggou	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wanggou 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
warman	ng	View Comments 2015-12-04	2015-12-05	View Mitigation warman Mitigation By Weir Group IP Limited Provide a brief explanation of the TLD: Weir Group IP Limited has applied for .WARMAN to run a closed .brand environment. Protections Weir Group IP Limited for the .WARMAN TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Weir Group IP Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .WARMAN is identical to a qualifying registered trademark; 2. .WARMAN is not a Generic String, as this is defined in Specification 11; 3. .WARMAN TLD has developed and will implement a closed registration policy for .WARMAN that requires that all domain names in the .WARMAN TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .WARMAN TLD will clearly publish this registration policy; 5. .WARMAN TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .WARMAN TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WARMAN TLD is a proprietary space in which all second-level domains in the TLD are being operated by Weir Group IP Limited, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter Weir Group IP Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	Weir Group IP Limited	Yes
watch	ng	View Comments 2015-12-04	2015-12-05	View Mitigation watch Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
webcam	ng	View Comments 2015-12-04	2015-12-05	View Mitigation webcam Mitigation By Famous Four Media Limited By Famous Four media Limited. Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants. 3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	Famous Four Media Limited	No
website	ng	View Comments 2015-12-04	2015-12-05	View Mitigation website 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	Radix	No
wedding	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wedding 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 GmbH	No
weir	ng	View Comments 2015-12-04	2015-12-05	View Mitigation weir Mitigation By Weir Group IP Limited Provide a brief explanation of the TLD: Weir Group IP Limited has applied for .WEIR to run a closed .brand environment. Protections Weir Group IP Limited for the .WEIR TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Weir Group IP Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .WEIR is identical to a qualifying registered trademark; 2. .WEIR is not a Generic String, as this is defined in Specification 11; 3. .WEIR TLD has developed and will implement a closed registration policy for .WEIR that requires that all domain names in the .WEIR TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .WEIR TLD will clearly publish this registration policy; 5. .WEIR TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .WEIR TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WEIR TLD is a proprietary space in which all second-level domains in the TLD are being operated by Weir Group IP Limited, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter Weir Group IP Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	Weir Group IP Limited	Yes
whoswho	ng	View Comments 2015-12-04	2015-12-05			No
wien	ng	View Comments 2015-12-04	2015-12-05	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 .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 GmbH	No
wiki	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wiki Mitigation By Top Level Design LLC The .wiki measures for the avoidance of confusion pertain to the following letter/letter labels: ci, cn, eg, il, in, and me. Top Level Design LLC is the Registry Operator for .wiki, an open, generic TLD that resonates with a wide variety of industries and topics. Top Level Design LLC understands the concern that confusion may arise and is willing to offer the following: 1. Top Level Design LLC will commit to: a. Investigate any reports of misuse, including misleading or deceptive conduct, from relevant governments (including Ivory Coast, China, Egypt, Israel, India, and Montenegro), and provide a written report in response. b. Where, in the Registry Operator’s sole opinion, misuse has occurred, the 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, in accordance with its Acceptable Use Policy. 2016-04-25	Top Level Design LLC	No
win	ng	View Comments 2015-12-04	2015-12-05	View Mitigation win Mitigation By Famous Four Media Limited By Famous Four media Limited. Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants. 3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	Famous Four Media Limited	No
windows	ng	View Comments 2015-12-04	2015-12-05	View Mitigation windows Mitigation By Microsoft Corporation Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: .WINDOWS TLD is a closed Brand new gTLD operated by Microsoft Corporation Protections: Microsoft Corporation for the .WINDOWS TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Microsoft Corporation will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .WINDOWS is identical to a qualifying registered trademark; 2. .WINDOWS is not a Generic String, as this is defined in Specification 11; 3. .WINDOWS TLD has developed and will implement a closed registration policy for .WINDOWS that requires that all domain names in the .WINDOWS TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .WINDOWS TLD will clearly publish this registration policy; 5. .WINDOWS TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .WINDOWS TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .WINDOWS TLD is a proprietary space in which all second-level domains in the TLD are being operated by Microsoft Corporation, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Microsoft Corporation confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-05	Microsoft Corporation	Yes
wine	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wine Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
wme	ng	View Comments 2015-12-04	2015-12-05			Yes
woodside	ng	View Comments 2015-12-04	2015-12-05	View 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 ltd	Yes
work	ng	View Comments 2015-12-04	2015-12-05	View Mitigation work 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 GmbH	No
works	ng	View Comments 2015-12-04	2015-12-05	View Mitigation works Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
world	ng	View Comments 2015-12-04	2015-12-05	View Mitigation world Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
wow	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wow Mitigation By Amazon Registry Services, Inc. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .WOW TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code: a. the use in the .WOW TLD of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the .WOW TLD will require registrants of a domain name in the .WOW TLD to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
wtf	ng	View Comments 2015-12-04	2015-12-05	View Mitigation wtf Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xbox	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xbox Mitigation By Microsoft Corporation Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: .XBOX TLD is a closed Brand new gTLD operated by Microsoft Corporation Protections: Microsoft Corporation for the .XBOX TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Microsoft Corporation will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .XBOX is identical to a qualifying registered trademark; 2. .XBOX is not a Generic String, as this is defined in Specification 11; 3. .XBOX TLD has developed and will implement a closed registration policy for .XBOX that requires that all domain names in the .XBOX TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .XBOX TLD will clearly publish this registration policy; 5. .XBOX TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .XBOX TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .XBOX TLD is a proprietary space in which all second-level domains in the TLD are being operated by Microsoft Corporation, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Microsoft Corporation confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-05	Microsoft Corporation	Yes
xerox	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xerox Mitigation By Xerox DNHC LLC .XEROX gTLD Confusion Avoidance Plan Xerox DNHC LLC, the Registry Operator for the .XEROX gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Xerox DNHC LLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .XEROX is identical to a qualifying registered trademark; 2. .XEROX is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Xerox DNHC LLC has developed and will implement a closed registration policy for .XEROX that requires that all domain names in the .XEROX gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Xerox DNHC LLC submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .XEROX will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .XEROX gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .XEROX gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Xerox DNHC LLC, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Xerox DNHC LLC confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-21	Xerox DNHC LLC	Yes
xin	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xin Mitigation By Elegant Leader Limited A Proposal to Minimize the Potential Likelihood of Confusion in Connection with the Allocation of Specific Two Character Domain Names The .XIN gTLD wishes to help establish a trusted and reliable namespace for the Chinese market. Protections Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct involving a two character domain name associated with the corresponding government and provide a written report in response b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. Furthermore, contained within our Acceptable Use Policy for the .XIN TLD is the following text: “Registry operator reserves the right at its sole discretion to deny, cancel, or transfer any registration or transaction, or place any domain name(s) on registry lock, hold, or similar status, that it deems necessary: (1) to protect the integrity and stability of the registry; (2) to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process; (3) to avoid any liability, civil or criminal, on the part of registry operator, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) per the terms of the registration agreement and this Anti-Abuse Policy, or (5) to correct mistakes made by registry operator or any registrar in connection with a domain name registration. Registry operator also reserves the right to place upon registry lock, hold, or similar status a domain name during resolution of a dispute. View Documents 2016-04-25	Elegant Leader Limited	No
xn--1ck2e1b	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--1ck2e1b Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--3bst00m	ng	View Comments 2015-12-04	2015-12-05			No
xn--3ds443g	ng	View Comments 2015-12-04	2015-12-05			No
xn--3oq18vl8pn36a	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--3oq18vl8pn36a Mitigation By Volkswagen (China) Investment Co., Ltd. .大众汽车 is a closed Brand TLD for the sole and exclusive use of Volkswagen (China) Investment Co., Ltd. Protections Volkswagen (China) Investment Co., Ltd. (Registry Operator) for the .大众汽车 TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: .大众汽车 is identical to a qualifying registered trademark; .大众汽车 is not a Generic String, as this is defined in Specification 11; Registry Operator has developed and will implement a closed registration policy for .大众汽车 that requires that all domain names in the .大众汽车 TLD be registered only by Volkswagen (China) Investment Co., Ltd., its Affiliates, and its Trademark Licensees. As required under the Registry Agreement, the Registry Operator will publish this registration policy on its website. Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .大众汽车 TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators. By this submission Volkswagen (China) Investment Co., Ltd. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-21	Volkswagen (China) Investment Co., Ltd.	Yes
xn--45q11c	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--45q11c Mitigation By Zodiac Registry This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs: Registry Operator TLD English translation Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王" Zodiac Aquarius Limited .商城 (xn--czru2d) .mall Zodiac Taurus Limited .网店(xn--hxt814e) .web store Zodiac Gemini Limited .八卦(xn--45q11c) .gossip All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country. As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise. Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion. Protections 1. Registry Operator will commit to: a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use: “Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law” … “Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion: a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;” Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term: “Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.” This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted. 2016-04-22	Zodiac Registry	No
xn--55qx5d	ng	View Comments 2015-12-04	2015-12-05			No
xn--6frz82g	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--6frz82g Mitigation By Afilias Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion. 2016-04-20	Afilias	No
xn--6qq986b3xl	ng	View Comments 2015-12-04	2015-12-05			No
xn--bck1b9a5dre4c	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--bck1b9a5dre4c Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--cck2b3b	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--cck2b3b Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--czr694b	ng	View Comments 2015-12-04	2015-12-05	View 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 LIMITED	No
xn--czrs0t	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--czrs0t Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--czru2d	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--czru2d Mitigation By Zodiac Registry This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs: Registry Operator TLD English translation Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王" Zodiac Aquarius Limited .商城 (xn--czru2d) .mall Zodiac Taurus Limited .网店(xn--hxt814e) .web store Zodiac Gemini Limited .八卦(xn--45q11c) .gossip All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country. As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise. Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion. Protections 1. Registry Operator will commit to: a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use: “Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law” … “Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion: a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;” Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term: “Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.” This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted. 2016-04-22	Zodiac Registry	No
xn--eckvdtc9d	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--eckvdtc9d Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--fct429k	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--fct429k Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--fiq228c5hs	ng	View Comments 2015-12-04	2015-12-05			No
xn--fiq64b	ng	View Comments 2015-12-04	2015-12-05			No
xn--fjq720a	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--fjq720a Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--g2xx48c	ng	View Comments 2015-12-04	2015-12-05	View 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 GmbH	No
xn--gckr3f0f	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--gckr3f0f Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--gk3at1e	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--gk3at1e Mitigation By Amazon Registry Services, Inc. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .xn--gk3at1e TLD, proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, and vn. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, gb, gi, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, tw, uk, or vn) corresponds to its country code: a. the use in the .xn--gk3at1e TLD of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the .xn--gk3at1e TLD will require registrants of a domain name in the .xn--gk3at1e TLD to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--hxt814e	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--hxt814e Mitigation By Zodiac Registry This “Proposed Measure to Avoid Confusion” is submitted to ICANN on behalf of the Registry Operator of the following TLDs: Registry Operator TLD English translation Zodiac Wang Limited .wang “web” or “net” or the Chinese surname "王" Zodiac Aquarius Limited .商城 (xn--czru2d) .mall Zodiac Taurus Limited .网店(xn--hxt814e) .web store Zodiac Gemini Limited .八卦(xn--45q11c) .gossip All four TLDs are Chinese IDNs, except .wang (a Chinese pinyin). All these TLDs have applied for and three of them have received approval from the Ministry of Industry and Information Technology (MIIT) of China to operate within the country. As these TLDs are intended for the millions of the Chinese-speaking Internet users and the way in which pinyin (the official phonetic system for transcribing Chinese characters into Latin alphabet) works, we believe it is extremely unlikely that confusion with corresponding country codes will arise. Nevertheless, we understand the concerns expressed by governments or ccTLD Managers and set out the protections below that are already in place or to be implemented by Registry Operator, to avoid confusion. Protections 1. Registry Operator will commit to: a. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, including those from the relevant government or ccTLD Manager, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. The Registry Operator’s Anti-Abuse Policy contains the following text that prohibits abusive use and provides consequences for abusive use: “Registry Operator expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law” … “Registry Operator reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion: a. to enforce any Registry Policies (http://en.zodiac.wang/policy.html, including this policy) and ICANN requirements, as amended from time to time;” Further, the Registry-Registrar Agreements of all these TLDs require registrars to enter a registration agreement with each Registered Name Holder (“RNH Registration Agreement”) and such agreement must include the following term: “Registered Name Holder must comply with all Registry Policies (http://en.zodiac.wang/policy.html), as if they were incorporated into, and form part of the RNH Registration Agreement. In the event of any inconsistency between any Registry Policy and the RNH Registration Agreement, then that Registry Policy will prevail to the extent of such inconsistency.” This mandatory term in the RNH Registration Agreement means registrants in the above TLDs are bound by the Registry’s Anti-Abuse Policy. Thus, if a registrant’s use of a two-character domain name amounts to misuse or abusive use, the domain name may be cancelled, locked, placed on hold, transferred or deleted. 2016-04-22	Zodiac Registry	No
xn--io0a7i	ng	View Comments 2015-12-04	2015-12-05			No
xn--jvr189m	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--jvr189m Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .xn--gckr3f0f, .xn--fct429k, .xn--bck1b9a5dre4c, .xn--jvr189m, .xn--eckvdtc9d, .xn--1ck2e1b, .xn--cck2b3b, .YOU, and .ZERO. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--kcrx77d1x4a	ng	View Comments 2015-12-04	2015-12-05	View 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--ngbe9e0a	ng	View Comments 2015-12-04	2015-12-05			No
xn--q9jyb4c	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--q9jyb4c Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	No
xn--rovu88b	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--rovu88b Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
xn--ses554g	ng	View Comments 2015-12-04	2015-12-05			No
xn--unup4y	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--unup4y Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--vermgensberater-ctb	ng	View Comments 2015-12-04	2015-12-05			No
xn--vermgensberatung-pwb	ng	View Comments 2015-12-04	2015-12-05			No
xn--vhquv	ng	View Comments 2015-12-04	2015-12-05	View Mitigation xn--vhquv Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--vuq861b	ng	View Comments 2015-12-04	2015-12-05			No
xn--w4r85el8fhu5dnra	ng	View Comments 2015-12-04	2015-12-05			No
xn--w4rs40l	ng	View Comments 2015-12-04	2015-12-05			Yes
xperia	ng	View Comments 2015-12-04	2015-12-05	View 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 AB	Yes
xxx	ng	View Comments 2015-12-04	2015-12-05	View 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
xyz	ng	View Comments 2015-12-04	2015-12-05			No

ng Comments

By Nkiru Ebenmelu, GAC Rep, Nigerian Communications Commission

Nigeria does not support the release of Two-Character ASCII Labels ".ng" or the use of "NIGERIA", in the context of any/all of the gTLD(s) at the second level. This should apply to all current and future requests. It is against Nigerian law and strictly prohibited to use the word "Nigeria" or code representing Nigeria without proper authorization by the Government. This assists the Country forestall the abuse and misuse of reserved names associated with the Government; the release would be a breach of our laws. We also wish to inform you that Nigeria reserves the right of authorization for use of “NGR” and “NGA”. As these are also reserved for use by Nigeria. (ISO 3166). We will appreciate it if we are informed of the decision(s) taken.

Two-Character Letter/Letter Label Comments and Mitigation Measures

town Mitigation

toys Mitigation

trade Mitigation

trading Mitigation

training Mitigation

tui Mitigation

tunes Mitigation

tushu Mitigation

university Mitigation

uol Mitigation

vacations Mitigation

ventures Mitigation

vet Mitigation

viajes Mitigation

video Mitigation

vig Mitigation

villas Mitigation

vin Mitigation

vip Mitigation

vision Mitigation

vista Mitigation

vistaprint Mitigation

vodka Mitigation

volkswagen Mitigation

voyage Mitigation

walter Mitigation

wang Mitigation

wanggou Mitigation

warman Mitigation

watch Mitigation

webcam Mitigation

website Mitigation

wedding Mitigation

weir Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wien Mitigation

wiki Mitigation

win Mitigation

windows Mitigation

wine Mitigation

woodside Mitigation

work Mitigation

works Mitigation

world Mitigation

wow Mitigation

wtf Mitigation

xbox Mitigation

xerox Mitigation

xin Mitigation

xn--1ck2e1b Mitigation

xn--3oq18vl8pn36a Mitigation

xn--45q11c Mitigation

xn--6frz82g Mitigation

xn--bck1b9a5dre4c Mitigation

xn--cck2b3b Mitigation

xn--czr694b Mitigation

xn--czrs0t Mitigation

xn--czru2d Mitigation

xn--eckvdtc9d Mitigation

xn--fct429k Mitigation

xn--fjq720a Mitigation

xn--g2xx48c Mitigation

xn--gckr3f0f Mitigation

xn--gk3at1e Mitigation

xn--hxt814e Mitigation

xn--jvr189m Mitigation

xn--kcrx77d1x4a Mitigation

xn--q9jyb4c Mitigation

xn--rovu88b Mitigation