Skip to main content
Resources

Two-Character Letter/Letter Label Comments and Mitigation Measures

As of 13 December 2016, this page is no longer active. Please visit here for more information.

For comments submitted before 6 October 2015, view the archive of comments received.

Download Excel
TLD  Two
Characters  		Comments from GovernmentLast
updated  		RO Mitigation PlanRO NameBRAND TLD
citytwView Comments
2015-10-14
2015-12-02View Mitigation

city Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

clinique Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.Yes
cloudtwView Comments
2015-10-14
2015-12-02View Mitigation

cloud Mitigation

By Aruba PEC SpA

.cloud proposal for Mitigation Measures to Avoid Confusion in the use of domain names corresponding to ccTLDs

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, the Registry Operator considers the issue of domain name used in a way that generates confusion to be already covered in its Registration Policies (available for review at https://www.get.cloud/policies.aspx), for example in:

9.1 [...] Without limiting any other agreement or policy, by submitting an Application for a domain name an Applicant will be deemed to have warranted that:
[...]
d) it is not submitting the Application or Domain Name Registration request and, upon registration, will not use the Domain Name for an unlawful purpose, contrary to public policy or morality, for offensive purposes, to mislead the public and/or contrary to good and fair business practices;

Should a Registrant fail to comply with the .cloud Registration Policies, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, have an obligation to avoid misleading the public by generating confusion also with two letter country codes and there are clear penalties for any failure to do so.

Registry Operator is however also open to further clarify this point by including in its Registration Policies a specific requirement for Registrants of domain names that are two letter Labels that correspond to a country code described in the ISO 3166-1 alpha-2 standard not to use them in a manner that generates confusion with the corresponding country code.



2016-04-25

Aruba PEC SpANo
clubmedtwView Comments
2015-10-14
2015-12-02View Mitigation

clubmed Mitigation

By Club Méditerranée S.A.

Provide a brief explanation of the TLD:
Club Méditerranée S.A. has applied for .CLUBMED to run a closed .brand environment.

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

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


2016-04-25

Club Méditerranée S.A.Yes
collegetwView Comments
2015-10-14
2015-12-02No
commbanktwView Comments
2015-10-14
2015-12-02View Mitigation

commbank Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes
countrytwView Comments
2015-10-14
2015-12-02View Mitigation

country Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
couponstwView Comments
2015-10-14
2015-12-02View Mitigation

coupons Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

cuisinella Mitigation

By SALM S.A.S.

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

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


2016-04-25

SALM S.A.S.Yes
dealtwView Comments
2015-10-14
2015-12-02View 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
deloittetwView Comments
2015-10-14
2015-12-02View 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 TohmatsuYes
deltatwView Comments
2015-10-14
2015-12-02View 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
desitwView Comments
2015-10-14
2015-12-02No
docstwView Comments
2015-10-14
2015-12-02View 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
dogtwView Comments
2015-10-14
2015-12-02View Mitigation

dog Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
dunloptwView Comments
2015-10-14
2015-12-02View 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 CompanyYes
expresstwView Comments
2015-10-14
2015-12-02View Mitigation

express Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
familytwView Comments
2015-10-14
2015-12-02View 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
fanstwView Comments
2015-10-14
2015-12-02No
filmtwView Comments
2015-10-14
2015-12-02View 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 RegistryNo
firetwView Comments
2015-10-14
2015-12-02View 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
firestonetwView Comments
2015-10-14
2015-12-02View 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 CorporationYes
forextwView Comments
2015-10-14
2015-12-02View 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
fyitwView Comments
2015-10-14
2015-12-02View Mitigation

fyi Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
galluptwView Comments
2015-10-14
2015-12-02View 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
gentingtwView Comments
2015-10-14
2015-12-02Yes
goldtwView Comments
2015-10-14
2015-12-02View Mitigation

gold Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

golf Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

goodyear Mitigation

By The Goodyear Tire & Rubber Company

Brief explanation of the TLD: The Goodyear Tire & Rubber Company has applied for .goodyear to run a closed .brand environment.
Protections
The Goodyear Tire & Rubber Company for the .goodyear 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. .goodyear is identical to a qualifying registered trademark;
2. .goodyear is not a Generic String, as this is defined in Specification 11;
3. .goodyear TLD has developed and will implement a closed registration policy for .goodyear that requires that all domain names in the .goodyear TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .goodyear TLD will clearly publish this registration policy;
5. .goodyear TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.
Compliance with Specification 13 prohibits the .goodyear TLD from registering domain names to unaffiliated third parties and thus clearly designate to the public that .goodyear 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 CompanyYes
hamburgtwView Comments
2015-10-14
2015-12-02View Mitigation

hamburg Mitigation

By Hamburg Top-Level-Domain GmbH

Proposed Measures to Avoid Confusion within the Community-based GeoTLD .HAMBURG 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

“.HAMBURG is the top-level domain of the Community of Hamburg in the Internet. The local domain names available with the .HAMBURG 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 .HAMBURG domain names strengthen the feeling of community amongst Hamburgers, improve communication and make interaction easier, thus providing a stimulus for innovation and development. Both for Hamburgers and for non-Hamburgers, Hamburg 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 .HAMBURG, the Registry Operator Hamburg Top-Level-Domain GmbH has implemented a restricted registration policy for .HAMBURG 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/1351?t:ac=1351):

Registry Operator developed and implemented a restricted registration policy and enforces this restricted Registration Policy for .HAMBURG including:

Eligibility Requirements: .HAMBURG is intended to serve the community of the Hamburgers in general, the group of eligible registrants is limited. Exclusively eligible to register a domain name under the top-level domain .HAMBURG 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 metropolitan area of Hamburg, verifiable by

- their residence or second home, office or place of business, a branch or permanent establishment in the metropolitan area of Hamburg, or
- a contact listed in the Whois database with a domicile in the metropolitan area of Hamburg, 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 .HAMBURG 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.

Content and Use Requirements: The contents of websites under .HAMBURG must be accessible under a domain directly related to the registration criteria of .HAMBURG.

The Registry has in its discretion developed restrictions on the content and use of any domain name. Such restrictions apply to any domain name registration that occurs after such restrictions come into effect.

Each domain name must, within one year following the date of registration, and thereafter throughout the term of the domain name, be used as the domain name for a website displaying Hamburg Community related content relevant to the domain name, or in such other manner (such as email) that the Registry may approve after review. Domain names used as contemplated above may resolve directly to the relevant website or be forwarded or redirected to another domain name displaying content relevant to the domain name.

Legal Safeguards, Enforcement and continued Compliance: This designation of .HAMBURG to the .HAMBURG 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 Registry Operator will, from time to time in its sole discretion or upon evidence or advice, but at least once a year, 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 a timeframe 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. The Registry is entitled to lock, cancel, initiate the gTLD-deletion cycle or transfer domain names that do not meet the registration criteria if certain circumstances appear.

Those policies have been clearly published on Registry Operator’s homepage for .HAMBURG.

This registration and usage policy would prevent governments from registering domains in the .HAMBURG TLD. It would clearly designate to users that .HAMBURG was a restricted space in which all second-level domains were registered by eligible Registrants.


2016-04-25

Hamburg Top-Level-Domain GmbHNo
hermestwView Comments
2015-10-14
2015-12-02View Mitigation

hermes Mitigation

By HERMES INTERNATIONAL

.hermes is a closed top-level domain name for the sole and exclusive use of HERMES INTERNATIONAL.

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


2016-04-11

HERMES INTERNATIONALYes
hockeytwView Comments
2015-10-14
2015-12-02View Mitigation

hockey Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

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

hyundai Mitigation

By Hyundai Motor Company

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

Provide a brief explanation of the TLD: .hyundai is a closed Brand new gTLD operated by Hyundai Motor Company

Protections:

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

1. .hyundai is identical to a qualifying registered trademark;

2. .hyundai is not a Generic String, as this is defined in Specification 11;

3. .hyundai TLD has developed and will implement a closed registration policy for .hyundai that requires that all domain names in the .hyundai TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;

4. As required under the Registry Agreement, the .hyundai TLD will clearly publish this registration policy;

5. .hyundai TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

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


2016-04-25

Hyundai Motor Company Yes
imdbtwView Comments
2015-10-14
2015-12-02View Mitigation

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

itv Mitigation

By ITV Services Limited

.ITV TLD is a closed Brand new gTLD operated by ITV Services Limited

Protections:

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

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

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


2016-04-12

ITV Services LimitedYes
javatwView Comments
2015-10-14
2015-12-02Yes
jewelrytwView Comments
2015-10-14
2015-12-02View Mitigation

jewelry Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
jlltwView Comments
2015-10-14
2015-12-02Yes
jmptwView Comments
2015-10-14
2015-12-02View Mitigation

jmp Mitigation

By Karen L. Day

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


View Documents
2016-05-06

Karen L. DayYes
kerryhotelstwView Comments
2015-10-14
2015-12-02No
kerrylogisticstwView Comments
2015-10-14
2015-12-02No
kerrypropertiestwView Comments
2015-10-14
2015-12-02No
kfhtwView Comments
2015-10-14
2015-12-02No
kiatwView Comments
2015-10-14
2015-12-02View Mitigation

kia Mitigation

By KIA MOTORS CORPORATION

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

Provide a brief explanation of the TLD:

.kia is a closed Brand new gTLD operated by KIA MOTORS CORPORATION

Protections:

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

1. .kia is identical to a qualifying registered trademark;

2. .kia is not a Generic String, as this is defined in Specification 11;

3. .kia TLD has developed and will implement a closed registration policy for .kia that requires that all domain names in the .kia TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;

4. As required under the Registry Agreement, the .kia TLD will clearly publish this registration policy;

5. .kia TLD will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

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


2016-04-25

KIA MOTORS CORPORATION Yes
kindletwView Comments
2015-10-14
2015-12-02View Mitigation

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

kpmg Mitigation

By KPMG International Cooperative

.KPMG TLD is a closed Brand new gTLD operated by KPMG International Cooperative

Protections:

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

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

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


2016-04-04

KPMG International CooperativeYes
krdtwView Comments
2015-10-14
2015-12-02No
kuokgrouptwView Comments
2015-10-14
2015-12-02No
lamertwView Comments
2015-10-14
2015-12-02Yes
lasalletwView Comments
2015-10-14
2015-12-02No
lawtwView Comments
2015-10-14
2015-12-02View Mitigation

law Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
lindetwView Comments
2015-10-14
2015-12-02View Mitigation

linde Mitigation

By Linde Aktiengesellschaft

Provide a brief explanation of the TLD:
Linde Aktiengesellschaft has applied for .LINDE to run a closed .brand environment.

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

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


2016-04-25

Linde AktiengesellschaftYes
livetwView Comments
2015-10-14
2015-12-02View Mitigation

live Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

lotte Mitigation

By Lotte Holdings Co., Ltd.

.lotte 2 Letter Codes Mitigation Plan

To address the confusion concerns cited by governments regarding the use of the second-level domains in the .lotte TLD, Lotte Holdings Co., Ltd. will implement a closed registration policy for .lotte that mitigates the potential confusion. To these ends, Lotte Holdings Co., Ltd. commits to the following:

・Developing and implementing a closed registration policy for .lotte that requires that all domains name in the TLD be registered and used by Lotte Holding Co., Ltd., its affiliates, or its trademark licensees;

・Clearly publishing this registration policy on Registry Operator`s homepage for the .lotte TLD at “nic.lotte”.

・Referring to this registration policy in registry Operator`s Registry-Registrar Agreement with all appointed preferred registrars for the .lotte TLD.

・Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of .lotte`s qualification for Specification 13; and

・Using all domain names in the .lotte TLD in association with Lotte`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the .lotte TLD. It would therefore clearly designate to the public that .lotte was a proprietary space in which all second-level domains in the TLD were being operated by Lotte Holdings Co., Ltd. and not governments.


2016-04-25

Lotte Holdings Co., Ltd.Yes
mantwView Comments
2015-10-14
2015-12-02View Mitigation

man Mitigation

By MAN SE

.man is a closed Brand TLD for the sole and exclusive use of MAN SE.

Protections
MAN SE (Registry Operator) for the .man 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:

.man is identical to a qualifying registered trademark;
.man is not a Generic String, as this is defined in Specification 11;
Registry Operator has developed and implemented a closed registration policy for .man that requires that all domain names in the .man TLD be registered only by MAN SE, 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 .man 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 text MAN SE confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


2016-04-21

MAN SEYes
marketstwView Comments
2015-10-14
2015-12-02View Mitigation

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

mba Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

melbourne Mitigation

By The Crown in right of the State of Victoria, represented by its Department of State Development, Business and Innovation

Proposed Measure to Avoid Confusion

A brief explanation of the TLD:

.melbourne is a geographic TLD for the city of Melbourne, Australia and the the State Government of Victoria is the designated ‘Registry Operator’. While .melbourne is an open TLD, registration of domain names is limited to Victorian residents and businesses, and other entities with an interest in the state of Victoria, Australia as described in the Registration Policy.

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

Protections

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

Furthermore, contained within our Acceptable Use Policy for the .melbourne 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-03-31

 The Crown in right of the State of Victoria, represented by its Department of State Development, Business and InnovationNo
miamitwView Comments
2015-10-14
2015-12-02View Mitigation

miami Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
monstertwView Comments
2015-10-14
2015-12-02No
movietwView Comments
2015-10-14
2015-12-02View Mitigation

movie Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

nagoya Mitigation

By GMO Registry

About .NAGOYA

.nagoya is a GeoTLD for the city of Nagoya, Japan, operated by GMO Registry, Inc.
The purpose of .nagoya is to promote Nagoya 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, .NAGOYA 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 .NAGOYA 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 .NAGOYA TLD is the following text:

All Applicants, all Domain Name Registrants, and any party submitting a Domain Name registration request represents and warrants that:
− to its knowledge, the registration of the Domain Name mentioned in the Application
or Domain Name Registration Request will not infringe upon or otherwise violate the
rights of any third party;
− will not register a domain name for the purpose of distributing malware, abusively
operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent
or deceptive practices, counterfeiting or otherwise engaging in activity contrary to
applicable laws or regulations;

Should a Registrant fail to comply with the Acceptable Use Policy, the domain name may be canceled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-25

GMO RegistryNo
navytwView Comments
2015-10-14
2015-12-02View Mitigation

navy Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

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

netbank Mitigation

By Commonwealth Bank of Australia

Refer measures in attached PDF document


View Documents
2016-04-13

Commonwealth Bank of AustraliaYes
nikontwView Comments
2015-10-14
2015-12-02Yes
nowtwView Comments
2015-10-14
2015-12-02View Mitigation

now Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes.

ARSI will commit to:
1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above.


2016-04-25

Amazon Registry Services, Inc. No
nrwtwView Comments
2015-10-14
2015-12-02View Mitigation

nrw Mitigation

By Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbH

Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any relevant government and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
nyctwView Comments
2015-10-14
2015-12-02View Mitigation

nyc Mitigation

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

Proposed Measure to Avoid Confusion

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

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

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

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

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

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


2016-04-25

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

obi Mitigation

By OBI Group Holding SE & Co. KGaA

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

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


2016-04-25

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

omega Mitigation

By The Swatch Group Ltd

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

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

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


2016-04-25

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

online Mitigation

By Radix

Dear ICANN,

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

Protections

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

1. Radix will commit to:

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

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

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

Thank you.


2016-04-25

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

orange Mitigation

By Orange Brand Services Limited

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

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

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


2016-04-25

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

pay Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes.

ARSI will commit to:
1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above.


2016-04-25

Amazon Registry Services, Inc. No
pettwView Comments
2015-10-14
2015-12-02View Mitigation

pet Mitigation

By Afilias

Afilias has reviewed the comments submitted for the release of certain 2 character labels. We have taken these comments into consideration and will will continue to block the respective labels at the second level until further notice to avoid confusion.


2016-04-20

AfiliasNo
pharmacytwView Comments
2015-10-14
2015-12-02View Mitigation

pharmacy Mitigation

By National Association of Boards of Pharmacy

Background

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

Implementation Plan to Avoid Confusion

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

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

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

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

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


View Documents
2016-04-25

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

philips Mitigation

By Koninklijke Philips N.V.

Registry Operator will not register two letter SLDs that are equal to ccTLDs under its gTLD, unless:
- the corresponding country has given general consent to register these SLDs, or
- that Registry Operator has obtained authorization of the competent authority of that corresponding country to register the two letter SLD under its TLD..

Registry Operator will not register two letter SLDs under its TLD that are equal to ccTLDs when the corresponding country has objected to these registrations.


2016-03-08

Koninklijke Philips N.V.Yes
plustwView Comments
2015-10-14
2015-12-02View Mitigation

plus Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

porn Mitigation

By ICM Registry

Protections

Registry Operator understands the concern that confusion may arise, and in order to avoid such confusion is willing to offer the following:

1. Registry Operator will commit to:
a. investigate any reports of misuse, including misleading or deceptive conduct, including those from any governments, and provide a written report in response; and
b. where, in Registry Operator’s sole opinion, misuse has occurred, cause the domain name’s records to be removed from the DNS.

Furthermore, we have the following Anti-Abuse Policy:

Registry has the right, pursuant to its Registry-Registrant Agreement, to immediately deny, cancel, terminate, suspend, lock, hold, or transfer any domain name and/or registration to ensure registrant’s compliance with the following Anti-Abuse Policy.

1. Accurate Registration Information
Registrant represents and warrants to have provided current, complete, and accurate information in connection with its registration and agrees to correct and update this information to ensure that it remains current, complete, and accurate throughout the term of any resulting registration in a TLD. Registrant’s obligation to provide current, accurate, and complete information is a material element of the Registry-Registrant Agreement, and the registry reserves the right to immediately deny, cancel, terminate, suspend, lock, or transfer any registration if it determines, in its sole discretion, that the information is materially inaccurate.

2. Child Protection Labeling
Registrant understands that Registry Operator may label the sites in the TLD and any site to which such sites are automatically redirected irrespective of the top-level domain for child protection purposes; registrant consents to such labeling.

3. Prohibition on Child Abuse Images and Conduct or Content Designed to Suggest the Presence of Child Abuse Images
The term “child abuse images” is defined as any photograph, film, video, picture, or computer or computer-generated image or picture, whether made or produced by electronic, mechanical, or other means, depicting child sexual abuse as stated in the United Nations Convention on the Rights of the Child. Registrant’s sites in the TLD shall not display any child abuse images. Registrant’s sites in the TLD shall not engage in practices that are designed to suggest the presence of child abuse images, including, without limitation, the use of meta-tags for that purpose. Registry Operator will refer any sites in a TLD that are reported to the Registry Operator to be in violation of this policy to child safety hotlines like the National Center for Missing and Exploited Children (NCMEC), the Internet Watch Foundation (IWF), or the International Association of Internet Hotlines (INHOPE).

4. Prohibition on Abusive Registrations
No registrant may register an abusive second-level domain name in the TLD including, without limitation, domain names that infringe the intellectual property rights of a third party, including common law trademark rights; domain names that are obvious variants of well-known trademarks not belonging to the registrant; or domain names that suggest the presence of child abuse images.

5. Prohibition on Malicious Conduct
No registrant shall use or permit use of a domain name in the TLD for or in connection with email spoofing, phishing, spam, or other forms of malicious behavior.

6. Ongoing Best Practices Policies
Registry Operator will revise this Anti-Abuse Policy or the Registry-Registrant Agreement to include commercially reasonable best practices policies developed by the International Foundation for Online Responsibility (IFFOR) that are designed to promote responsible business practices related to (i) combating online child abuse images, (ii) facilitating user choice and parental control regarding access to online adult entertainment, (iii) protecting free expression rights, and/or (iv) protecting the privacy, security, and consumer rights of consenting adult consumers of online adult entertainment goods and services; registrant consents to adhere to such policies.

The Registrant of a domain name, as recorded in the Registry Service, will be responsible for:
a. the use of their domain name;
b. ensuring that the use of the domain name, where that domain name is a two letter Label that corresponds to a country code described in the ISO 3166-1 alpha-2 standard, avoids confusion with the corresponding country code;”

Should a Registrant fail to comply with the Anti-Abuse Policy, the domain name may be cancelled, locked, placed on hold, transferred or deleted. Thus all Registrants in the TLD, including ourselves, have an obligation to avoid confusion with two letter country codes and we have clear penalties for any failure to do so.


2016-04-19

ICM Registry No
primetwView Comments
2015-10-14
2015-12-02View Mitigation

prime Mitigation

By Amazon Registry Services, Inc.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the .Brand TLDs .AUDIBLE, .AWS, .FIRE, .IMDB, .KINDLE, .PRIME, .SILK, and .ZAPPOS (collectively, “the .Brand TLDs”) proposes release of the following 2-character letter-letter combinations: : ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw.

ARSI has executed Specification 13 to the Registry Agreement for each of the .Brand TLDs. Specification 13 contractually requires ARSI to apply measures which, in and of themselves, avoid confusion with the country codes corresponding to the 2-character letter-letter combinations listed above, namely:

1. Each of the .Brand TLDs is identical to a qualifying registered trademark;
2. Each of the .Brand TLDs is not a Generic String, as this is defined in Specification 11;
3. ARSI has developed and will implement a registration policy for each of the .Brand TLDs that requires all domain names in each such TLD be registered only by ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates;
4. ARSI will publish the registration policy for each of the .Brand TLDs upon delegation; and
5. ARSI has ensured, and will continue to ensure, its compliance with the registration policy through annual certification of qualification for Specification 13 for each of the .Brand TLDs.

Compliance with Specification 13 clearly designates to the public that the .Brand TLDs are proprietary spaces in which ARSI, its Affiliates, or Trademark Licensees of ARSI or its Affiliates use all second-level domain names. Accordingly, there will be no basis on which a letter-letter domain name registered in any of the .Brand TLDs could be confused with the country codes corresponding to the 2-character letter-letter combinations listed above.


2016-04-25

Amazon Registry Services, Inc.Yes
progressivetwView Comments
2015-10-14
2015-12-02No
protectiontwView Comments
2015-10-14
2015-12-02No
questtwView Comments
2015-10-14
2015-12-02No
rentwView Comments
2015-10-14
2015-12-02View Mitigation

ren Mitigation

By Beijing Qianxiang Wangjing Technology Development Co., Ltd.

.REN Registry Operator understands the concern that confusion may arise, and in order to mitigate such concern is willing to offer the domains with the following:
1. not be used to imply that it is, or represents, the government；
2. investigate any reports of misuse or abusive use, including misleading or deceptive conduct, and provide a written report in response; and
3. in Registry Operator’s sole opinion, if misuse has occurred or been reported, the domain name may be cancelled, locked, placed on hold, transferred or deleted.
Thus all Registrants in the TLDs, including ourselves, have an obligation to avoid confusion with two letter country codes.


View Documents
2016-04-25

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

ruhr Mitigation

By regiodot GmbH & Co. KG

Proposed Measures to avoid confusion


View Documents
2016-04-20

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

run Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

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

rwe Mitigation

By RWE AG

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

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

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


2016-04-25

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

sandvik Mitigation

By Sandvik AB

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

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


2016-04-11

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

sandvikcoromant Mitigation

By Sandvik AB

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

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


2016-04-11

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

sanofi Mitigation

By Sanofi

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

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

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


2016-04-25

SanofiYes
sastwView Comments
2015-10-14
2015-12-02View Mitigation

sas Mitigation

By Karen L. Day

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


View Documents
2016-05-06

Karen L. DayYes
savetwView Comments
2015-10-14
2015-12-02View Mitigation

save Mitigation

By Amazon Registry Services, Inc.

Proposed Release of 2-Character Letter-Letter Combinations in .AUTHOR, .BOT, .BUY, .CALL, .CIRCLE, .COUPON, .DEAL, .FAST, .GOT, .HOT, .JOT, .JOY, .LIKE, .MOI, .NOW, .PAY, .PIN, .READ, .ROOM, .SAFE, .SECURE, .SAVE, .SMILE, .SONG, .SPOT, .TALK, .TUNES, .TUSHU, .WANGGOU, and .xn--rovu88b.

Amazon Registry Services, Inc. (“ARSI”), the Registry Operator for the TLDs listed above (“the TLDs”), proposes release of the following 2-character letter-letter combinations: ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, and tw. ARSI further proposes the following measures to avoid confusion with the corresponding country codes.

ARSI will commit to:
1. Investigate in a timely manner a report by the government of the country, state, or territory for which a 2-character letter-letter combination listed above (ai, bh, bm, ci, cn, eg, il, in, io, it, kr, ky, me, ms, pt, ru, sg, sh, su, tc, or tw) corresponds to its country code, that:
a. the use in any of the TLDs of a domain name consisting of a 2-character letter-letter combination listed above; and
b. corresponds to that government’s country code; and
c. implies or represents that it is, or has the approval of, such government; and
2. Where, in ARSI’s sole opinion, such use has occurred, ARSI, in its sole discretion:
a. will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address such use, or
b. may cause the domain name’s records to be removed from the DNS; and
3. Provide a written response within a commercially reasonable time period.

ARSI’s Acceptable Use Policy for the TLDs will require registrants of a domain name in each of the TLDs to ensure that their use of a 2-character letter-letter combination does not imply or represent that it is, or has the approval of, any government. ARSI will reserve the right to cancel, lock, place on hold, transfer or delete the domain name in accordance with our commitment above.


2016-04-25

Amazon Registry Services, Inc. No
saxotwView Comments
2015-10-14
2015-12-02View Mitigation

saxo Mitigation

By Saxo Bank A/S

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

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


2016-04-08

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

sbs Mitigation

By SPECIAL BROADCASTING SERVICE CORPORATION

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


2016-04-22

SPECIAL BROADCASTING SERVICE CORPORATIONYes

tw Comments

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

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

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

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

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