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.
TLD | Two Characters | Comments from Government | Last updated | RO Mitigation Plan | RO Name | BRAND TLD |
---|---|---|---|---|---|---|
adult | vn | View Comments 2015-12-02 | 2015-12-02 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | pn | View Comments 2015-12-02 | 2015-12-02 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | bm | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | io | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | ky | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | ms | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | sh | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | tc | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | gi | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | ac | View Comments 2015-12-02 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | il | View Comments 2015-12-03 | 2015-12-03 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | kr | View Comments 2015-12-04 | 2015-12-04 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | ng | View Comments 2015-12-04 | 2015-12-05 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | ru | View Comments 2015-12-07 | 2016-08-15 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | su | View Comments 2015-12-07 | 2016-08-15 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | my | View Comments 2015-12-07 | 2015-12-07 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | gb | View Comments 2015-12-08 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | uk | View Comments 2015-12-08 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
adult | it | View Comments 2015-12-08 | 2015-12-08 | View Mitigationadult MitigationBy ICM Registry Protections 2016-04-19 | ICM Registry | No |
aeg | tw | View Comments 2015-10-14 | 2015-12-02 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | in | View Comments 2015-12-01 | 2015-12-01 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | sg | View Comments 2015-11-11 | 2015-12-03 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | ln | View Comments 2015-12-01 | 2015-12-01 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | fk | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | pt | View Comments 2015-11-30 | 2015-11-30 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | gs | View Comments 2015-12-02 | 2015-12-02 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | vn | View Comments 2015-12-02 | 2015-12-02 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | pn | View Comments 2015-12-02 | 2015-12-02 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | bm | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | io | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | ky | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | ms | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | sh | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | tc | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | gi | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | ac | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | il | View Comments 2015-12-03 | 2015-12-03 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | kr | View Comments 2015-12-04 | 2015-12-04 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | ng | View Comments 2015-12-04 | 2015-12-05 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | ru | View Comments 2015-12-07 | 2016-08-15 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | su | View Comments 2015-12-07 | 2016-08-15 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | gb | View Comments 2015-12-08 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | uk | View Comments 2015-12-08 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
aeg | it | View Comments 2015-12-08 | 2015-12-08 | View Mitigationaeg MitigationBy Aktiebolaget Electrolux Provide a brief explanation of the TLD: 2016-04-25 | Aktiebolaget Electrolux | Yes |
agency | in | View Comments 2015-12-01 | 2015-12-01 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | sg | View Comments 2015-11-11 | 2015-12-03 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | ln | View Comments 2015-12-01 | 2015-12-01 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | fk | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | pt | View Comments 2015-11-30 | 2015-11-30 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | gs | View Comments 2015-12-02 | 2015-12-02 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | vn | View Comments 2015-12-02 | 2015-12-02 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | pn | View Comments 2015-12-02 | 2015-12-02 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | bm | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | io | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | ky | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | ms | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | sh | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | tc | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | gi | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | ac | View Comments 2015-12-02 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | il | View Comments 2015-12-03 | 2015-12-03 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | kr | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | ng | View Comments 2015-12-04 | 2015-12-05 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | ru | View Comments 2015-12-07 | 2016-08-15 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | fr | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | gp | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | wf | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | re | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | pm | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | mf | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | pf | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | su | View Comments 2015-12-07 | 2016-08-15 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | nc | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | mq | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | yt | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | tf | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | gf | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | bl | View Comments 2015-12-04 | 2015-12-04 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | gb | View Comments 2015-12-08 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | uk | View Comments 2015-12-08 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
agency | it | View Comments 2015-12-08 | 2015-12-08 | View Mitigation View Documents 2016-04-25 | Donuts Inc. | No |
aig | in | View Comments 2015-12-01 | 2015-12-01 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | sg | View Comments 2015-11-11 | 2015-12-03 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | ln | View Comments 2015-12-01 | 2015-12-01 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | fk | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | pt | View Comments 2015-11-30 | 2015-11-30 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | gs | View Comments 2015-12-02 | 2015-12-02 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | vn | View Comments 2015-12-02 | 2015-12-02 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | pn | View Comments 2015-12-02 | 2015-12-02 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | bm | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | io | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | ky | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | ms | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | sh | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | tc | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | gi | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | ac | View Comments 2015-12-02 | 2015-12-08 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | il | View Comments 2015-12-03 | 2015-12-03 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | kr | View Comments 2015-12-04 | 2015-12-04 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
aig | ng | View Comments 2015-12-04 | 2015-12-05 | View Mitigationaig MitigationBy American International Group, Inc. Provide a brief explanation of the TLD: American International Group, Inc. has applied for .AIG to run a closed .brand environment. 2016-04-20 | American International Group, Inc. | Yes |
vn Comments
By Le Thi Ngoc Mo, Deputy Director General of Vietnam Telecommunications Authority (VNTA), Ministry of Information and Communication (MIC)
Dear ICANN,
“vn” is the country code for Viet Nam. The release of the two-character ".vn" label at the second-level under new gTLDs would create confusion with the ccTLD ".vn". On behalf of Viet Nam government, I would like to submit an objection to the release of the “.vn” at the second level under all new gTLDs.
Viet Nam is seting up the accurate criteria for releasing this two character at the second level domain names under new gTLDs . This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of “.vn” at the second level until we set up the accurate criteria for releasing and send notice to ICANN.
Thank you and best regards,
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
The administration in the Pitcairn Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of Bermuda (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of British Indian Ocean Territory wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of Cayman Islands (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of Montserrat (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of Saint Helena (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of the Turks and Caicos Islands (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of Gibraltar (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion and any unintended consequences, the administration of Ascension Island (UK overseas territory) wish to be notified of all registry requests to use the two characters of their country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
il Comments
By Dr. Amir Adler, Chief Scientist, Ministry of Communications, Ministry of Communications
Request that “il” will be assigned under these TLDs only to a person, entity or
corporation proposed or accepted by the Israeli Government, due to the following concerns:
(1) Unproper or offensive utilization in conjuction with ".il".
(2) Missleading association with the State of Israel.
(3) Interference, or violation of the rights of domestic businesses and organizations.
kr Comments
By Seonyoung Jeong, Assistant Director, Internet Policy Division, Internet Convergence Policy Bureau Ministry of Science, ICT and Future Planning
KR is the country code for the republic of Korea. On behalf of the .kr registry and Korean government, we would like to submit a temporary objection to the release of the '.kr' at the second level under all new gTLDs UNTIL we, Korea government, set up the accurate criteria for releasing. This is sensitive issue for government so it is taking some time for government to consider.
To reiterate, our objections are applied to all new gTLDs who have requested or will be requesting for the release of .kr at the second level until we set up the accurate criteria for releasing. Thank you.
ng Comments
By Nkiru Ebenmelu, GAC Rep, Nigerian Communications Commission
Nigeria does not support the release of Two-Character ASCII Labels ".ng" or the use of "NIGERIA", in the context of any/all of the gTLD(s) at the second level. This should apply to all current and future requests. It is against Nigerian law and strictly prohibited to use the word "Nigeria" or code representing Nigeria without proper authorization by the Government. This assists the Country forestall the abuse and misuse of reserved names associated with the Government; the release would be a breach of our laws. We also wish to inform you that Nigeria reserves the right of authorization for use of “NGR” and “NGA”. As these are also reserved for use by Nigeria. (ISO 3166). We will appreciate it if we are informed of the decision(s) taken.
ru 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 “.ru” 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.
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.
my Comments
By Nur Yushan Binti Yusof, Acting Deputy Director, Network media and Security Management Department
We hereby respectfully submit an objection to release of “my” with names in the subject line for its registration by the registry operators of the TLDs.
.MY is the ccTLD representing Malaysia under ISO 3166-1 alpha-2 country code, duly delegated to MYNIC Berhad by the Internet Assigned Numbers Authority (IANA) with registration record dated 8th June 1987. MY means Malaysia to the Internet community globally and locally. The use of "MY" as SLD in new gTLDs would give the perception that the domain names in question belong to or are related to Malaysia and the Malaysian community.
The preamble to the Government Advisory Committee (GAC) Operating Principles dated April 2005 states that ccTLDs are operated in trust by the Registry for the public interest, including the interest of the Internet community, on behalf of the relevant public authorities including governments, who ultimately have public policy authority over their ccTLDs, consistent with universal connectivity of the Internet. In this context, "MY" officially represents the ccTLD for Malaysia and it is operated in trust by MYNIC Berhad as the duly appointed Registry pursuant to national laws by the Malaysian Communications & Multimedia Commission (MCMC) for the public interest, which includes the interests of the Internet community in Malaysia and globally.
Reference is made to ICANN NGPC Resolution No. 2014.02.05.NG01 and Category 1 Safeguards as Public Interest Commitments in Specification 11 of the new gTLD Registry Agreement. We emphasize on the importance to ensure that these Safeguards are implemented by the Registry operators. We also emphasize on the obligations for Registry Operators to implement measures to avoid confusion and misleading use. Until and unless those measures to avoid confusion and misleading use are implemented by Registry operators, MCMC requests that:-
Registry operator should consult both MCMC and MYNIC on any request for domain name registration of "MY" at the SLD in ADULT, LGBT, PORN, SEX and WTF TLD.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
The UK government notes that gb is a reserved ccTLD string. In order to avoid the potential for confusion, any unintended consequences and consistency within the DNS, the UK requests that this two character code must not be delegated for use as a second-level domain.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
In order to avoid the potential for confusion, and any unintended consequences, the UK government wish to be notified of all registry requests to use the two characters of its country code at the second level - and any existing requests should be put on hold accordingly until they have considered these requests.
it Comments
By Rita Forsi, Italia GAC Representative, Ministry of Economic Development
With reference to the process for Considering Comments for Two-Character Letter/Letter Labels launched by ICANN on October 6, 2015, Italy restates its position expressed on March 25, 2015 (http://mm.icann.org/pipermail/twochar_comments/2015/000063.html) and on May 14, 2015 (email attached).
Italy does not object tout-court to the delegation of our ccSLD, but wants to exercise the right to evaluate the delegation of “it” as a SLD on a case-by-case basis.
The evaluation process takes into account not only the confusion risks, but also the national and international legal framework (e.g. IPR) and opportunity considerations (e.g. it.sucks).
We would like to recall that both the Singapore and Dublin GAC Communiqué advise the Board that comments submitted by the relevant Governments be fully considered regardless of the grounds for objection.
For the abovementioned reasons, we reiterate our position expressed in March 25 2015 for the release of the two‐character “it” label at the second level under new gTLDs.
In general, “it” label string may be released to the extent that the registry operator reaches a formal agreement with the Italian government (included our ccTLD registry “.it”) as per Specification 5 of the Registry Agreement.
This policy is to be applied to all new gTLDs, including, but not limited to, those falling within Category 1 and Category 2 of the Beijing Communiquè. who have requested for the release of “it” labels at the second level.
The authorization requests should be sent to the Italian GAC representatives.
Furthermore, we would like to underline that these “lines-to-take” are agreed with the “.it” Registry.
Rita Forsi
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”.
in Comments
By Rahul Gosain, Director, Department of Electronics and Information Technology, Ministry of communication and Information Technology
India is not favouring the release of Two-Character ASCII labels "in", "1n" and deceptively similar as the ccTLD ".in" at the second level. ICANN is requested that India's objection on release of Two-character ASCII labels "in" and "1n" at the second level should apply to all current and future requests from new gTLD's
sg Comments
By Queh Ser Pheng, Deputy Director, Internet Resource Management, Policy & Competition Development Group, Infocomm Development Authority of Singapore
We hereby respectfully submit our comment regarding the release of letter/letter two-character labels as second level domains.
At this stage, we are unable to agree to the release of the two-character "sg" label at the second-level under gTLDs because of the concern that such use would create confusion with the ccTLD "sg" representing Singapore. Until further notice, this policy is to be applied to all gTLDs who have requested or will be requesting for the release of letter-letter two-character labels at the second level.
To elaborate further, we are open to considering the release of "sg" to registry operators who have robust framework in place to address concerns of government. We recognise there are legitimate and valid reasons for such use. However, we are of the view that it is prudent for ICANN to first put in place a holistic and robust framework before approvals can be given. More thoughts need to be given to the evaluation process and in particular the remedies available should a registry operator use the approved names in an undesirable manner. Besides possible confusion with the corresponding country code and/or country/territory name, we are also concerned with:
(a) The possible reputational harm if ".sg.
(b) The direct harm if ".sg.
ICANN's current policy focuses only on the "initial release" process. There needs to be considerations given to "post-release" issues. As such, the ICANN framework should include:
(a) A recourse for the government/country code manager to issue a notice to object to the content and/or manner-of-use that is misleading, questionable, objectionable or contrary to the country’s reputation and laws. There should be an effective and robust process acceptable by the government/country code manager for the registry operator to address the concern; and
(b) Provisions to require the registry operator to re-seek approval from government/country code manager should there be material changes in ownership or organisational control (for example merger with or acquisitions by another entity).
In addition, ICANN must be committed to take actions against the registry operator should they fail to comply with the framework (e.g. implement a process for country/territory to raise objections to ICANN and for ICANN to take appropriate remedial actions such as remove/delete/revoke affected names).
in Comments
By Rahul Gosain, Director, Department of Electronics and Information Technology, Ministry of communication and Information Technology
India is not favouring the release of Two-Character ASCII labels "ln" and "1n" and deceptively similar as the ccTLD ".in" at the second level. ICANN is requested that India's objection on release of Two-character ASCII labels "ln" and "1n" at the second level should apply to all current and future requests from new gTLD's
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
The administration of the Falkland Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.
pt Comments
By Ana Cristina Ferreira Amoroso das Neves, Director, Department Information Society, Fundação para a Ciência e a Tecnologia, Ministry of Science, Technology and Higher Education
I request previous comments to objections to the release of the ".pt" as the SLD signalling 1) consumer protection concerns and confusion; 2) some gTLD correspond to a regulated market in EU countries, so their release might generate possible abuses and confusion at the end-users level and therefore must be subject to authorization by the Portuguese Government; 3) others should remain reserved so that can only be assigned to a person, entity or corporation proposed or accepted by the Portuguese Government, which demands consultations with the Portuguese Government. These comments are due to the ICANN's new process launched on the 6th October 2015 on the use of the 2-letter CC and CN at the SLD, taken into account nonetheless GAC's advice from Dublin Communiqué (October 2015). Confusability exists in all instances since the PT code is widely recognized both on and off the Internet as an identifier for Portugal. In this regard, we are concerned that consumers assume that persons or undertakings operating under "pt.string" not only offer their services in Portugal or products or services related to Portugal but that they comply with applicable regulations. As this may not be warranted by registration policies and contracts, we would request Portuguese Government is consulted before any registration, regardless of the grounds for objection. Portugal reserves the right to change position in this regard in the future.
The Portuguese Government will continue to closely follow the evolution of the market and of the technical and political framework to collect data and evidence to better understand the consequences of such release.
uk Comments
By Nick Shorey, Senior Policy Officer, Department for Culture, Media & Sport
The administration in South Georgia and the South Sandwich Islands (UK overseas territory) have no objection to the use of two character domains which coincide with their ccTLD at the second level, and do not wish to be notified of such requests by registries.
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, domains, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique
fr Comments
By Ghislain de Salins, Direction générale des entreprises – Service de l’économie numérique, Ministère de l’économie, de l’industrie et du numérique
Dear ICANN,
The French government requests that the release of the two-letter codes attached to the territory of France (fr, gp, wf, re, pm, mf, pf, nc, mq, yt, tf, gf, bl) at the second-level under new gTLDS should be subject to preliminary authorization by the French authorities, regarding gTLDs that correspond to either sovereign domains (e.g. .army) or regulated sectors and activities in French law (e.g. .doctors). Indeed, such codes used at the second-level under these gTLDs could create confusion with the corresponding ccTLDs, and could therefore harm or deceive consumers.
Therefore, in order to release the relevant country codes under the following TLDs, registries should contact the French authorities directly:
* “old” requests: academy, accountant, accountants, agency, attorney, auction, beer, bid, bingo, broker, clinic, college, dental, education, lotto, pharmacy, services, theatre, university, vote
archi, army, airforce, bank, bet, bio, casino, cloud, dentist, doctor, domains, finance, lawyer, navy, sarl
* « new » requests : travelersinsurance, property, help, properties, bet, clinique