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
financialsuView Comments
2015-12-07
2016-08-15View Mitigation

financial Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
firesuView Comments
2015-12-07
2016-08-15View 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
firestonesuView Comments
2015-12-07
2016-08-15View 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
firmdalesuView Comments
2015-12-07
2016-08-15No
fishsuView Comments
2015-12-07
2016-08-15View Mitigation

fish Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
fishingsuView Comments
2015-12-07
2016-08-15View Mitigation

fishing Mitigation

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

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


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
fitsuView Comments
2015-12-07
2016-08-15View Mitigation

fit Mitigation

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

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


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
fitnesssuView Comments
2015-12-07
2016-08-15View Mitigation

fitness Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
flickrsuView Comments
2015-12-07
2016-08-15View Mitigation

flickr Mitigation

By Yahoo! Domain Services Inc.

.FLICKR TLD is a closed Brand new gTLD operated by Yahoo! Domain Services Inc.

Protections:

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

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

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


2016-04-12

Yahoo! Domain Services Inc.Yes
flightssuView Comments
2015-12-07
2016-08-15View Mitigation

flights Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
floristsuView Comments
2015-12-07
2016-08-15View Mitigation

florist Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
flowerssuView Comments
2015-12-07
2016-08-15No
flsmidthsuView Comments
2015-12-07
2016-08-15Yes
foosuView Comments
2015-12-07
2016-08-15View Mitigation

foo Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)No
footballsuView Comments
2015-12-07
2016-08-15View Mitigation

football Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
forexsuView Comments
2015-12-07
2016-08-15View 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
forsalesuView Comments
2015-12-07
2016-08-15View Mitigation

forsale Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
foundationsuView Comments
2015-12-07
2016-08-15View Mitigation

foundation Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
foxsuView Comments
2015-12-07
2016-08-15View Mitigation

fox Mitigation

By FOX Registry, LLC

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

Provide a brief explanation of the TLD:

.FOX TLD is a closed Brand new gTLD operated by FOX Registry, LLC

Protections:

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

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

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


2016-04-21

FOX Registry, LLCYes
frlsuView Comments
2015-12-07
2016-08-15View Mitigation

frl Mitigation

By Ewout de Graaf

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

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

Furthermore, .frl acceptable use policy contains definitions and measures to avoid confusion between the use of an .frl domain name and country codes listed in the ISO-3166 list of 2-letter country codes. Please review attached document for more information.


View Documents
2016-04-25

Ewout de GraafNo
fundsuView Comments
2015-12-07
2016-08-15View Mitigation

fund Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
furnituresuView Comments
2015-12-07
2016-08-15View Mitigation

furniture Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
futbolsuView Comments
2015-12-07
2016-08-15View Mitigation

futbol Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
fyisuView Comments
2015-12-07
2016-08-15View Mitigation

fyi Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
gallerysuView Comments
2015-12-07
2016-08-15View Mitigation
View Documents
2016-04-25

Donuts Inc.No
gallupsuView Comments
2015-12-07
2016-08-15View 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
gamesuView Comments
2015-12-07
2016-08-15No
gardensuView Comments
2015-12-07
2016-08-15View Mitigation

garden Mitigation

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

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


2016-04-22

Minds + Machines Group Limited, Bayern Connect GmbH, Minds + Machines GmbHNo
geasuView Comments
2015-12-07
2016-08-15View Mitigation

gea Mitigation

By GEA Group Aktiengesellschaft

.GEA Mitigation

.GEA mitigation measures apply across all two character labels
By GEA Group Aktiengesellschaft

.GEA TLD is a closed Brand new gTLD operated by GEA Group Aktiengesellschaft.

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

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

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

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

4. As required under the Registry Agreement, the .GEA TLD is clearly publishing this registration policy;

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

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






2016-04-19

GEA Group AktiengesellschaftYes
gentingsuView Comments
2015-12-07
2016-08-15Yes
giftsuView Comments
2015-12-07
2016-08-15No
giftssuView Comments
2015-12-07
2016-08-15View Mitigation

gifts Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
givessuView Comments
2015-12-07
2016-08-15View Mitigation

gives Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
givingsuView Comments
2015-12-07
2016-08-15No
glasssuView Comments
2015-12-07
2016-08-15View Mitigation

glass Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
globalsuView Comments
2015-12-07
2016-08-15View Mitigation

global Mitigation

By Dot GLOBAL Domain Registry Limited

ABOUT .GLOBAL

.GLOBAL operates an open registration policy with no restrictions.

.Global is a clearly defined name path for organisations large and small who wish to demonstrate a global presence, or promote global services and products.

The Registry Operator has an Acceptable Use Policy (http://go.global/registry-policies/aup/) that prevents abusive use of .GLOBAL domain names which creates security and stability issues for the Registry, Registrars and Registrants – as well as for users of the Internet in general.

The Registry Operator actively monitors the .GLOBAL namespace for abuse and suspicious behaviour using a third party solution. In co-operation with Registrars, .GLOBAL takes action when abuse or suspicious behaviour is detected.

Protections

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

Registry Operator will commit to:

A. investigate any reports of misuse, including misleading or deceptive conduct, including those from the government Cote D'ivoire (ci), China (cn), Egypt (eg), Israel (il), India (in), Italy(it), Montenegro(me), Portugal (pt) and Singapore (sg), and provide a written report in response; and
B. where, in Registry Operator’s sole opinion, misuse has occurred, registry operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
C. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name.


2016-04-19

Dot GLOBAL Domain Registry LimitedNo
globosuView Comments
2015-12-07
2016-08-15View Mitigation

globo Mitigation

By Globo Comunicação e Participações SA

.globo is an exclusive-use TLD for the Globo media conglomerate, based in Brazil.

Globo Comunicações e Participações SA[Globo], for the .globo gTLD[TLD], has applied for and been granted an exemption to the registry operator code of conduct under Specification 9 to the Registry Agreement. This code of conduct exemption already contractually requires that [Globo] will apply measures which, by their very nature, avoid confusion with the corresponding country code,
namely the following:
• Developing and implementing a closed registration policy for .globo that requires that all domain names in the TLD be registered and used by Registry Operator and its affiliates;
• Clearly publishing this registration policy on Registry Operator’s homepage for .globo at http://nic.globo; and
• Enforcing of this registration policy and ensuring continued compliance, including through annual recertification of .globo’s
qualification for an exemption to the Registry Operator Code of Conduct.
This publicly available registration and usage policy prevent governments from registering domains in the .globo TLD.
It clearly designates to the public that .globo is a proprietary space in which all second-level domains in the TLD are and will be operated by [Globo] and not a government, a ccTLD or a reference to a country.


2016-04-22

Globo Comunicação e Participações SANo
gmailsuView Comments
2015-12-07
2016-08-15View Mitigation

gmail Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)Yes
goldsuView Comments
2015-12-07
2016-08-15View Mitigation

gold Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
goldpointsuView Comments
2015-12-07
2016-08-15View Mitigation

goldpoint Mitigation

By YODOBASHI CAMERA CO.,LTD.

2 Letter Codes Mitigation Plan for YODOBASHI TLDs
(.yodobashi .goldpoint)

To address the confusion concerns cited by governments regarding the use of the second-level domains in the YODOBASHI TLDs,
YODOBASHI CAMERA CO.,LTD. will implement a closed registration policy for YODOBASHI TLDs that mitigates the potential confusion. To these ends, YODOBASHI CAMERA CO., LTD. commits to the following:

・Developing and implementing a closed registration policy for YODOBASHI TLDs that requires that all domains name in the TLDs be registered and used by YODOBASHI CAMERA CO.,LTD., its affiliates, or its trademark licensees;

・Clearly publishing this registration policy on Registry Operator`s homepage for the YODOBASHI TLDs at “nic.yodobashi”, and “nic.goldpoint”.

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

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

・Using all domain names in the YODOBASHI TLDs in association with YODOBASHI`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the YODOBASHI TLDs. It would therefore clearly designate to the public that YODOBASHI TLDs were proprietary spaces in which all second-level domains in the TLDs were being operated by YODOBASHI CAMERA CO., LTD. and not governments.


2016-04-25

YODOBASHI CAMERA CO.,LTD.Yes
golfsuView Comments
2015-12-07
2016-08-15View Mitigation

golf Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
goosuView Comments
2015-12-07
2016-08-15View Mitigation

goo Mitigation

By NTT Resonant Inc.

.goo 2 Letter Codes Mitigation Plan

To address the confusion concerns cited by governments regarding the use of the second-level domains in the .goo TLD, NTT Resonant Inc. will implement a closed registration policy for .goo that mitigates the potential confusion. To these ends, NTT Resonant Inc. commits to the following:

・Developing and implementing a closed registration policy for .goo that requires that all domains name in the TLD be registered and used by NTT Resonant Inc., its affiliates, or its trademark licensees;

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

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

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

・Using all domain names in the .goo TLD in association with NTT Resonant`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the .goo TLD. It would therefore clearly designate to the public that .goo was a proprietary space in which all second-level domains in the TLD were being operated by NTT Resonant Inc. and not governments.


2016-04-25

NTT Resonant Inc.Yes
goodyearsuView Comments
2015-12-07
2016-08-15View 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
googsuView Comments
2015-12-07
2016-08-15View Mitigation

goog 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
googlesuView Comments
2015-12-07
2016-08-15View Mitigation

google Mitigation

By Charleston Road Registry Inc. (d/b/a Google Registry)

Please find attached Google Registry's proposed mechanisms to avoid confusion between the use of two-letter labels in its top level domains and the corresponding country codes.


View Documents
2016-04-22

Charleston Road Registry Inc. (d/b/a Google Registry)Yes
gopsuView Comments
2015-12-07
2016-08-15No
gotsuView Comments
2015-12-07
2016-08-15View Mitigation

got 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
graingersuView Comments
2015-12-07
2016-08-15View Mitigation

grainger Mitigation

By Grainger Registry Services, LLC

.GRAINGER gTLD Confusion Avoidance Plan

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

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

Compliance with Specification 13 prohibits the .GRAINGER gTLD from registering domain names to unaffiliated third parties and thus clearly designates to the public that the .GRAINGER gTLD is a proprietary space in which all second-level domains in the gTLD are being operated by Grainger Registry Services, LLC, its Affiliates and Trademark Licensees and not any government or corresponding country-code TLD operator.

With this submission, Grainger Registry Services, LLC confirms that all registrations of two-letter domain names shall comply with the requirements of Specification 13.


2016-04-25

Grainger Registry Services, LLCYes
graphicssuView Comments
2015-12-07
2016-08-15View Mitigation

graphics Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
gratissuView Comments
2015-12-07
2016-08-15View Mitigation

gratis Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
greensuView Comments
2015-12-07
2016-08-15View Mitigation

green 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
gripesuView Comments
2015-12-07
2016-08-15View Mitigation

gripe Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
guccisuView Comments
2015-12-07
2016-08-15View Mitigation

gucci Mitigation

By Guccio Gucci S.p.a.

.GUCCI TLD is a closed Brand new gTLD operated by Guccio Gucci S.p.a.

Protections:

Guccio Gucci S.p.a. for the .GUCCI TLD has executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that Guccio Gucci S.p.a. will apply measures which, by their very nature, avoid confusion with the corresponding country code, namely the following:

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

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


2016-04-20

Guccio Gucci S.p.a.Yes
guidesuView Comments
2015-12-07
2016-08-15View Mitigation

guide Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
guitarssuView Comments
2015-12-07
2016-08-15No
gurusuView Comments
2015-12-07
2016-08-15View Mitigation

guru Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
hamburgsuView Comments
2015-12-07
2016-08-15View 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
haussuView Comments
2015-12-07
2016-08-15View Mitigation

haus Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
healthcaresuView Comments
2015-12-07
2016-08-15View Mitigation

healthcare Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
helpsuView Comments
2015-12-07
2016-08-15No
heresuView Comments
2015-12-07
2016-08-15View Mitigation

here 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
hermessuView Comments
2015-12-07
2016-08-15View 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
hiphopsuView Comments
2015-12-07
2016-08-15No
hitachisuView Comments
2015-12-07
2016-08-15View Mitigation

hitachi Mitigation

By Hitachi, Ltd.

.hitachi 2 Letter Codes Mitigation Plan

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

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

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

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

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

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

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


2016-04-25

Hitachi, Ltd.Yes
hockeysuView Comments
2015-12-07
2016-08-15View Mitigation

hockey Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
holdingssuView Comments
2015-12-07
2016-08-15View Mitigation

holdings Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
holidaysuView Comments
2015-12-07
2016-08-15View Mitigation

holiday Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
homessuView Comments
2015-12-07
2016-08-15View Mitigation

homes Mitigation

By DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)

See attached document


View Documents
2016-04-26

DERAutos LLC, DERBoats LLC, DERHomes LLC, DERMotorcycles LLC, DERYachts LLC (collective Dominion Registries)No
hondasuView Comments
2015-12-07
2016-08-15View Mitigation

honda Mitigation

By Honda Motor Co.,Ltd

Provide a brief explanation of the TLD:

.honda is a closed Brand new gTLD operated by Honda Motor Co.,Ltd

Protections:

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

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

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

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

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

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

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


2016-04-25

Honda Motor Co.,LtdYes
horsesuView Comments
2015-12-07
2016-08-15View Mitigation

horse 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
hostsuView Comments
2015-12-07
2016-08-15View Mitigation

host 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
hostingsuView Comments
2015-12-07
2016-08-15No
hotsuView Comments
2015-12-07
2016-08-15View 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
hotmailsuView Comments
2015-12-07
2016-08-15View Mitigation

hotmail Mitigation

By Microsoft Corporation

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

Provide a brief explanation of the TLD:

.HOTMAIL TLD is a closed Brand new gTLD operated by Microsoft Corporation

Protections:

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

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

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


2016-04-05

Microsoft CorporationYes
housesuView Comments
2015-12-07
2016-08-15View Mitigation

house Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
howsuView Comments
2015-12-07
2016-08-15View Mitigation

how 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
hsbcsuView Comments
2015-12-07
2016-08-15View Mitigation

hsbc Mitigation

By HSBC Holdings PLC

.HSBC TLD is a closed Brand new gTLD operated by HSBC Holdings PLC

Protections:

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

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

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


2016-04-20

HSBC Holdings PLCYes
hyundaisuView Comments
2015-12-07
2016-08-15View 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
icbcsuView Comments
2015-12-07
2016-08-15View Mitigation

icbc Mitigation

By Industrial and Commercial Bank of China Limited

A Proposal to Minimize the Potential Likelihood of Confusion in Connection with the Allocation of Specific Two Character Domain Names

.ICBC and .工行（xn--estv75g）are trademarks of Industrial and Commercial Bank of China Ltd. The primary use of .ICBC and .工行（xn--estv75g） TLDs will initially be defensive in nature, and provide a trusted, hierarchical and intuitive namespace for business and consumers that use ICBC’s broad range of financial products and services.

Protections

Industrial and Commercial Bank of China Ltd. for the .ICBC/.工行（xn--estv75g） TLD have executed Specification 13 to the Registry Agreement. Specification 13 already contractually requires that the Industrial and Commercial Bank of China Ltd. will apply measures which by their very nature, avoid confusion with the corresponding country code, namely the following:
1. .ICBC/.工行（xn--estv75g ）are identical to a qualifying registered trademark;
2. .ICBC/.工行（xn--estv75g ）are not a Generic String, as this is defined in Specification 11;
3. .ICBC/.工行（xn--estv75g ）TLDs have developed and will implement a closed registration policy for .ICBC/.工行（xn--estv75g ）that requires that all domain names in the .ICBC/.工行（xn--estv75g ）TLD be registered ONLY by Registry Operator, its Affiliates, and its Trademark Licensees;
4. As required under the Registry Agreement, the .ICBC/.工行（xn--estv75g ）TLDs will clearly publish this registration policy;
5. .ICBC/.工行（xn--estv75g ）TLDs will conduct internal reviews at least once per calendar year to ensure continued compliance with Specification 13.

Compliance with Specification 13 prohibits the .ICBC/.工行（xn--estv75g ）TLDs from registering domain names to unaffiliated third parties and thus clearly designate to the public that .ICBC/.工行（xn--estv75g ）TLDs are a proprietary space in which all second-level domains in the TLD are being operated by Industrial and Commercial Bank of China Ltd., its Affiliates and Trademark Licensees and not a government or their corresponding country code operator.

Industrial and Commercial Bank of China Ltd. confirms that all registrations of two letter domain names shall comply with the requirements of Specification 13.


View Documents
2016-04-25

Industrial and Commercial Bank of China LimitedYes
ifmsuView Comments
2015-12-07
2016-08-15Yes
imdbsuView Comments
2015-12-07
2016-08-15View 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
immosuView Comments
2015-12-07
2016-08-15View Mitigation

immo Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
immobiliensuView Comments
2015-12-07
2016-08-15View Mitigation

immobilien Mitigation

By United TLD Holdco

Please see attached PDF on behalf of United TLD Holdco


View Documents
2016-04-25

United TLD Holdco No
industriessuView Comments
2015-12-07
2016-08-15View Mitigation

industries Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
infinitisuView Comments
2015-12-07
2016-08-15View Mitigation

infiniti Mitigation

By NISSAN MOTOR CO., LTD.

2 Letter Codes Mitigation Plan for NISSAN TLDs
(.nissan .infiniti .datsun)

To address the confusion concerns cited by governments regarding the use of the second-level domains in the NISSAN TLDs,
NISSAN MOTOR CO., LTD. will implement a closed registration policy for NISSAN TLDs that mitigates the potential confusion. To these ends, NISSAN MOTOR CO., LTD. commits to the following:

・Developing and implementing a closed registration policy for NISSAN TLDs that requires that all domains name in the TLDs be registered and used by NISSAN MOTOR CO., LTD., its affiliates, or its trademark licensees;

・Clearly publishing this registration policy on Registry Operator`s homepage for the NISSAN TLDs at “nic.nissan”,”nic.infiniti”, and “nic.datsun”.

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

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

・Using all domain names in the NISSAN TLDs in association with NISSAN`s brand products, and services.

This publicly available registration and usage policy would prevent Governments from registering domains in the NISSAN TLDs. It would therefore clearly designate to the public that NISSAN TLDs were proprietary spaces in which all second-level domains in the TLDs were being operated by NISSAN MOTOR CO., LTD. and not governments.


2016-04-25

NISSAN MOTOR CO., LTD.No
inksuView Comments
2015-12-07
2016-08-15View Mitigation

ink Mitigation

By Top Level Design LLC

The .ink measures for the avoidance of confusion pertain to the following letter/letter labels: ci, cn, eg, il, in, it, me, pt, and sg.

Top Level Design LLC is the Registry Operator for .ink, an open, generic TLD that applies to a wide range of industries and individuals, including printers, bloggers, and artists.

Top Level Design LLC understands the concern that confusion may arise and is willing to offer the following:

1. Top Level Design LLC will commit to:
a. Investigate any reports of misuse, including misleading or deceptive conduct, from relevant governments (including Ivory Coast, China, Egypt, Israel, India, Italy, Montenegro, Portugal, and Singapore), and provide a written report in response.
b. Where, in the Registry Operator’s sole opinion, misuse has occurred, the Registry Operator will seek to work indirectly with the sponsoring registrar and/or directly with the registrant to address the misuse.
c. In the event that misuse continues to occur, the Registry Operator may, in its sole discretion, undertake direct action up to and including suspension or deletion of the domain name, in accordance with its Acceptable Use Policy.


2016-04-25

Top Level Design LLCNo
institutesuView Comments
2015-12-07
2016-08-15View Mitigation

institute Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
insuresuView Comments
2015-12-07
2016-08-15View Mitigation

insure Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
internationalsuView Comments
2015-12-07
2016-08-15View Mitigation

international Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
investmentssuView Comments
2015-12-07
2016-08-15View Mitigation

investments Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
irishsuView Comments
2015-12-07
2016-08-15No
itvsuView Comments
2015-12-07
2016-08-15View 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
iwcsuView Comments
2015-12-07
2016-08-15View Mitigation

iwc Mitigation

By Richemont DNS Inc.

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

Provide a brief explanation of the TLD:

.IWC TLD is a closed Brand new gTLD operated by Richemont DNS Inc

Protections:

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

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

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


2016-04-05

Richemont DNS Inc.Yes
javasuView Comments
2015-12-07
2016-08-15Yes
jcbsuView Comments
2015-12-07
2016-08-15View Mitigation

jcb Mitigation

By JCB Co., Ltd.

.jcb 2 Letter Codes Mitigation Plan

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

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

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

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

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

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

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


2016-04-25

JCB Co., Ltd.Yes
jetztsuView Comments
2015-12-07
2016-08-15No
jewelrysuView Comments
2015-12-07
2016-08-15View Mitigation

jewelry Mitigation

By Donuts Inc.

Attached.


View Documents
2016-04-25

Donuts Inc.No
jlcsuView Comments
2015-12-07
2016-08-15View Mitigation

jlc Mitigation

By Richemont DNS Inc.

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

Provide a brief explanation of the TLD:

.JLC TLD is a closed Brand new gTLD operated by Richemont DNS Inc

Protections:

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

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

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


2016-04-05

Richemont DNS Inc.Yes
jllsuView Comments
2015-12-07
2016-08-15Yes
jmpsuView Comments
2015-12-07
2016-08-15View 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

su Comments

By Yulia Elanskaya, Deputy Director of International Cooperation Department, Ministry of Telecom and Mass Communications of the Russian Federation

Russia objects the release of Two-Character combination “.su” at the second level under any kind/all gTLD.
We are concerned that the deceptive similarity of these two-letter combinations with country codes ccTLDs creates the risk of confusion and misleading of Internet users.
This requirement should apply to all current and future requests.

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."