About ICANN
- 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
- Expected Standards of Behavior
- Employee Practices and Resources
- Enhancing ICANN Accountability – Work Stream 2 Implementation
Governance
- Governance Documents
- Evolving ICANN’s MSM
- Agreements
- Annual Reports
- Financials
- Planning
  - Strategic Plan
- Presentations
- RFPs
- Litigation
- Newsletter
- Correspondence
  - 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
- Programs
- Complaint Submission & Learn More
- Reporting & Performance Measurement
Registrars
- Accreditation Agreement
  - Global Amendments
    - 2024 Global Amendment to the RAA
    - 2023 Global Amendment to the RAA
- Registrar Library
- News & Communications
- How to Become a Registrar
- Changes to Existing Accreditation
- Privacy and Proxy Service Providers
- Registrar Resources
Registry Operators
- Advisories & Consensus Policies
  - Advisories
  - Consensus Policies
    - Registration Data Policy
      - Registration Data Policy Implementation Resources
    - Registry Service Evaluation Policy (RSEP)
- News & Events
- Registry Agreements
  - Global Amendments
- Registry Resources
- Services for Registry Operators
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 IS-SSR)
- IS-SSR Team Blogs
- Security Terminology
- Document Archive
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
- Universal Acceptance Steering Group (UASG)
- UA Training
- UA Day
- UA Readiness Evaluations
- 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
dance	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dance Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
date	ng	View Comments 2015-12-04	2015-12-05	View Mitigation date 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
dating	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dating Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
datsun	ng	View Comments 2015-12-04	2015-12-05	View Mitigation datsun Mitigation By NISSAN MOTOR CO., LTD. 2 Letter Codes Mitigation Plan for NISSAN TLDs (.nissan .infiniti .datsun) To address the confusion concerns cited by governments regarding the use of the second-level domains in the NISSAN TLDs, NISSAN MOTOR CO., LTD. will implement a closed registration policy for NISSAN TLDs that mitigates the potential confusion. To these ends, NISSAN MOTOR CO., LTD. commits to the following: ・Developing and implementing a closed registration policy for NISSAN TLDs that requires that all domains name in the TLDs be registered and used by NISSAN MOTOR CO., LTD., its affiliates, or its trademark licensees; ・Clearly publishing this registration policy on Registry Operator`s homepage for the NISSAN TLDs at “nic.nissan”,”nic.infiniti”, and “nic.datsun”. ・Referring to this registration policy in registry Operator`s Registry-Registrar Agreement with all appointed preferred registrars for the NISSAN TLDs. ・Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of Nissan TLDs` qualification for Specification 13; and ・Using all domain names in the NISSAN TLDs in association with NISSAN`s brand products, and services. This publicly available registration and usage policy would prevent Governments from registering domains in the NISSAN TLDs. It would therefore clearly designate to the public that NISSAN TLDs were proprietary spaces in which all second-level domains in the TLDs were being operated by NISSAN MOTOR CO., LTD. and not governments. 2016-04-25	NISSAN MOTOR CO., LTD.	No
deal	ng	View Comments 2015-12-04	2015-12-05	View Mitigation deal Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
deals	ng	View Comments 2015-12-04	2015-12-05	View Mitigation deals Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
degree	ng	View Comments 2015-12-04	2015-12-05	View Mitigation degree Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
delivery	ng	View Comments 2015-12-04	2015-12-05	View Mitigation delivery Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
dell	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dell Mitigation By Dell Inc. Dell Inc., the Registry Operator for the .DELL gTLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Dell Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .DELL is identical to a qualifying registered trademark; 2. .DELL is not a Generic String, as the term is defined in Specification 11 of the Registry Agreement; 3. Dell Inc. has developed and will implement a closed registration policy for .DELL that requires that all domain names in the .DELL gTLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, Dell Inc. submitted this policy as part of its application for Specification 13 and has clearly published this registration policy; and 5. .DELL 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 .DELL gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .DELL gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Dell Inc., its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator. With this submission, Dell Inc. confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13. 2016-04-15	Dell Inc.	Yes
deloitte	ng	View Comments 2015-12-04	2015-12-05	View Mitigation deloitte Mitigation By Deloitte Touche Tohmatsu Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: The .deloitte TLD is a .brand TLD as defined in Schedule 13 to ICANN’s registry agreement. It is used by Deloitte Touche Tohmatsu Limited (“DTTL”), the member firms of DTTL, and their related entities to register various domain names related to their business operations. “Deloitte” is the brand under which tens of thousands of dedicated professionals in these entities throughout the world collaborate to provide audit, consulting, financial advisory, risk management, tax and related services to select clients. The .deloitte TLD supports these business, providing for brand enhancement and protection by creating a single ecosystem where Deloitte stakeholders know that they are an “official” Deloitte website. Protections: Deloitte Touche Tohmatsu for the .deloitte TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Deloitte Touche Tohmatsu will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .deloitte is identical to a qualifying registered trademark; 2. .deloitte is not a Generic String, as this is defined in Specification 11; 3. .deloitte TLD has developed and will implement a closed registration policy for .deloitte that requires that all domain names in the .deloitte TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .deloitte TLD will clearly publish this registration policy; 5. .deloitte TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .deloitte TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .deloitte TLD is a proprietary space in which all second-level domains in the TLD are being operated by Deloitte Touche Tohmatsu, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this submission Deloitte Touche Tohmatsu confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. View Documents 2016-04-18	Deloitte Touche Tohmatsu	Yes
delta	ng	View Comments 2015-12-04	2015-12-05	View Mitigation delta Mitigation By Delta Air Lines, Inc. The .DELTA TLD is a closed, single-registrant TLD as defined by Specification 13 of the Registry Agreement (“RA”). Domain registrations, renewals and maintenance will be available only to authorized users and members of Delta Air Lines, Inc. and its subsidiaries. The .DELTA TLD sets to optimize customer service, communicate corporate and consumer information and promote security as follows: • A consistently structured and authenticated system of Internet and Intranet communication. • An authenticated brand that enhances consumer confidence in communication from and to .DELTA. Eligibility All second-level domains and subsequent sub-domains will be generated solely for the communication structure and strategy of Delta Air Lines, Inc. and its subsidiaries. Accordingly, .DELTA registrations will not be freely available to the market. Registry Operator will comply with all requirements of Specification 5 of the Registry Agreement. Rights Protection Registry Operator will adhere to rights protection mechanisms mandated by ICANN, including all mechanisms included in Specification 7 of the Registry Agreement. Acceptable Use Registry Operator will take all reasonable steps to protect personal data from loss, misuse, unauthorized disclosure, alteration or destruction. Registry Operator will also comply, in accordance with the Registry Agreement, with all existing and future consensus policies as formally adopted by ICANN. Registry Operator will only use ICANN-accredited registrars established under the 2013 Registrar Accreditation Agreement. As a single-registrant TLD eligible for Specification 13, Registry Operator will implement all policies and procedures established within the Registry Agreement. 2016-04-25	Delta Air Lines, Inc.	Yes
democrat	ng	View Comments 2015-12-04	2015-12-05	View Mitigation democrat Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
dental	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dental Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
dentist	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dentist Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
desi	ng	View Comments 2015-12-04	2015-12-05			No
design	ng	View Comments 2015-12-04	2015-12-05	View Mitigation design Mitigation By Top Level Design LLC The .design measures for the avoidance of confusion pertain to the following letter/letter labels: ci, cn, eg, il, in, it, me, pt, and sg. Top Level Design LLC is the Registry Operator for .design, an open, generic TLD for designers of all disciplines. 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, Italy, Montenegro, Portugal, and Singapore), 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
diamonds	ng	View Comments 2015-12-04	2015-12-05	View Mitigation diamonds Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
diet	ng	View Comments 2015-12-04	2015-12-05			No
digital	ng	View Comments 2015-12-04	2015-12-05	View Mitigation digital Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
direct	ng	View Comments 2015-12-04	2015-12-05	View Mitigation direct Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
directory	ng	View Comments 2015-12-04	2015-12-05	View Mitigation directory Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
discount	ng	View Comments 2015-12-04	2015-12-05	View Mitigation discount Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
dnp	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dnp Mitigation By Dai Nippon Printing Co., Ltd. .dnp 2 Letter Codes Mitigation Plan To address the confusion concerns cited by governments regarding the use of the second-level domains in the .dnp TLD, Dai Nippon Printing Co., Ltd. will implement a closed registration policy for .dnp that mitigates the potential confusion. To these ends, Dai Nippon Printing Co., Ltd. commits to the following: ・Developing and implementing a closed registration policy for .dnp that requires that all domains name in the TLD be registered and used by Dai Nippon printing Co., Ltd., its affiliates, or its trademark licensees; ・Clearly publishing this registration policy on Registry Operator`s homepage for the .dnp TLD at “nic.dnp”. ・Referring to this registration policy in registry Operator`s Registry-Registrar Agreement with all appointed preferred registrars for the .dnp TLD. ・Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of .dnp`s qualification for Specification 13; and ・Using all domain names in the .dnp TLD in association with DNP`s brand products, and services. This publicly available registration and usage policy would prevent Governments from registering domains in the .dnp. It would therefore clearly designate to the public that .dnp was a proprietary space in which all second-level domains in the TLD were being operated by Dai Nippon Printing Co., Ltd. and not governments. 2016-04-25	Dai Nippon Printing Co., Ltd.	Yes
docs	ng	View Comments 2015-12-04	2015-12-05	View Mitigation docs Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	No
dog	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dog Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
domains	ng	View Comments 2015-12-04	2015-12-05	View Mitigation domains Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
download	ng	View Comments 2015-12-04	2015-12-05	View Mitigation download 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
drive	ng	View Comments 2015-12-04	2015-12-05	View Mitigation drive Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	No
dunlop	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dunlop Mitigation By The Goodyear Tire & Rubber Company Brief explanation of the TLD: The Goodyear Tire & Rubber Company has applied for .dunlop to run a closed .brand environment. Protections The Goodyear Tire & Rubber Company for the .dunlop TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that The Goodyear Tire & Rubber Company will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .dunlop is identical to a qualifying registered trademark; 2. .dunlop is not a Generic String, as this is defined in Specification 11; 3. .dunlop TLD has developed and will implement a closed registration policy for .dunlop that requires that all domain names in the .dunlop TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .dunlop TLD will clearly publish this registration policy; 5. .dunlop TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .dunlop TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .dunlop TLD is a proprietary space in which all second-level domains in the TLD are being operated by The Goodyear Tire & Rubber Company, its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator. By this [LETTER] The Goodyear Tire & Rubber Company confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-21	The Goodyear Tire & Rubber Company	Yes
dvag	ng	View Comments 2015-12-04	2015-12-05	View Mitigation dvag Mitigation By Deutsche Vermögensberatung Aktiengesellschaft DVAG Please find Deutsche Vermögensberatung Aktiengesellschaft DVAG's Mitigation Measures to Avoid Confusion (concerning 2-letter labels in general) for the “.DVAG” and ".POHL" TLDs attached. View Documents 2016-04-23 View Mitigation dvag Mitigation By Deutsche Vermögensberatung Aktiengesellschaft DVAG Please find Deutsche Vermögensberatung Aktiengesellschaft DVAG's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) for the “.DVAG” and ".POHL" TLDs attached. View Documents 2016-04-25	Deutsche Vermögensberatung Aktiengesellschaft DVAG	No
earth	ng	View Comments 2015-12-04	2015-12-05			No
education	ng	View Comments 2015-12-04	2015-12-05	View Mitigation education Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
email	ng	View Comments 2015-12-04	2015-12-05	View Mitigation email Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
emerck	ng	View Comments 2015-12-04	2015-12-05	View Mitigation emerck Mitigation By Merck KGaA Please find Merck KGaA's "Mitigation Measures to Avoid Confusion" (concerning 2-letter labels in general) the “.EMERCK” TLD attached. View Documents 2016-04-25	Merck KGaA	Yes
energy	ng	View Comments 2015-12-04	2015-12-05	View Mitigation energy Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
engineer	ng	View Comments 2015-12-04	2015-12-05	View Mitigation engineer Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
engineering	ng	View Comments 2015-12-04	2015-12-05	View Mitigation engineering Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
enterprises	ng	View Comments 2015-12-04	2015-12-05	View Mitigation enterprises Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
epson	ng	View Comments 2015-12-04	2015-12-05	View Mitigation epson Mitigation By Seiko Epson Corporation Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: .epson is a closed Brand new gTLD operated by Seiko Epson Corporation Protections: Seiko Epson Corporation for the .epson TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Seiko Epson Corporation will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .epson is identical to a qualifying registered trademark; 2. .epson is not a Generic String, as this is defined in Specification 11; 3. .epson TLD has developed and will implement a closed registration policy for .epson that requires that all domain names in the .epson TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .epson TLD will clearly publish this registration policy; 5. .epson TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .epson TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .epson TLD is a proprietary space in which all second-level domains in the TLD are being operated by Seiko Epson Corporation, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Seiko Epson Corporation confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	Seiko Epson Corporation	Yes
equipment	ng	View Comments 2015-12-04	2015-12-05	View Mitigation equipment Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
estate	ng	View Comments 2015-12-04	2015-12-05	View Mitigation estate Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
events	ng	View Comments 2015-12-04	2015-12-05	View Mitigation events Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
everbank	ng	View Comments 2015-12-04	2015-12-05			Yes
exchange	ng	View Comments 2015-12-04	2015-12-05	View Mitigation exchange Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
expert	ng	View Comments 2015-12-04	2015-12-05	View Mitigation expert Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
exposed	ng	View Comments 2015-12-04	2015-12-05	View Mitigation exposed Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
express	ng	View Comments 2015-12-04	2015-12-05	View Mitigation express Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
fage	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fage Mitigation By Fage International S.A. Protections FAGE INTERNATIONAL S.A., for the .FAGE TLD, has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that FAGE INTERNATIONAL S.A. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .FAGE is identical to a qualifying registered trademark; 2. .FAGE is not a Generic String, as this is defined in Specification 11; 3. .FAGE has developed and will implement a closed registration policy for .FAGE that requires that all domain names in the .FAGE TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .FAGE TLD will clearly publish this registration policy; 5. .FAGE TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .FAGE TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .FAGE TLD is a proprietary space in which all second-level domains in the TLD are being operated by FAGE INTERNATIONAL S.A. - its Affiliates and Trademark Licensees and not the Government or the corresponding country code operator. By this letter, FAGE INTERNATIONAL S.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-20	Fage International S.A.	Yes
fail	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fail Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
faith	ng	View Comments 2015-12-04	2015-12-05	View Mitigation faith 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
family	ng	View Comments 2015-12-04	2015-12-05	View Mitigation family Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
fan	ng	View Comments 2015-12-04	2015-12-05			No
fans	ng	View Comments 2015-12-04	2015-12-05			No
farm	ng	View Comments 2015-12-04	2015-12-05	View Mitigation farm Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
fashion	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fashion 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
fast	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fast Mitigation By Amazon Registry Services, Inc. Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b. Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes. ARSI will commit to: 1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that: a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and b. corresponds to that government’s country code; and c. implies or represents that it is, or has the approval of, such government; and 2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion: a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or b. may cause the domain name’s records to be removed from the DNS; and 3. Provide a written response within a commercially reasonable time period. ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above. 2016-04-25	Amazon Registry Services, Inc.	No
ferrero	ng	View Comments 2015-12-04	2015-12-05	View Mitigation ferrero Mitigation By Ferrero Trading Lux S.A. .FERRERO TLD is a closed Brand new gTLD operated by Ferrero Trading Lux S.A. Protections: Ferrero Trading Lux S.A. for the .FERRERO TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Ferrero Trading Lux S.A. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .FERRERO is identical to a qualifying registered trademark; 2. .FERRERO is not a Generic String, as this is defined in Specification 11; 3. .FERRERO TLD has developed and will implement a closed registration policy for .FERRERO that requires that all domain names in the .FERRERO TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .FERRERO TLD will clearly publish this registration policy; 5. .FERRERO TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .FERRERO TLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that .FERRERO TLD is a proprietary space in which all second-level domains in the TLD are being operated by Ferrero Trading Lux S.A., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this notice, Ferrero Trading Lux S.A. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-18	Ferrero Trading Lux S.A.	Yes
film	ng	View Comments 2015-12-04	2015-12-05	View Mitigation film Mitigation By Motion Picture Domain Registry .film Mitigation Proposed Measure to Avoid Confusion .film is a generic TLD for the film industry. While .film is an open TLD, registration of domain names is limited to members of the film community as described in the Registration Policy. The proposed protections to avoid confusion with country codes at the second level outlined below specifically apply to: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw Protections: Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following: 1. Registry Operator will commit to: a. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government of a related country code, and provide a written report in response; and b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS. Furthermore, contained within our Acceptable Use Policy for the .film TLD is the following text: “…The Registrant of a domain name, as recorded in the Registry Service, will be responsible for: a. the use of their domain name; b. ensuring that the use of the domain name, where that domain name is a two letter Label that corresponds to a country code described in the ISO 3166-1 alpha-2 standard, avoids confusion with the corresponding country code;…” Should a Registrant fail to comply with the Acceptable Use Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so. 2016-04-14	Motion Picture Domain Registry	No
final	ng	View Comments 2015-12-04	2015-12-05	View Mitigation final Mitigation By Núcleo de Informação e Coordenação do Ponto BR - NIC.br Here follows the measures to avoid confusion submitted by NIC.br for its gTLDs .bom and .final are attached. We note the incorrect usage of the word "mitigation" in ICANN 2-char website since it's not what is prescribed in the registry agreement. .bom and .final are Portuguese words and the target market for such domains is mostly Brazil, the largest Portuguese speaking country in the world, although not restricted to Brazilians. We divided our comment into 3 sets of 2-letter combinations. Set 1: ci, cn, eg, il, sg ========================= Although we do not perceive any of these combinations as confusing, we won't file measures for these combinations at this time. We reserve the right to refile for these combinations in the future, as they might be referenced in the yet to be published registration policies. Set 2: in, it, me ================= Although not a native language, most Internet users in Brazil have at least a rudimentary understanding of the English language. The 3 2-letter combinations in this set are incredibly common words of the English language that are known even by less skilled Internet users. Also of notice is that the word "it" is also known as the acronym "IT" for Information Technology; IT specialists have a higher understanding of English than the average Internet user and commonly see "IT" as referencing their area of expertise. Considering this, we understand that no further measures to avoid confusion with these combination are required. Set 3: pt ========= pt is not only the country designation for Portugal, it's also the language designation in ISO 639-1 code for the Portuguese language. A myriad of websites use the form pt.example.com or example.com/pt for their Portuguese versions, which makes pt most known for Internet users as a language designator rather than a country designator. We note that this reasoning has already been accepted in RSEP2014007 for all ISO 639-1 and 639-2 codes, and is even more applicable to this context considering it being the native language of the target registrants and the likely target users of such domains. "PT" is also widely recognized in Brazil for the acronym of the Workers's Party ("Partido dos Trabalhadores"), the ruling party in Brazil since 2002. "PT" is also known in the Brazil, and possibly other Portuguese speaking countries, as an abbreviation for "Ponto" (dot). In telegrams or telex messages of the previous century, it was used to replace "Ponto" due to having less letters at a time each character was costly to transmit. "PT" is also commonly used as acronym of "Perda Total", which is a total loss of an insured property (usually a car). This become a slang used not only in the insurance business but to mean that anything was beyond repair, or even to mean that a person was totally drunk. Considering the many uses of the 2-char combination 'pt', it would be surprising for someone to understand it as a reference to Portugal or .pt domains, and we understand that no further measures to avoid confusion with this 2-char combination are required. 2016-04-22	Núcleo de Informação e Coordenação do Ponto BR - NIC.br	No
finance	ng	View Comments 2015-12-04	2015-12-05	View Mitigation finance Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
financial	ng	View Comments 2015-12-04	2015-12-05	View Mitigation financial Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
fire	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fire 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
firestone	ng	View Comments 2015-12-04	2015-12-05	View Mitigation firestone Mitigation By Bridgestone Corporation Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: .firestone is a closed Brand new gTLD operated by Bridgestone Corporation Protections: Bridgestone Corporation for the .firestone TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Bridgestone Corporation will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .firestone is identical to a qualifying registered trademark; 2. .firestone is not a Generic String, as this is defined in Specification 11; 3. .firestone TLD has developed and will implement a closed registration policy for .firestone that requires that all domain names in the .firestone TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .firestone TLD will clearly publish this registration policy; 5. .firestone TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .firestone TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .firestone TLD is a proprietary space in which all second-level domains in the TLD are being operated by Bridgestone Corporation, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this Bridgestone Corporation confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-25	Bridgestone Corporation	Yes
firmdale	ng	View Comments 2015-12-04	2015-12-05			No
fish	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fish Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
fishing	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fishing 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
fit	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fit 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
fitness	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fitness Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
flickr	ng	View Comments 2015-12-04	2015-12-05	View Mitigation flickr Mitigation By Yahoo! Domain Services Inc. .FLICKR TLD is a closed Brand new gTLD operated by Yahoo! Domain Services Inc. Protections: Yahoo! Domain Services Inc. for the .FLICKR TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Yahoo! Domain Services Inc. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .FLICKR is identical to a qualifying registered trademark; 2. .FLICKR is not a Generic String, as this is defined in Specification 11; 3. .FLICKR TLD has developed and will implement a closed registration policy for .FLICKR that requires that all domain names in the .FLICKR TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .FLICKR TLD will clearly publish this registration policy; 5. .FLICKR TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .FLICKR TLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that .FLICKR TLD is a proprietary space in which all second-level domains in the TLD are being operated by Yahoo! Domain Services Inc., its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this notice, Yahoo! Domain Services Inc. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-12	Yahoo! Domain Services Inc.	Yes
flights	ng	View Comments 2015-12-04	2015-12-05	View Mitigation flights Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
florist	ng	View Comments 2015-12-04	2015-12-05	View Mitigation florist Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
flowers	ng	View Comments 2015-12-04	2015-12-05			No
flsmidth	ng	View Comments 2015-12-04	2015-12-05			Yes
foo	ng	View Comments 2015-12-04	2015-12-05	View Mitigation foo Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	No
football	ng	View Comments 2015-12-04	2015-12-05	View Mitigation football Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
forex	ng	View Comments 2015-12-04	2015-12-05	View Mitigation forex Mitigation By dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"] Please find attached a document which outlines the Registry's plans to avoid confusion in respect of the below TLDs: .Markets .Trading .Forex .Broker .Spreadbetting .CFD View Documents 2016-04-21	dotBroker Registry, dotCFD Registry, dotForex Registry, dotMarkets Registry, dotSpreadbetting Registry, dotTrading Registry [collectively, the "Boston Ivy Registry"]	No
forsale	ng	View Comments 2015-12-04	2015-12-05	View Mitigation forsale Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
foundation	ng	View Comments 2015-12-04	2015-12-05	View Mitigation foundation Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
fox	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fox Mitigation By FOX Registry, LLC Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: .FOX TLD is a closed Brand new gTLD operated by FOX Registry, LLC Protections: FOX Registry, LLC for the .FOX TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that FOX Registry, LLC will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .FOX is identical to a qualifying registered trademark; 2. .FOX is not a Generic String, as this is defined in Specification 11; 3. .FOX TLD has developed and will implement a closed registration policy for .FOX that requires that all domain names in the .FOX TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .FOX TLD will clearly publish this registration policy; 5. .FOX TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .FOX TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .FOX TLD is a proprietary space in which all second-level domains in the TLD are being operated by FOX Registry, LLC, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this FOX Registry, LLC confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-21	FOX Registry, LLC	Yes
frl	ng	View Comments 2015-12-04	2015-12-05	View Mitigation frl Mitigation By Ewout de Graaf 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. Furthermore, .frl acceptable use policy contains definitions and measures to avoid confusion between the use of an .frl domain name and country codes listed in the ISO-3166 list of 2-letter country codes. Please review attached document for more information. View Documents 2016-04-25	Ewout de Graaf	No
fund	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fund Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
furniture	ng	View Comments 2015-12-04	2015-12-05	View Mitigation furniture Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
futbol	ng	View Comments 2015-12-04	2015-12-05	View Mitigation futbol Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
fyi	ng	View Comments 2015-12-04	2015-12-05	View Mitigation fyi Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
gallery	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gallery Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
gallup	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gallup Mitigation By Gallup, Inc. Proposed Measure to Avoid Confusion—Brand TLD (Specification 13) Provide a brief explanation of the TLD: [Registry Operator] has applied for .[TLD] to run a closed .brand environment. Protections [REGISTRY OPERATOR] for the .[TLD] TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the [Registry Operator] will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .[TLD] is identical to a qualifying registered trademark; 2. .[TLD] is not a Generic String, as this is defined in Specification 11; 3. .[TLD] TLD has developed and will implement a closed registration policy for .[TLD] that requires that all domain names in the .[TLD] TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .[TLD] TLD will clearly publish this registration policy; 5. .[TLD] TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .[TLD] TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .[TLD] TLD is a proprietary space in which all second-level domains in the TLD are being operated by [REGISTRY OPERATOR], its Affiliates and Trademark Licensees and not the [GOVERNMENT] or the corresponding country code operator. By this [LETTER] [REGISTRY OPERATOR] confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-18	Gallup, Inc.	Yes
game	ng	View Comments 2015-12-04	2015-12-05			No
garden	ng	View Comments 2015-12-04	2015-12-05	View Mitigation garden 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
gea	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gea Mitigation By GEA Group Aktiengesellschaft .GEA Mitigation .GEA mitigation measures apply across all two character labels By GEA Group Aktiengesellschaft .GEA TLD is a closed Brand new gTLD operated by GEA Group Aktiengesellschaft. Protections GEA Group Aktiengesellschaft for the .GEA TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that GEA Group Aktiengesellschaft will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: 1. .GEA is identical to a qualifying registered trademark; 2. .GEA is not a Generic String, as this is defined in Specification 11; 3. .GEA TLD has developed and implement a closed registration policy for .GEA that requires that all domain names in the .GEA TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees; 4. As required under the Registry Agreement, the .GEA TLD is clearly publishing this registration policy; 5. .GEA TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13. Compliance with Specification 13 prohibits the .GEA TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .GEA TLD is a proprietary space in which all second-level domains in the TLD are being operated by GEA Group Aktiengesellschaft, its Affiliates and Trademark Licensees and not the government or the corresponding country code operator. By this GEA Group Aktiengesellschaft confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13. 2016-04-19	GEA Group Aktiengesellschaft	Yes
genting	ng	View Comments 2015-12-04	2015-12-05			Yes
gift	ng	View Comments 2015-12-04	2015-12-05			No
gifts	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gifts Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
gives	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gives Mitigation By United TLD Holdco Please see attached PDF on behalf of United TLD Holdco View Documents 2016-04-25	United TLD Holdco	No
giving	ng	View Comments 2015-12-04	2015-12-05			No
glass	ng	View Comments 2015-12-04	2015-12-05	View Mitigation glass Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
global	ng	View Comments 2015-12-04	2015-12-05	View Mitigation global Mitigation By Dot GLOBAL Domain Registry Limited ABOUT .GLOBAL .GLOBAL operates an open registration policy with no restrictions. .Global is a clearly defined name path for organisations large and small who wish to demonstrate a global presence, or promote global services and products. The Registry Operator has an Acceptable Use Policy (http://go.global/registry-policies/aup/) that prevents abusive use of .GLOBAL domain names which creates security and stability issues for the Registry, Registrars and Registrants – as well as for users of the Internet in general. The Registry Operator actively monitors the .GLOBAL namespace for abuse and suspicious behaviour using a third party solution. In co-operation with Registrars, .GLOBAL takes action when abuse or suspicious behaviour is detected. Protections Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the following: Registry Operator will commit to: A. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government Cote D'ivoire (ci), China (cn), Egypt (eg), Israel (il), India (in), Italy(it), Montenegro(me), Portugal (pt) and Singapore (sg), 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-19	Dot GLOBAL Domain Registry Limited	No
globo	ng	View Comments 2015-12-04	2015-12-05	View Mitigation globo Mitigation By Globo Comunicação e Participações SA .globo is an exclusive-use TLD for the Globo media conglomerate, based in Brazil. Globo Comunicações e Participações SA[Globo], for the .globo gTLD[TLD], has applied for and been granted an exemption to the registry operator code of conduct under Specification 9 to the Registry Agreement. This code of conduct exemption already contractually requires that [Globo] will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following: • Developing and implementing a closed registration policy for .globo that requires that all domain names in the TLD be registered and used by Registry Operator and its affiliates; • Clearly publishing this registration policy on Registry Operator’s homepage for .globo at http://nic.globo; and • Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of .globo’s qualification for an exemption to the Registry Operator Code of Conduct. This publicly available registration and usage policy prevent governments from registering domains in the .globo TLD. It clearly designates to the public that .globo is a proprietary space in which all second-level domains in the TLD are and will be operated by [Globo] and not a government, a ccTLD or a reference to a country. 2016-04-22	Globo Comunicação e Participações SA	No
gmail	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gmail Mitigation By Charleston Road Registry Inc. (d/b/a Google Registry) Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes. View Documents 2016-04-22	Charleston Road Registry Inc. (d/b/a Google Registry)	Yes
gold	ng	View Comments 2015-12-04	2015-12-05	View Mitigation gold Mitigation By Donuts Inc. Attached. View Documents 2016-04-25	Donuts Inc.	No
goldpoint	ng	View Comments 2015-12-04	2015-12-05	View Mitigation goldpoint 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

ng Comments

By Nkiru Ebenmelu, GAC Rep, Nigerian Communications Commission

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

Two-Character Letter/Letter Label Comments and Mitigation Measures

dance Mitigation

date Mitigation

dating Mitigation

datsun Mitigation

deal Mitigation

deals Mitigation

degree Mitigation

delivery Mitigation

dell Mitigation

deloitte Mitigation

delta Mitigation

democrat Mitigation

dental Mitigation

dentist Mitigation

design Mitigation

diamonds Mitigation

digital Mitigation

direct Mitigation

directory Mitigation

discount Mitigation

dnp Mitigation

docs Mitigation

dog Mitigation

domains Mitigation

download Mitigation

drive Mitigation

dunlop Mitigation

dvag Mitigation

dvag Mitigation

education Mitigation

email Mitigation

emerck Mitigation

energy Mitigation

engineer Mitigation

engineering Mitigation

enterprises Mitigation

epson Mitigation

equipment Mitigation

estate Mitigation

events Mitigation

exchange Mitigation

expert Mitigation

exposed Mitigation

express Mitigation

fage Mitigation

fail Mitigation

faith Mitigation

family Mitigation

farm Mitigation

fashion Mitigation

fast Mitigation

ferrero Mitigation

film Mitigation

final Mitigation

finance Mitigation

financial Mitigation

fire Mitigation

firestone Mitigation

fish Mitigation

fishing Mitigation

fit Mitigation

fitness Mitigation

flickr Mitigation

flights Mitigation

florist Mitigation

foo Mitigation

football Mitigation

forex Mitigation

forsale Mitigation

foundation Mitigation

fox Mitigation

frl Mitigation

fund Mitigation

furniture Mitigation

futbol Mitigation

fyi Mitigation

gallery Mitigation

gallup Mitigation

garden Mitigation