Instantané du 8 octobre 2026 · ICANN APS, champs publics

Candidatures / .yueyang / YFTZ2669T-T39431 · publié par l'ICANN le 7 octobre 2026 · instantané du 2026-10-08

.yueyang

GéographiqueActive

Yueyang Free Trade Zone Investment Co., LTD, CN Q1·Q25

Contrôle ultime déclaré : Management Committee of Yueyang Area of China (Hunan) Pilot Free Trade Zone Q108 · Fiche ICANN ↗

§ 1 — Sens de la chaîne Q118·Q120

The string “yueyang” is based on “YUEYANG” ,the commonly used romanized spelling of the name of the City of Yueyang in Hunan Province, China.

jue'jæŋ

§ 2 — Mission et objet Q133

The mission of the proposed .yueyang gTLD is to establish a dedicated, globally resolvable Internet namespace named for Yueyang, Hunan Province, China. It will provide organizations, businesses and eligible individuals with a substantive connection to Yueyang with a clearly city related tool for Internet naming, identification, information presentation and access, while supporting the city’s digital development, public services, open economy, port related industries, culture, tourism and international communication. Intended registrants and users include government authorities and public service providers; enterprises in the China (Hunan) Pilot Free Trade Zone Yueyang Area, port logistics, petrochemicals, new materials, advanced manufacturing, cross border commerce and other key industries; tourism sites, museums, cultural institutions, universities, research institutions, industry associations and nonprofit organizations; local businesses , local lifestyle service platforms and operators of distinctive local products; eligible residents, entrepreneurs, brand creators and other individual users; and overseas organizations and users with economic, cultural or other connections to Yueyang. Registration services will be provided through qualified ICANN accredited registrars under uniform, public, transparent and non discriminatory rules. A .yueyang domain name will provide Internet naming, resolution, identification and access functions. It will not, by itself, certify a registrant’s identity, qualifications, creditworthiness, security capability, data quality or service quality, and it will not replace an administrative license, professional certification, credit assessment, trademark right or determination of data ownership. The namespace will be managed through classified and tiered registration policies. In addition to names reserved under ICANN policies and applicable laws and regulations, names relating to government, administrative divisions, public services, major landmarks, important cultural identifiers, sensitive terms and other matters of public interest will be reserved, authorized for use or restricted. General names will be reviewed under published rules, and applications involving trademarks, organization names, project names or other rights will be reviewed for the relevant eligibility, rights or authorization. The applicant has developed and will implement policies covering registration, renewal, transfer, suspension, cancellation, rights protection, complaint handling, dispute resolution, data protection and domain name abuse mitigation. An ICANN evaluated Registry Service Provider will provide DNS, DNSSEC, EPP, RDAP, registry database, data escrow, security monitoring, disaster recovery and business continuity services. The Applicant will also develop domestic and international registration channels and promote practical uses in public services, industrial promotion, cross border trade, tourism and cultural communication, brand presentation and individual online identity. The mission is sustainable over time because it is based on Yueyang’s enduring geographic identity and continuing demand arising from public service digitization, industrial development, trade, tourism and international communication. Long term operation will be supported by a diversified registrant base, recurring registration and renewal demand, tiered services and published pricing, professional operations, phased market development and necessary reserve funding. If revenue is lower than projected, priority will be given to the continuous operation of DNS and registry systems, security and compliance, customer service, data escrow and existing domain names.

§ 3 — Engagements et sauvegardes Q164–Q188

Confiance accrue, risque pour le consommateur, secteur réglementé, déclarations à l'État, préjudice, fonction régalienne Q164–Q169Non à chacune
PIC de sauvegarde volontaires Q170·Q171Aucun · 90 candidatures de la ronde en proposent
Registry Voluntary Commitments Q172·Q173Aucun · 5 en proposent
Exemption du Code de conduite demandée Q185·Q188Non

§ 4 — Toutes les autres réponses publiées

Toutes les autres réponses que l'ICANN a publiées pour cette candidature, dans l'ordre du formulaire. Les coordonnées (Q17–Q24) sont laissées à la fiche ICANN.

Q212Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.

Q4.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. If financial statements are provided by a Qualified Parent Entity (QPE), the CEO, President, CFO, and/or equivalent officer of the QPE must co-sign the certification document. The self-certification document must represent and warrant: SC4.2-1.1 - The applying entity and/or a QPE will fund the startup and long-term operation of all applied-for gTLD strings and (if applicable) currently operated gTLDs of a QPE. SC4.2-1.2 - The applying entity or QPE has at a minimum of US$50,000 plus 25% of the application base fee for each applied-for gTLD string in Cash and Cash Equivalents on the balance sheet of the provided financial statements, up to a maximum of US$300,000, designated to support the startup and operation of all of the applying entity’s applied-for gTLD strings. SC4.2-1.3 - The applying entity and/or its officers are bound by law in its jurisdiction to represent financial statements accurately and the applying entity is in good standing in that jurisdiction.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q220Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Q5.1-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.1-1.1 - The applying entity will appropriately protect confidentiality of data and prevent unauthorized access to data and services. SC5.1-1.2 - The applying entity will maintain a mature, appropriately funded and staffed security program, following a recognized, modern security framework based on risk management (such as the ISO27000 series, COBIT, HITRUST CSF, legally required security frameworks, or equivalent). The security program must be in place prior to delegation, and exist through at least the period of the registry agreement. SC5.1-1.3 - The applying entity is aware of and has designed its systems and business to comply with the relevant privacy and security regulations for all countries in which it operates.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q221Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Q5.2-1 - Provide the applying entity’s self-certification document, signed by the CEO, President, CFO and/or equivalent officer of the applying entity. The self-certification document must represent and warrant: SC5.2-1.1 - The applying entity will, no later than delegation of the Top Level Domain (TLD), establish a dedicated abuse point of contact responsible for addressing matters requiring expedited attention and providing a timely response to abuse complaints concerning any name registered in the TLD. SC5.2-1.2 - The applying entity will, no later than delegation of the TLD, establish, publish, and provide to ICANN the location of a mechanism for members of the public to submit reports of abuse in accordance with the current obligations of the Base RA and any Consensus Policies. SC5.2-1.3 - The applying entity has developed proposed measures for removal of orphan glue records for names removed from the zone when provided with evidence in written form that the glue is present in connection with malicious conduct (see Specification 6). SC5.2-1.4 - The applying entity has or will have at time of delegation, established policies for handling complaints regarding abuse. Such policies are to be maintained and posted publicly so that anyone can review the policies via the Internet and any other means deemed appropriate by the applying entity. The applying entity’s policies at a minimum should contain appropriate confirmation of the receipt of the abuse report, the process of review of the report, and actions that will be taken if the applying entity confirms the report is legitimate. SC5.2-1.5 - The applying entity understands that DNS Abuse is Phishing, Malware, Botnets, Pharming and Spam (when used to deliver other forms of DNS Abuse). The applying entity understands and is prepared to contribute to the mitigation or disruption of DNS Abuse in domains in the TLD zone. SC5.2-1.6 - The applying entity’s abuse response capabilities are resourced appropriately to ensure a timely and adequate investigation and response to reports of DNS Abuse. This includes capabilities to receive and evaluate evidence of DNS Abuse in reports, and to take action to stop or disrupt the DNS Abuse. SC5.2-1.7 - The applying entity is prepared to conduct periodic scans of its zone to identify if domains are being used to perpetrate DNS Abuse, and to maintain statistical reports of the scans, the findings, and actions taken.

Réponse fournie sous forme de document. L'ICANN ne publie pas les pièces jointes.

Q121As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.

As per Section 3(d) of Specification 11 of the Base Registry Agreement, a registry operator of a “generic string” may not impose eligibility criteria for registering names in the TLD that limit registrations exclusively to a single person or entity and/or that person’s or entity’s “Affiliates” (as defined in Section 2.9(c) of the Registry Agreement). “Generic String” means a string consisting of a word or term that denominates or describes a general class of goods, services, groups, organizations or things, as opposed to distinguishing a specific brand of goods, services, groups, organizations or things from those of others. Confirm that the applied-for string is not a “generic string” in which the applying entity intends to limit registrations exclusively to a single person or entity.

true

Q159Is the applied-for string the name of a city and, if so, is the intention to use the TLD primarily for purposes associated with the city name?

Is the applied-for string the name of a city and, if so, is the intention to use the TLD primarily for purposes associated with the city name?

Yes

Q160If answered yes to previous question, how will the applying entity market and/or use the TLD primarily for purposes associated with the city name?

If answered yes to previous question, how will the applying entity market and/or use the TLD primarily for purposes associated with the city name?

The Applicant will market and use “.yueyang” primarily as a geographic top level domain associated with the name of the City of Yueyang in Hunan Province, China, and with purposes related to the city. “yueyang” is the Hanyu Pinyin and Roman letter spelling of “岳阳” and directly refers to the City of Yueyang. Accordingly, the Applicant will position “.yueyang” as an Internet identifier with a clear association with the city, enabling users in China and abroad to recognize the connection between relevant organizations, businesses, content, operations, projects, activities or digital services and Yueyang. This association with the city will be conveyed primarily through the combination of the second level domain name, the registrant and the actual use of the domain name. Registrants may combine the names of organizations, brands, projects, activities, services or other distinctive terms with “.yueyang” to indicate that they conduct business in Yueyang, undertake projects related to Yueyang, serve Yueyang residents or customers, or provide content and services relating to Yueyang’s public services, free trade and port related industries, port logistics, cross border trade, petrochemicals and new materials, culture and tourism, distinctive local products, urban life or international cooperation. For example, public service authorities may use names corresponding to government websites, public convenience services, public information systems or public service portals. Enterprises may use names corresponding to their corporate brands, trade projects, port services or industrial projects. Tourism resources such as Yueyang Tower, Junshan Island and Dongting Lake, as well as museums, cultural institutions, industry associations and social organizations, may use relevant names for tourism promotion, cultural communication and industry services. Overseas organizations and users may use names reflecting their Yueyang related economic and trade cooperation, cultural exchanges or international cooperation projects. To reinforce these city related purposes, the Applicant will conduct promotion, establish demonstration uses and undertake marketing through qualified ICANN accredited registrars, Yueyang public institutions, the free trade zone and port platforms, key industrial parks, industrial enterprises, cultural and tourism institutions, universities, research institutions, industry associations, domestic and overseas partners, city promotion events, economic and trade exchange activities, tourism promotion activities and international conferences. These efforts will focus on presenting domain name examples that are actively used and that clearly communicate an association with Yueyang. General names may, in principle, be opened to registrants worldwide in phases in accordance with the applicable policies. Registration will not be limited solely to entities registered in Yueyang. In its marketing and usage guidance, the Applicant will emphasize the Yueyang related business, projects, services, content or other reasonable associations represented by the domain name. For names within reserved, authorized or reviewed categories, including names relating to government, public services, administrative divisions, city landmarks, important cultural identifiers, key free trade zone and port resources, and important brands, registrants must demonstrate the relevant eligibility, rights or authorization in accordance with the applicable rules. Through these marketing and usage arrangements, “.yueyang” will continue to connect the Yueyang city name with specific entities, businesses, projects, activities and Internet resources, and will be used primarily for identification, presentation, access and communication purposes associated with the City of Yueyang.

Q158Is the applied-for string a geographic name as defined by it being any one of the following: a) the capital city name of a country or territory listed in the ISO 3166-1 standard; b) a city name, where it is clear from statements in the application that the applying entity intends to use the gTLD for purposes associated with the city name; c) a sub-national place name listed in the ISO 3166-2 standard; or d) Strings listed as UNESCO regions or appearing on the Geographic Regions section of the “Standard country or area codes for statistical use (M49)”

Is the applied-for string a geographic name as defined by it being any one of the following: a) the capital city name of a country or territory listed in the ISO 3166-1 standard; b) a city name, where it is clear from statements in the application that the applying entity intends to use the gTLD for purposes associated with the city name; c) a sub-national place name listed in the ISO 3166-2 standard; or d) Strings listed as UNESCO regions or appearing on the Geographic Regions section of the “Standard country or area codes for statistical use (M49)”

Yes

Q223By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

By submitting this Application, the applying entity confirms that it is submitting this Application with a good faith (“bona fide”) intent to operate the gTLD for which it has applied, and that the applying entity has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

true

Q224By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

By submitting this Application, the applying entity confirms that it has read and understands the provisions of Section 5.2.3.1 Prohibited Communications and Activities of the Applicant Guidebook regarding the New gTLD Program rules prohibiting certain communications and activities to prevent parties from privately resolving string contention among themselves.

true