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
webcam	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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
whoswho	gs	View Comments 2015-12-02	2015-12-02			No
wien	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	View Mitigation wine Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
wme	gs	View Comments 2015-12-02	2015-12-02			Yes
woodside	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	View Mitigation works Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
world	gs	View Comments 2015-12-02	2015-12-02	View Mitigation world Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
wow	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	View Mitigation wtf Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xbox	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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--3ds443g	gs	View Comments 2015-12-02	2015-12-02			No
xn--3oq18vl8pn36a	gs	View Comments 2015-12-02	2015-12-02	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--55qx5d	gs	View Comments 2015-12-02	2015-12-02			No
xn--czr694b	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	View Mitigation xn--czrs0t Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--czru2d	gs	View Comments 2015-12-02	2015-12-02	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--fiq228c5hs	gs	View Comments 2015-12-02	2015-12-02			No
xn--fjq720a	gs	View Comments 2015-12-02	2015-12-02	View Mitigation xn--fjq720a Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--g2xx48c	gs	View Comments 2015-12-02	2015-12-02	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--gk3at1e	gs	View Comments 2015-12-02	2015-12-02	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--io0a7i	gs	View Comments 2015-12-02	2015-12-02			No
xn--kcrx77d1x4a	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02			No
xn--ses554g	gs	View Comments 2015-12-02	2015-12-02			No
xn--unup4y	gs	View Comments 2015-12-02	2015-12-02	View Mitigation xn--unup4y Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--vermgensberater-ctb	gs	View Comments 2015-12-02	2015-12-02			No
xn--vermgensberatung-pwb	gs	View Comments 2015-12-02	2015-12-02			No
xn--vhquv	gs	View Comments 2015-12-02	2015-12-02	View Mitigation xn--vhquv Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
xn--vuq861b	gs	View Comments 2015-12-02	2015-12-02			No
xn--w4r85el8fhu5dnra	gs	View Comments 2015-12-02	2015-12-02			No
xn--w4rs40l	gs	View Comments 2015-12-02	2015-12-02			Yes
xperia	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02	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	gs	View Comments 2015-12-02	2015-12-02			No
yachts	gs	View Comments 2015-12-02	2015-12-02	View Mitigation yachts Mitigation By DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries) See attached document View Documents 2016-04-26	DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)	No
yodobashi	gs	View Comments 2015-12-02	2015-12-02	View Mitigation yodobashi Mitigation By YODOBASHI CAMERA CO.,LTD. 2 Letter Codes Mitigation Plan for YODOBASHI TLDs (.yodobashi .goldpoint) To address the confusion concerns cited by governments regarding the use of the second-level domains in the YODOBASHI TLDs, YODOBASHI CAMERA CO.,LTD. will implement a closed registration policy for YODOBASHI TLDs that mitigates the potential confusion. To these ends, YODOBASHI CAMERA CO., LTD. commits to the following: ・Developing and implementing a closed registration policy for YODOBASHI TLDs that requires that all domains name in the TLDs be registered and used by YODOBASHI CAMERA CO.,LTD., its affiliates, or its trademark licensees; ・Clearly publishing this registration policy on Registry Operator`s homepage for the YODOBASHI TLDs at “nic.yodobashi”, and “nic.goldpoint”. ・Referring to this registration policy in registry Operator`s Registry-Registrar Agreement with all appointed preferred registrars for the YODOBASHI TLDs. ・Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of YODOBASHI TLDs` qualification for Specification 13; and ・Using all domain names in the YODOBASHI TLDs in association with YODOBASHI`s brand products, and services. This publicly available registration and usage policy would prevent Governments from registering domains in the YODOBASHI TLDs. It would therefore clearly designate to the public that YODOBASHI TLDs were proprietary spaces in which all second-level domains in the TLDs were being operated by YODOBASHI CAMERA CO., LTD. and not governments. 2016-04-25	YODOBASHI CAMERA CO.,LTD.	Yes
yoga	gs	View Comments 2015-12-02	2015-12-02	View Mitigation yoga Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No
yokohama	gs	View Comments 2015-12-02	2015-12-02	View Mitigation yokohama Mitigation By GMO Registry About .YOKOHAMA .YOKOHAMA is a GeoTLD for the city of Yokohama, Japan, operated by GMO Registry, Inc. The purpose of .YOKOHAMA is to promote .YOKOHAMA and provide an opportunity for citizens, businesses and community groups to link their identities to the city’s brand. By bringing together quality and informative content, .YOKOHAMA provides a platform to effectively deliver city information to Internet users both locally and globally. It is also an important goal for the Registry that .YOKOHAMA is operated as a trusted, safe, secure, relevant and enjoyable namespace Protections Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the governments of a related country-code and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. Furthermore, contained within our Domain Name Registration Policy for the .YOKOHAMA TLD is the following text: All Applicants, all Domain Name Registrants, and any party submitting a Domain Name registration request represents and warrants that: − to its knowledge, the registration of the Domain Name mentioned in the Application or Domain Name Registration Request will not infringe upon or otherwise violate the rights of any third party; − will not register a domain name for the purpose of distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable laws or regulations; Should a Registrant fail to comply with the Acceptable Use Policy, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	GMO Registry	No
zappos	gs	View Comments 2015-12-02	2015-12-02	View Mitigation zappos Mitigation By Amazon Registry Services, Inc. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw. ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely: 1. Each of the .Brand TLDs is identical to a qualifying registered trademark; 2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11; 3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates; 4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and 5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs. Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above. 2016-04-25	Amazon Registry Services, Inc.	Yes
zara	gs	View Comments 2015-12-02	2015-12-02	View Mitigation zara Mitigation By INDITEX, S.A. .ZARA TLD is a closed Brand new gTLD operated by Inditex S.A. Protections: Inditex S.A. for the .ZARA TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Inditex S.A. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ZARA is identical to a qualifying registered trademark; 2. .ZARA is not a Generic String, as this is defined in Specification 11; 3. .ZARA TLD has developed and will implement a closed registration policy for .ZARA that requires that all domain names in the .ZARA TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ZARA TLD will clearly publish this registration policy; 5. .ZARA TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ZARA TLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that .ZARA TLD is a proprietary space in which all second-level domains in the TLD are being operated by Inditex S.A., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this notice, Inditex S.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-20	INDITEX, S.A.	Yes
zone	gs	View Comments 2015-12-02	2015-12-02	View Mitigation zone Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
zuerich	gs	View Comments 2015-12-02	2015-12-02			No
aarp	pn	View Comments 2015-12-02	2015-12-02	View Mitigation aarp Mitigation By AARP .AARP gTLD Confusion Avoidance Plan AARP, the Registry Operator for the .AARP gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that AARP will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AARP is identical to a qualifying registered trademark; 2. .AARP is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. AARP has developed and will implement a closed registration policy for .AARP that requires that all domain names in the .AARP gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, AARP submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .AARP will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .AARP gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .AARP gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by AARP, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, AARP confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-25	AARP	Yes
abb	pn	View Comments 2015-12-02	2015-12-02	View Mitigation abb Mitigation By ABB Ltd Provide a brief explanation of the TLD: ABB Ltd has applied for .ABB to run a closed .brand environment. Protections ABB Ltd for the .ABB TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the ABB Ltd will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABB is identical to a qualifying registered trademark; 2. .ABB is not a Generic String, as this is defined in Specification 11; 3. .ABB TLD has developed and will implement a closed registration policy for .ABB that requires that all domain names in the .ABB TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ABB TLD will clearly publish this registration policy; 5. .ABB TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ABB TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ABB TLD is a proprietary space in which all second-level domains in the TLD are being operated by ABB Ltd, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter ABB Ltd confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	ABB Ltd	Yes
abbott	pn	View Comments 2015-12-02	2015-12-02	View Mitigation abbott Mitigation By Abbott Laboratories, Inc. Abbott Laboratories, Inc., the Registry Operator for the .ABBOTT gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Abbott Laboratories, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ABBOTT is identical to a qualifying registered trademark; 2. .ABBOTT is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Abbott Laboratories, Inc. has developed and will implement a closed registration policy for .ABBOTT that requires that all domain names in the .ABBOTT gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Abbott Laboratories, Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .ABBOTT will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13, as required by the Registry Agreement. Compliance with Specification 13 prohibits the .ABBOTT gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .ABBOTT gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Abbott Laboratories, Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Abbott Laboratories, Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Abbott Laboratories, Inc.	Yes
abogado	pn	View Comments 2015-12-02	2015-12-02	View Mitigation abogado Mitigation By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse. c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name. 2016-04-22	Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH	No
academy	pn	View Comments 2015-12-02	2015-12-02	View Mitigation academy Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
accenture	pn	View Comments 2015-12-02	2015-12-02	View Mitigation accenture Mitigation By Accenture plc Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: Accenture plc has applied for .ACCENTURE to run a closed .brand environment. Protections Accenture plc for the .ACCENTURE TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Accenture plc will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ACCENTURE is identical to a qualifying registered trademark; 2. .ACCENTURE is not a Generic String, as this is defined in Specification 11; 3. .ACCENTURE TLD has developed and will implement a closed registration policy for .ACCENTURE that requires that all domain names in the .ACCENTURE TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ACCENTURE TLD will clearly publish this registration policy; 5. .ACCENTURE TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ACCENTURE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ACCENTURE TLD is a proprietary space in which all second-level domains in the TLD are being operated by Accenture plc - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator. By this letter, Accenture plc confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-20	Accenture plc	Yes
accountant	pn	View Comments 2015-12-02	2015-12-02	View Mitigation accountant Mitigation By Famous Four Media Limited By Famous Four media Limited. Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. 2. Registry Operator will enforce the terms of its Acceptable Use and Take down Policy against Registrants. 3. Should a Registrant fail to comply with the Acceptable Use and Take down Policy, the domain names may be cancelled, locked, placed on hold, transferred or deleted. Thus, all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-25	Famous Four Media Limited	No
accountants	pn	View Comments 2015-12-02	2015-12-02	View Mitigation accountants Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
actor	pn	View Comments 2015-12-02	2015-12-02	View Mitigation actor Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
adult	pn	View Comments 2015-12-02	2015-12-02	View Mitigation adult Mitigation By ICM Registry Protections Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any governments, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. Furthermore, we have the following Anti-Abuse Policy: Registry has the right, pursuant to its Registry-Registrant Agreement, to immediately deny, cancel, terminate, suspend, lock, hold, or transfer any domain name and/or registration to ensure registrant’s compliance with the following Anti-Abuse Policy. 1. Accurate Registration Information Registrant represents and warrants to have provided current, complete, and accurate information in connection with its registration and agrees to correct and update this information to ensure that it remains current, complete, and accurate throughout the term of any resulting registration in a TLD. Registrant’s obligation to provide current, accurate, and complete information is a material element of the Registry-Registrant Agreement, and the registry reserves the right to immediately deny, cancel, terminate, suspend, lock, or transfer any registration if it determines, in its sole discretion, that the information is materially inaccurate. 2. Child Protection Labeling Registrant understands that Registry Operator may label the sites in the TLD and any site to which such sites are automatically redirected irrespective of the top-level domain for child protection purposes; registrant consents to such labeling. 3. Prohibition on Child Abuse Images and Conduct or Content Designed to Suggest the Presence of Child Abuse Images The term “child abuse images” is defined as any photograph, film, video, picture, or computer or computer-generated image or picture, whether made or produced by electronic, mechanical, or other means, depicting child sexual abuse as stated in the United Nations Convention on the Rights of the Child. Registrant’s sites in the TLD shall not display any child abuse images. Registrant’s sites in the TLD shall not engage in practices that are designed to suggest the presence of child abuse images, including, without limitation, the use of meta-tags for that purpose. Registry Operator will refer any sites in a TLD that are reported to the Registry Operator to be in violation of this policy to child safety hotlines like the National Center for Missing and Exploited Children (NCMEC), the Internet Watch Foundation (IWF), or the International Association of Internet Hotlines (INHOPE). 4. Prohibition on Abusive Registrations No registrant may register an abusive second-level domain name in the TLD including, without limitation, domain names that infringe the intellectual property rights of a third party, including common law trademark rights; domain names that are obvious variants of well-known trademarks not belonging to the registrant; or domain names that suggest the presence of child abuse images. 5. Prohibition on Malicious Conduct No registrant shall use or permit use of a domain name in the TLD for or in connection with email spoofing, phishing, spam, or other forms of malicious behavior. 6. Ongoing Best Practices Policies Registry Operator will revise this Anti-Abuse Policy or the Registry-Registrant Agreement to include commercially reasonable best practices policies developed by the International Foundation for Online Responsibility (IFFOR) that are designed to promote responsible business practices related to (i) combating online child abuse images, (ii) facilitating user choice and parental control regarding access to online adult entertainment, (iii) protecting free expression rights, and/or (iv) protecting the privacy, security, and consumer rights of consenting adult consumers of online adult entertainment goods and services; registrant consents to adhere to such policies. The Registrant of a domain name, as recorded in the Registry Service, will be responsible for: a. the use of their domain name; b. ensuring that the use of the domain name, where that domain name is a two letter Label that corresponds to a country code described in the ISO 3166-1 alpha-2 standard, avoids confusion with the corresponding country code;” Should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-19	ICM Registry	No
aeg	pn	View Comments 2015-12-02	2015-12-02	View Mitigation aeg Mitigation By Aktiebolaget Electrolux Provide a brief explanation of the TLD: Aktiebolaget Electrolux has applied for .[TLD] to run a closed .brand environment. Protections Aktiebolaget Electrolux for the .[TLD] TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Aktiebolaget Electrolux will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .[TLD] is identical to a qualifying registered trademark; 2. .[TLD] is not a Generic String, as this is defined in Specification 11; 3. .[TLD] TLD has developed and will implement a closed registration policy for .[TLD] that requires that all domain names in the .[TLD] TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .[TLD] TLD will clearly publish this registration policy; 5. .[TLD] TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .[TLD] TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .[TLD] TLD is a proprietary space in which all second-level domains in the TLD are being operated by Aktiebolaget Electrolux, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter Aktiebolaget Electrolux confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	Aktiebolaget Electrolux	Yes
agency	pn	View Comments 2015-12-02	2015-12-02	View Mitigation agency Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
aig	pn	View Comments 2015-12-02	2015-12-02	View Mitigation aig Mitigation By American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. Protections American International Group, Inc. for the .AIG TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the American International Group, Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .AIG is identical to a qualifying registered trademark; 2. .AIG is not a Generic String, as this is defined in Specification 11; 3. .AIG TLD has developed and will implement a closed registration policy for .AIG that requires that all domain names in the .AIG TLD be registered ONLY by American International Group, Inc., its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .AIG TLD will clearly publish this registration policy; 5. .AIG TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .AIG TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .AIG TLD is a proprietary space in which all second-level domains in the TLD are being operated by American International Group, Inc., its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator. By this [LETTER] American International Group, Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-20	American International Group, Inc.	Yes
airforce	pn	View Comments 2015-12-02	2015-12-02	View Mitigation airforce Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
allfinanz	pn	View Comments 2015-12-02	2015-12-02	View Mitigation allfinanz Mitigation By Allfinanz Deutsche Vermögensberatung Aktiengesellschaft Please find Allfinanz Deutsche Vermögensberatung Aktiengesellschaft's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.ALLFINANZ” attached. View Documents 2016-04-23	Allfinanz Deutsche Vermögensberatung Aktiengesellschaft	No
ally	pn	View Comments 2015-12-02	2015-12-02			Yes
amsterdam	pn	View Comments 2015-12-02	2015-12-02	View Mitigation amsterdam Mitigation By City of Amsterdam For the top level domain .AMSTERDAM we would like to use two letter domains and we propose the following measures to avoid confusion. A brief explanation of the TLD: .amsterdam is a geographic TLD for the City of Amsterdam; the City of Amsterdam is the designated Registry Operator. The toplevel domain is open, anyone in the world can register domain names. Proposed measures to avoid confusion The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ci, cn, eg, hk, il, in, it, me, pt and sg. Protections The Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: • Registry Operator will commit to investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and • where, in Registry Operator's sole opinion, misuse has occurred, cause the domain name's records to be removed from the DNS. Policy measures Contained within our Acceptable Use Policy for .amsterdam is the following text: ".Abuse in the context of this Policy shall be defined as an action that causes actual and substantial harm, or is a material predicate of such harm, or is illegal, illegitimate, or otherwise contrary to this Policy, including, but not limited to, the following: ... h. Violation of any applicable local, state, national or international law or regulation by use of a Domain Name; i . The confusing use of a 2character domain name that corresponds to a country code as described in the ISO 3166 alpha 2 standard with the corresponding country code...” Should a Registrant fail to comply with the Acceptable Use Policy, the registry has the right to lock, transfer or cancel any offending domain name. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and the City of Amsterdam has clear penalties for any failure to do so. View Documents 2016-05-09	City of Amsterdam	No
analytics	pn	View Comments 2015-12-02	2015-12-02	View Mitigation analytics Mitigation By Karen L. Day Please see the attached documents outlining our registry's plans to avoid confusion with certain 2 character labels as previously requested. View Documents 2016-05-06	Karen L. Day	No
anz	pn	View Comments 2015-12-02	2015-12-02	View Mitigation anz Mitigation By Australia and New Zealand Banking Group Limited Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: Australia and New Zealand Banking Group Limited has applied for .ANZ to run a closed .brand environment. Protections Australia and New Zealand Banking Group Limited for the .ANZ TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Australia and New Zealand Banking Group Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ANZ is identical to a qualifying registered trademark; 2. .ANZ is not a Generic String, as this is defined in Specification 11; 3. .ANZ has developed and will implement a closed registration policy for .ANZ that requires that all domain names in the .ANZ TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ANZ TLD will clearly publish this registration policy; 5. .ANZ TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ANZ TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ANZ TLD is a proprietary space in which all second-level domains in the TLD are being operated by Australia and New Zealand Banking Group Limited - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator. By this letter, Australia and New Zealand Banking Group Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13 2016-04-22	Australia and New Zealand Banking Group Limited	Yes
apartments	pn	View Comments 2015-12-02	2015-12-02	View Mitigation apartments Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
apple	pn	View Comments 2015-12-02	2015-12-02			Yes
aquarelle	pn	View Comments 2015-12-02	2015-12-02			Yes
archi	pn	View Comments 2015-12-02	2015-12-02	View Mitigation archi Mitigation By Starting Dot The proposed measure to avoid confusion for .ARCHI applies across all two-character labels. The proposed measure can be found in the file attached. View Documents 2016-04-25	Starting Dot	No
army	pn	View Comments 2015-12-02	2015-12-02	View Mitigation army Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
arte	pn	View Comments 2015-12-02	2015-12-02	View Mitigation arte Mitigation By Association Relative à la Télévision Européenne G.E.I.E. Provide a brief explanation of the TLD: Association Relative à la Télévision Européenne G.E.I.E. has applied for .ARTE to run a closed .brand environment. Protections Association Relative à la Télévision Européenne G.E.I.E. for the .ARTE TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Association Relative à la Télévision Européenne G.E.I.E. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .ARTE is identical to a qualifying registered trademark; 2. .ARTE is not a Generic String, as this is defined in Specification 11; 3. .ARTE TLD has developed and will implement a closed registration policy for .ARTE that requires that all domain names in the .ARTE TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .ARTE TLD will clearly publish this registration policy; 5. .ARTE TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .ARTE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ARTE TLD is a proprietary space in which all second-level domains in the TLD are being operated by Association Relative à la Télévision Européenne G.E.I.E., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this letter Association Relative à la Télévision Européenne G.E.I.E. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	Association Relative à la Télévision Européenne G.E.I.E.	Yes
associates	pn	View Comments 2015-12-02	2015-12-02	View Mitigation associates Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
attorney	pn	View Comments 2015-12-02	2015-12-02	View Mitigation attorney Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
auction	pn	View Comments 2015-12-02	2015-12-02	View Mitigation auction Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
audi	pn	View Comments 2015-12-02	2015-12-02	View Mitigation audi Mitigation By Audi Aktiengesellschaft .audi is a closed Brand TLD for the sole and exclusive use of Audi Aktiengesellschaft. Protections Audi Aktiengesellschaft (Registry Operator) for the .audi TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Registry Operator will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: .audi is identical to a qualifying registered trademark; .audi is not a Generic String, as this is defined in Specification 11; Registry Operator has developed and implemented a closed registration policy for .audi that requires that all domain names in the .audi TLD be registered only by Audi Aktiengesellschaft, its Affiliates, and its Trademark Licensees. As required under the Registry Agreement, the Registry Operator published this registration policy on its website. Registry Operator will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the Registry Operator from registering domain names to unaffiliated third parties and thus clearly designate to the public that .audi TLD is a proprietary space in which all second-level domains in the TLD are being operated by the Registry Operator, its Affiliates and Trademark Licensees and not the governments or the corresponding country code operators. By this submission Audi Aktiengesellschaft confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-21	Audi Aktiengesellschaft	Yes
audible	pn	View Comments 2015-12-02	2015-12-02	View Mitigation audible Mitigation By Amazon Registry Services, Inc. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw. ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely: 1. Each of the .Brand TLDs is identical to a qualifying registered trademark; 2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11; 3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates; 4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and 5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs. Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above. 2016-04-25	Amazon Registry Services, Inc.	Yes
audio	pn	View Comments 2015-12-02	2015-12-02			No
auto	pn	View Comments 2015-12-02	2015-12-02			No
autos	pn	View Comments 2015-12-02	2015-12-02	View Mitigation autos Mitigation By DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries) See attached document View Documents 2016-04-26	DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)	No
aws	pn	View Comments 2015-12-02	2015-12-02	View Mitigation aws Mitigation By Amazon Registry Services, Inc. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw. ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely: 1. Each of the .Brand TLDs is identical to a qualifying registered trademark; 2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11; 3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates; 4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and 5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs. Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above. 2016-04-25	Amazon Registry Services, Inc.	Yes
azure	pn	View Comments 2015-12-02	2015-12-02	View Mitigation azure Mitigation By Microsoft Corporation Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: .AZURE TLD is a closed Brand new gTLD operated by Microsoft Corporation Protections: Microsoft Corporation for the .AZURE 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. .AZURE is identical to a qualifying registered trademark; 2. .AZURE is not a Generic String, as this is defined in Specification 11; 3. .AZURE TLD has developed and will implement a closed registration policy for .AZURE that requires that all domain names in the .AZURE TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .AZURE TLD will clearly publish this registration policy; 5. .AZURE TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .AZURE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .AZURE 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
band	pn	View Comments 2015-12-02	2015-12-02	View Mitigation band Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
bank	pn	View Comments 2015-12-02	2015-12-02	View Mitigation bank Mitigation By fTLD Registry Services, LLC Please see the attached file that details fTLD Registry Services' implementation plan for .BANK and .INSURANCE to avoid confusion with corresponding country codes. View Documents 2016-04-20	fTLD Registry Services, LLC	No
barclaycard	pn	View Comments 2015-12-02	2015-12-02	View Mitigation barclaycard Mitigation By Barclays Bank PLC .barclaycard is a closed top-level domain name for the sole and exclusive use of Barclays Bank PLC. Protections Barclays Bank PLC is the Registry Operator for the .barclaycard TLD and has executed Specification 13 of the Registry Agreement. Specification 13 already contractually requires that Barclays Bank PLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .barclaycard is identical to a qualifying registered trademark; 2. .barclaycard is not a Generic String, as this is defined in Specification 11; 3. .barclaycard TLD has developed and will implement a closed registration policy for .barclaycard that requires that all domain names in the .barclaycard TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .barclaycard TLD will clearly publish this registration policy; 5. .barclaycard TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .barclaycard TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .barclaycard TLD is a proprietary space in which all second-level domains in the TLD are being operated by Barclays Bank PLC, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this text Barclays Bank PLC confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-08	Barclays Bank PLC	Yes
barclays	pn	View Comments 2015-12-02	2015-12-02	View Mitigation barclays Mitigation By Barclays Bank PLC .barclays is a closed top-level domain name for the sole and exclusive use of Barclays Bank PLC. Protections Barclays Bank PLC is the Registry Operator for the .barclays TLD and has executed Specification 13 of the Registry Agreement. Specification 13 already contractually requires that Barclays Bank PLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .barclays is identical to a qualifying registered trademark; 2. .barclays is not a Generic String, as this is defined in Specification 11; 3. .barclays TLD has developed and will implement a closed registration policy for .barclays that requires that all domain names in the .barclays TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .barclays TLD will clearly publish this registration policy; 5. .barclays TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .barclays TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .barclays TLD is a proprietary space in which all second-level domains in the TLD are being operated by Barclays Bank PLC, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this text Barclays Bank PLC confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-08	Barclays Bank PLC	Yes
bargains	pn	View Comments 2015-12-02	2015-12-02	View Mitigation bargains Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
bayern	pn	View Comments 2015-12-02	2015-12-02	View Mitigation bayern 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
bbva	pn	View Comments 2015-12-02	2015-12-02	View Mitigation bbva Mitigation By BANCO BILBAO VIZCAYA ARGENTARIA, S.A. Provide a brief explanation of the TLD: BANCO BILBAO VIZCAYA ARGENTARIA, S.A. has applied for .BBVA to run a closed .brand environment. Protections BANCO BILBAO VIZCAYA ARGENTARIA, S.A. for the .BBVA TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the BANCO BILBAO VIZCAYA ARGENTARIA, S.A. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .BBVA is identical to a qualifying registered trademark; 2. .BBVA is not a Generic String, as this is defined in Specification 11; 3. .BBVA TLD has developed and will implement a closed registration policy for .BBVA that requires that all domain names in the .BBVA TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .BBVA TLD will clearly publish this registration policy; 5. .BBVA TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .BBVA TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .BBVA TLD is a proprietary space in which all second-level domains in the TLD are being operated by BANCO BILBAO VIZCAYA ARGENTARIA, S.A., its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator. By this [LETTER] BANCO BILBAO VIZCAYA ARGENTARIA, S.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-15	BANCO BILBAO VIZCAYA ARGENTARIA, S.A.	Yes
beats	pn	View Comments 2015-12-02	2015-12-02			Yes
beer	pn	View Comments 2015-12-02	2015-12-02	View Mitigation beer 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
bentley	pn	View Comments 2015-12-02	2015-12-02	View Mitigation bentley Mitigation By Bentley Motors Limited Proposed measures to avoid confusion relating to all two-character labels .Bentley .Bentley TLD is a closed Brand new gTLD operated by Bentley Motors Limited. Within the .Bentley namespace, Internet traffic will be driven to sites that are a reflection of the brand and users will gain the full benefit of the Bentley experience, secure in the knowledge of its authentic, credible and reliable source. .Bentley will be positioned, promoted and deployed as the single, dependable and trustworthy domain for Internet users to access information relating to the brand. Protections Bentley Motors Limited for the .Bentley TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Bentley Motors Limited will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .Bentley is identical to a qualifying registered trademark; 2. .Bentley is not a Generic String, as this is defined in Specification 11; 3. .Bentley TLD has developed and will implement a closed registration policy for .Bentley that requires that all domain names in the .Bentley TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .Bentley TLD will clearly publish this registration policy; 5. .Bentley TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .Bentley TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .Bentley TLD is a proprietary space in which all second-level domains in the TLD are being operated by Bentley Motors Limited, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this notice Bentley Motors Limited confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-22	Bentley Motors Limited	Yes
berlin	pn	View Comments 2015-12-02	2015-12-02	View Mitigation berlin Mitigation By dotBERLIN GmbH & Co. KG Proposed Measures to Avoid Confusion within the Community-based GeoTLD .BERLIN for ci, cn, eg, hk, il, in, it, me, pt, sg, tw “.BERLIN is the top-level domain for the Community of Berliners in the Internet (the .BERLIN Community). The local domain names available with the .BERLIN top-level domain are concise and create an identity for citizens, companies and institutions. Those providing and looking for information, goods and services can thus intuitively come together. The .BERLIN domain names strengthen the feeling of community amongst Berliners, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Berliners and for non-Berliners, Berlin becomes more attractive as a place to visit, as a commercial location and as a place to live.” Protections To address the confusion concerns cited by the governments regarding the use of the second-level domains cited above in the .BERLIN, the Registry Operator dotBERLIN GmbH & Co. KG has implemented a restricted registration policy for .BERLIN that mitigates the potential confusion. To these ends, Registry Operator commits to the following (as mentioned in its application at https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails:downloadapplication/1777?t:ac=1777): dotBERLIN developed and implemented a restricted registration policy and enforces this restricted Registration Policy for .BERLIN including: Eligibility Requirements: To meet the requirements of ICANN to a community-based designation of the application and to meet a sufficient reference to BERLIN, the group of registrants is limited. Exclusively eligible to register a domain name under the top-level domain .BERLIN is any natural person, legal person, organization or association of persons, if they can demonstrate that they have an economic, cultural, historical, social or any other connection to the German capital Berlin, verifiable by -their residence or second home, office or place of business, a branch or permanent establishment in the City of BERLIN, or -a contact listed in the Whois database with a domicile in the City of BERLIN, or -other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate. With the registration of a .BERLIN domain name each registrant implicitly signs the registration policies and agrees with the fact that he acknowledges compliance with the registration guidelines. A review of whether the applicant meets the required eligibility, does not take place regularly on the date of registration, however, anyone can check compliance with the registration requirements by initiating an extrajudicial dispute resolution procedure (ʺ.BERLIN Eligibility Requirements Dispute Resolution Policyʺ) or an objection process. Content and Use Requirements: To meet the requirements of ICANN to a community-based designation of the application, the registrant must satisfy the following criteria for the content and the use of .BERLIN domain names: - The contents of the website under a domain name must be directly related to the eligibility requirements, and - the domain must be in use within 12 months of registration. Legal Safeguards, Enforcement and continued Compliance: To meet the requirements of ICANN to a community-based designation of the application, the registrant must use the .BERLIN domain in an economic, cultural, social or any other meaningful connection to the City of Berlin. This designation of .BERLIN to the .BERLIN Community will be enforced by specific language in the Registry-Registrar-Agreement that holds gTLD registrars responsible to include the restrictions as outlined above in respective agreements with their gTLD registrants. The .BERLIN Registry will, from time to time in its sole discretion or upon evidence or advice manually conduct continuing or recurring audits of domain names registered to ensure continued compliance with these requirements. Failure to comply will result in a notice providing 20-days to comply. Non-compliance following such a notice period may result in take-down of the relevant domain name, at the discretion of the Registry. Those policies have been clearly publishing policy on Registry Operator’s homepage for .BERLIN. This registration and usage policy would prevent governments from registering domains in the .BERLIN TLD. It would clearly designate to users that .BERLIN was a restricted space in which all second-level domains were registered by eligible Registrants. 2016-04-25 View Mitigation berlin Mitigation By dotBERLIN GmbH & Co. KG Proposed Measures to Avoid Confusion within the Community-based GeoTLD .BERLIN for su, ru, uk, it, gb, ac, gi, tc, sh, ms, ky, io, bm, fk, ng, kr, il, sg, hk, pn, gs, tw, vn, ln, in, pt “.BERLIN is the top-level domain for the Community of Berliners in the Internet (the .BERLIN Community). The local domain names available with the .BERLIN top-level domain are concise and create an identity for citizens, companies and institutions. Those providing and looking for information, goods and services can thus intuitively come together. The .BERLIN domain names strengthen the feeling of community amongst Berliners, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Berliners and for non-Berliners, Berlin becomes more attractive as a place to visit, as a commercial location and as a place to live.” Protections To address the confusion concerns cited by the governments regarding the use of the second-level domains cited above in the .BERLIN, the Registry Operator dotBERLIN GmbH & Co. KG has implemented a restricted registration policy for .BERLIN that mitigates the potential confusion. To these ends, Registry Operator commits to the following (as mentioned in its application at https://gtldresult.icann.org/application-result/applicationstatus/applicationdetails:downloadapplication/1777?t:ac=1777): dotBERLIN developed and implemented a restricted registration policy and enforces this restricted Registration Policy for .BERLIN including: Eligibility Requirements: To meet the requirements of ICANN to a community-based designation of the application and to meet a sufficient reference to BERLIN, the group of registrants is limited. Exclusively eligible to register a domain name under the top-level domain .BERLIN is any natural person, legal person, organization or association of persons, if they can demonstrate that they have an economic, cultural, historical, social or any other connection to the German capital Berlin, verifiable by -their residence or second home, office or place of business, a branch or permanent establishment in the City of BERLIN, or -a contact listed in the Whois database with a domicile in the City of BERLIN, or -other appropriate proof e.g. the certification by an employer to enroll at a school or college, or birth certificate. With the registration of a .BERLIN domain name each registrant implicitly signs the registration policies and agrees with the fact that he acknowledges compliance with the registration guidelines. A review of whether the applicant meets the required eligibility, does not take place regularly on the date of registration, however, anyone can check compliance with the registration requirements by initiating an extrajudicial dispute resolution procedure (ʺ.BERLIN Eligibility Requirements Dispute Resolution Policyʺ) or an objection process. Content and Use Requirements: To meet the requirements of ICANN to a community-based designation of the application, the registrant must satisfy the following criteria for the content and the use of .BERLIN domain names: - The contents of the website under a domain name must be directly related to the eligibility requirements, and - the domain must be in use within 12 months of registration. Legal Safeguards, Enforcement and continued Compliance: To meet the requirements of ICANN to a community-based designation of the application, the registrant must use the .BERLIN domain in an economic, cultural, social or any other meaningful connection to the City of Berlin. This designation of .BERLIN to the .BERLIN Community will be enforced by specific language in the Registry-Registrar-Agreement that holds gTLD registrars responsible to include the restrictions as outlined above in respective agreements with their gTLD registrants. The .BERLIN Registry will, from time to time in its sole discretion or upon evidence or advice manually conduct continuing or recurring audits of domain names registered to ensure continued compliance with these requirements. Failure to comply will result in a notice providing 20-days to comply. Non-compliance following such a notice period may result in take-down of the relevant domain name, at the discretion of the Registry. Those policies have been clearly publishing policy on Registry Operator’s homepage for .BERLIN. This registration and usage policy would prevent governments from registering domains in the .BERLIN TLD. It would clearly designate to users that .BERLIN was a restricted space in which all second-level domains were registered by eligible Registrants. 2016-04-25	dotBERLIN GmbH & Co. KG	No
best	pn	View Comments 2015-12-02	2015-12-02			No
bet	pn	View Comments 2015-12-02	2015-12-02	View Mitigation bet 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
bharti	pn	View Comments 2015-12-02	2015-12-02			Yes

uk Comments

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

The administration in South Georgia and the South Sandwich Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

uk Comments

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

The administration in the Pitcairn Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.

Two-Character Letter/Letter Label Comments and Mitigation Measures

webcam Mitigation

website Mitigation

wedding 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--3oq18vl8pn36a Mitigation

xn--czr694b Mitigation

xn--czrs0t Mitigation

xn--czru2d Mitigation

xn--fjq720a Mitigation

xn--g2xx48c Mitigation

xn--gk3at1e Mitigation

xn--kcrx77d1x4a Mitigation

xn--unup4y Mitigation

xn--vhquv Mitigation

xperia Mitigation

xxx Mitigation

yachts Mitigation

yodobashi Mitigation

yoga Mitigation

yokohama Mitigation

zappos Mitigation

zara Mitigation

zone Mitigation

aarp Mitigation

abb Mitigation

abbott Mitigation

abogado Mitigation

academy Mitigation

accenture Mitigation

accountant Mitigation

accountants Mitigation

actor Mitigation

adult Mitigation

aeg Mitigation

agency Mitigation

aig Mitigation

airforce Mitigation

allfinanz Mitigation

amsterdam Mitigation

analytics Mitigation

anz Mitigation

apartments Mitigation

archi Mitigation

army Mitigation

arte Mitigation

associates Mitigation

attorney Mitigation

auction Mitigation

audi Mitigation

audible Mitigation

autos Mitigation

aws Mitigation

azure Mitigation

band Mitigation

bank Mitigation