1. General Provisions

This Registry String Policy is incorporated by reference into the Registration Agreement between the Registrar and the Registrant. This Registry String Policy forms part of the Registry Policies and sets forth the string requirements for second-level domain name registrations under .fans.

This document is provided in both Chinese and English. In the event of any inconsistency or conflict between the two language versions, the English version shall prevail.

2. Technical Requirements for Strings

A domain name consists of multiple labels, which are referred to as “strings” in this document. Each domain name label must comply with Section 3.5 of RFC 1034. Any domain name application that does not comply with this Registry String Policy or other applicable Registry Policies shall not be registered.

3. ASCII Strings

An ASCII domain name, or an A-label domain name converted from a Chinese domain name, must comply with the following requirements:

• a. The second-level domain name must not exceed 63 ASCII characters;
• b. The second-level domain name may only consist of letters a–z, case-insensitive, digits 0–9, and the hyphen “-”;
• c. The hyphen “-” must not appear at the beginning or end of the string.

In addition, the third and fourth positions of an ASCII domain name label must not both be hyphens. For example, an ASCII domain name such as “ad--cd” may not be registered.

4. IDN Strings

IDNs, or Internationalized Domain Names, refer to domain names that contain characters used in non-English languages. For example, a domain name containing Japanese characters is a Japanese domain name, while a domain name containing Chinese characters is a Chinese domain name.

The .fans Registry does not currently support IDNs. Any future launch or support of IDNs will be subject to notices published on the official Registry website.

In addition to certain strings that are required by ICANN to be reserved, the Registry reserves the right, at its sole discretion, to reserve, withhold, allocate to the Registry, block, or otherwise prohibit the registration of certain strings. Such strings may not be registered to third parties, delegated in the DNS, used, activated, or otherwise made available for external use unless released or approved by the Registry in accordance with applicable policies.

The Registry shall establish and maintain a Reserved Names List in accordance with applicable laws and regulations. Each domain name registration request shall be checked against the Reserved Names List. If the domain name applied for is a reserved name, the registration request shall be rejected.

3. Reserved Names List

The reserved names maintained by the Registry include the following categories:

a. Names reserved pursuant to ICANN requirements;

b. Names reserved pursuant to applicable local laws and regulations;

c. Names reserved for Registry marketing activities.

Subject to ICANN requirements and applicable laws and regulations, the Registry reserves the right to add, remove, or modify names on the Reserved Names List from time to time.

3(A). ICANN Reserved Names

The following names are reserved pursuant to ICANN requirements:

• a. The English word “example”;
• b. Certain two-character labels;
• c. Registry-reserved names for self-allocation by the Registry;
• d. Country and territory names;
• e. Names relating to the International Olympic Committee, the International Red Cross and Red Crescent Movement;
• f. Names relating to intergovernmental organizations;
• g. Names under .fans that are required to be blocked from registration pursuant to ICANN policies regarding name collision management.

3(B). Names Reserved Pursuant to Local Laws

Pursuant to the Measures for the Administration of Internet Domain Names issued by the Ministry of Industry and Information Technology of the People’s Republic of China under Order No. 43, the .fans Registry shall block and not make available for registration any domain names that contain content falling within any of the following categories:

1. Content that opposes the basic principles established by the Constitution;
2. Content that endangers national security, discloses state secrets, subverts state power, or undermines national unity;
3. Content that harms national honor or interests;
4. Content that incites ethnic hatred or ethnic discrimination, or undermines ethnic unity;
5. Content that undermines national religious policies, or promotes cults or feudal superstition;
6. Content that spreads rumors, disrupts social order, or undermines social stability;
7. Content that disseminates obscenity, pornography, gambling, violence, murder, terrorism, or incites the commission of crimes;
8. Content that insults or defames others, or infringes upon the lawful rights and interests of others;
9. Content otherwise prohibited by laws or administrative regulations.

Accordingly, the Registry prohibits the registration of names that fall within the above categories, including variant forms of such names.

3(C). Names Reserved for Registry Marketing Activities

The Registry may also reserve certain names for marketing activities relating to the top-level domain. The Registry may allocate such reserved names through market sales, auctions, or other allocation mechanisms. Once a reserved name has been allocated, it shall be removed from the Reserved Names List.

4. Changes to Reserved Names

Names reserved pursuant to ICANN policies shall be updated in accordance with notices or policy changes issued by ICANN.

Names reserved pursuant to applicable local laws and regulations shall be updated in accordance with the requirements of the competent telecommunications authority and other relevant national authorities.

Names reserved by the Registry for its own marketing activities may be updated from time to time based on the Registry’s marketing activities.

5. Activation of Reserved Names

If an applicant wishes to register or activate a reserved name, the applicant may submit a reserved name registration request through a Registrar accredited or authorized by the Registry, together with authorization documents evidencing the consent of the relevant rights holder. For further details, please contact the Registrar or the Registry.

1. General Provisions

This Privacy Protection and WHOIS/RDAP Policy forms part of the .fans Registry Policies and sets forth the privacy protection and WHOIS/RDAP policy applicable to the .fans top-level domain.

This Policy is provided in both Chinese and English. In the event of any inconsistency or conflict between the two language versions, the English version shall prevail.

2. Purpose

The purposes of this Privacy Protection and WHOIS/RDAP Policy are as follows:

1. To disclose to Registrants, and to obtain their consent, that certain Personal Information provided by Registrants may be processed by the Registry in the following ways:
   a. In accordance with this Privacy Protection and WHOIS/RDAP Policy and/or other Registry Policies or practices, Registrants’ Personal Information will be collected and may be used, maintained, and/or corrected from time to time;
   b. Personal Information shall be collected by the Registry through Registrars for the purpose of storing, maintaining, disclosing, and/or using such Personal Information. In addition to ICANN and the Registry’s Data Escrow Agent, the Registry may disclose or transfer such Personal Information to other third parties under the circumstances outlined in the “Use and Disclosure” section of this Privacy Protection and WHOIS/RDAP Policy;
   c. Subject to the policies listed below, Personal Information provided by Registrants to the Registry or Registrars may be made available to third parties through publicly accessible WHOIS and/or RDAP services:

• the Registry’s privacy practices;
• the Registry Policies;
• ICANN Consensus Policies; and/or
• applicable laws, regulations, and rules.

1. To outline the Registry’s procedures for the proper collection, retention, use, correction, disclosure, and transfer of Registrants’ Personal Information.

In order to provide registry services for the TLD, ICANN requires the Registry to collect and publish registration data identifying the Registrant associated with each domain name.

3. Definitions

For this Privacy Protection and WHOIS/RDAP Policy, the following terms shall have the meanings set forth below.

1. “Data Escrow Agent” means a third party contracted by the Registry to provide data escrow services. The data escrow agreement entered into with the Data Escrow Agent ensures that all relevant DNS data and Registrant information, including Personal Information, may be transferred to ICANN and any ICANN-approved Emergency Back-End Registry Operator (“EBERO”), and further ensures the security and integrity of the Registry’s TLD database. The Data Escrow Agent is prohibited from using or disclosing the Registry’s TLD data unless such use or disclosure is essential to ensuring the stability and integrity of the Registry TLD.
2. “Personal Information” means information relating to a person, including any Registrant, by which the identity of such Registrant may reasonably be ascertained. Personal Information does not include indexes or aggregated information relating to multiple individuals, such as log files, DNS zone files, databases, or backups. Personal Information may include the Registrant’s name, address, telephone number, and email address, and may also include the Registrant’s home address and personal email address if the Registrant uses such information as the primary contact information for the domain name.
3. The “Primary Purpose” for collecting Personal Information is to store and maintain such information in the WHOIS/RDAP database, a copy of which ICANN requires to be provided to the Data Escrow Agent. Such database is searchable and publicly available. If the Registry does not collect such Personal Information and make it publicly available through the WHOIS database, the domain name cannot be registered.

4. Meaning of “WHOIS/RDAP” Server

The Registry shall maintain a publicly accessible information service known as the Registry “WHOIS” and/or “RDAP” service.

The WHOIS system is a standard service operated by all registries and Regional Internet Registries (“RIRs”), and is used by third parties to obtain information regarding registered domain names.

RDAP is a protocol that is being gradually introduced as a successor to WHOIS and provides the same or similar information in a structured, machine-readable data format.

The WHOIS and/or RDAP service provides the following domain name-related information in accordance with ICANN Consensus Policies, as may be amended from time to time:

1. Technical information regarding the DNS name servers for the domain name;
2. The date on which the domain name was entered into the Registry database;
3. The date on which the domain name information was last updated;
4. The expiration date of the domain name;
5. The current status of the domain name;
6. Contact information of the Registrar;
7. The name of the Registrant;
8. The address of the Registrant;
9. The email address and telephone number of the Registrant;
10. The province or state of the Registrant;
11. The country of the Registrant;
12. The administrative contact, technical contact, and billing contact information submitted by the Registrant.

5. Data Collection

1. Where necessary, the Registry will collect Personal Information for one or more of the following functions and/or activities:
   a. Identifying and maintaining contact details of domain name Registrants and their designated agents;
   b. Providing public access to such data and access to persons related to the Registrant;
   c. Providing services to Registrants and maintaining the Registry database;
   d. Providing WHOIS and/or RDAP services;
   e. Contacting Registrants, including by way of notice, in accordance with the Registry Policies; and/or
   f. Providing information to law enforcement agencies, governmental authorities, and relevant Internet security organizations where such information is required for the investigation or prevention of suspected criminal activity.
2. The Registry’s website may use technologies that collect user information and track usage, including cookies. The Registry’s website may contain links to third-party websites; however, the Registry is not responsible for the content or privacy practices of any such third-party websites.

6. Data Storage

Domain name registration information is stored in a centralized database. The database is hosted in secure hosting facilities and protected by enterprise-grade firewalls and an ISO 27001-certified information security management system.

The Registry performs regular database backups to ensure continuity of service. All backups are stored in encrypted format and transmitted through encrypted communications to secure off-site locations in order to prevent unauthorized access.

7. Use and Disclosure

1. The Registry may use or disclose Personal Information relating to a Registrant for purposes other than the Primary Purpose under the following circumstances:
   a. Where the Personal Information includes detailed contact information associated with Registrars, Internet service providers, Internet service resellers, or persons related to them, such as directors, managers, or other contacts;
   b. Where the Registrant has consented to such use or disclosure; or
   c. Where the Registry believes that such use or disclosure is necessary:

• to lessen or prevent a serious and imminent threat to an individual’s life, health, or safety; or
• to lessen or prevent a serious threat to public health or public safety; or
• where the Registry has reason to suspect that unlawful activity or a violation of any Registry Policy has been, is being, or may be engaged in, and the use or disclosure of Personal Information is a necessary part of the Registry’s investigation of the matter or reporting of the matter to relevant persons, including parties affected by such violation, or to relevant authorities; or
• where such use or disclosure is required or authorized by applicable laws, regulations, or rules; or
• where the Registry believes that such use or disclosure by or on behalf of a law enforcement agency is necessary for one or more of the following purposes:
  i. the prevention, detection, investigation, prosecution, or punishment of criminal offences, breaches of laws imposing penalties or sanctions, or breaches of prescribed laws;
  ii. the preparation for or conduct of proceedings before any court or tribunal, or the enforcement of orders of any court or tribunal; or
• pursuant to an order issued by a dispute resolution provider under ICANN’s Uniform Domain Name Dispute Resolution Policy (“UDRP”) or Uniform Rapid Suspension (“URS”) procedure; or
• as determined by the parties to a CRS dispute for any other lawful purpose.

1. Nothing in this Section 7, “Use and Disclosure,” shall require the Registry to disclose any Personal Information. Where the Registry is not under a legal obligation to disclose Personal Information, the Registry shall at all times retain the right not to disclose such Personal Information.
2. Where Personal Information is transferred to an individual or entity located outside China, the Registry may also be subject to current and future policy requirements governing cross-border data transfers.
3. The Registry maintains and uses servers in various locations worldwide and therefore may need to transfer data, including Personal Information, between servers and data networks.

8. Data Deletion

When a domain name is deleted, and the information records associated with such domain name are no longer useful for any other domain name in the database, any contact information associated with such domain name shall be deleted, unless the Registrar has elected not to delete such data upon expiration.

A Registrar that elects not to delete expired data shall be responsible for deleting any contact information that is no longer useful. The Registry shall require such Registrar to provide monthly reports on the management of expired but undeleted data in order to enforce this requirement. The Registry reserves the right to automatically purge such data if the Registrar fails to manage its contact data properly.

9. Data Quality

The Registry may, but is not obligated to, take steps to ensure that the Personal Information it collects, uses, or discloses is accurate, complete, and up to date. Such steps may include validation through the Registrant via the Registrar by effective email, SMS, or telephone.

10. Data Security

The Registry shall take steps required by ICANN and applicable Chinese laws to protect the Personal Information it holds against misuse and loss, and, to the extent required by law, against unauthorized access, modification, or disclosure.

11. Publication of Policy

This Privacy Protection and WHOIS/RDAP Policy sets forth the Registry’s policy regarding its management of Personal Information. The Registry shall make this document available to any person upon request and shall publish it on the Registry’s website.

12. Access and Correction

1. If the Registry holds Personal Information relating to a Registrant, the Registry shall, upon receipt of a written request from the Registrant, provide the Registrant with access to such information, unless the Registry determines that:
   a. Providing access to the Personal Information may pose a serious and imminent threat to the life or health of any individual; or
   b. Providing access may have an unreasonable impact on the privacy of others; or
   c. The request for access is frivolous or vexatious; or
   d. The information relates to existing or anticipated legal proceedings; or
   e. Providing access may be unlawful; or
   f. Refusal of access may be required or authorized by laws, regulations, or rules, including but not limited to an order of any court of competent jurisdiction; or
   g. Providing access may prejudice an investigation of possible unlawful activity; or
   h. Providing access may prejudice any of the following:

• the prevention, detection, investigation, prosecution, or punishment of criminal offences or other unlawful conduct; or
• the preparation for or conduct of proceedings before any court or tribunal, or the enforcement of its orders; or
• a request by a law enforcement agency or relevant Internet security organization that the Registry not provide access to the information.

1. Except as required by ICANN, applicable law, or a court order, the Registry shall not be obligated to disclose DNS zone files, payment logs, email archives, or data backups to any person.
2. If providing access would disclose evaluative information generated within the Registry in connection with a commercially sensitive decision-making process, the Registry may provide the Registrant with an explanation of the commercially sensitive decision instead of granting access to such information.
3. If the Registry holds Personal Information relating to a Registrant, the Registrant has the right to indicate that such information is inaccurate, incomplete, or not up to date. Upon receipt of such notice from the Registrant, the Registry shall take reasonable steps, as requested by the Registrant, to correct the relevant Personal Information so that it is accurate, complete, and up to date, unless such data has already been incorporated into historical records or archives.

13. Policy Review

The Registry reserves the right to review and amend this Privacy Protection and WHOIS/RDAP Policy from time to time in accordance with ICANN Consensus Policies or other applicable laws or regulations. Any Registrant that provides Personal Information to the Registry shall be deemed to have acknowledged and agreed to comply with this Privacy Protection and WHOIS/RDAP Policy and any subsequent amendments thereto.

The latest version of this Privacy Protection and WHOIS/RDAP Policy shall be published on the Registry’s official website. This Policy shall apply to any domain name registered under .FANS, regardless of when or through which channel such domain name is registered, renewed, or transferred.

If a Registrant licenses or leases a domain name registered under .FANS, or any subdomain thereof, in accordance with the Registry Policies, the Registry and the relevant Registrar shall require the Registrant to remain fully responsible for the licensed or leased domain name or subdomain.

1. General Provisions

This Domain Name Transfer Policy forms part of the .FANS Registry Policies and sets forth the domain name transfer policy applicable to the .FANS top-level domain.

This Policy is provided in both Chinese and English. In the event of any inconsistency or conflict between the two language versions, the English version shall prevail.

2. Domain Name Transfers

A domain name transfer refers to the transfer of a domain name registration from the current Registrar, namely the losing Registrar, to another Registrar, namely the gaining Registrar.

The holder of a registered domain name may transfer its domain name registration between Registrars, provided that the gaining Registrar’s transfer process complies with the minimum standards set forth in the ICANN Transfer Policy, and provided further that such transfer is not prohibited by ICANN policies or the Registry Policies.

3. Transfer Authorization

Only the administrative contact and the Registered Name Holder listed in the publicly accessible WHOIS/RDAP service of the Registrar, collectively referred to as the “Authorized Transfer Contacts,” are authorized to approve or deny a transfer request submitted by the gaining Registrar.

In the event of a dispute, the authority of the Registered Name Holder shall prevail over that of the administrative contact.

4. Registrar Cooperation

1. After verifying the identity of the user, the losing Registrar shall provide the transfer authorization code, also known as the AuthInfo Code, without undue restriction.
2. If the losing Registrar denies a transfer request on any of the following grounds, it must provide the reason for denial to the Registered Name Holder and the gaining Registrar. The losing Registrar may deny a transfer request only under the following circumstances:
   a. There is evidence of fraud in connection with the transfer request;
   b. There is a reasonable dispute over the identity of the Registered Name Holder or the administrative contact;
   c. The domain name has expired and payment for the previous registration period has not been made, or the domain name has not expired but payment for the previous or current registration period has not been made;
   d. The Authorized Transfer Contact has expressly objected to the transfer;
   e. According to the Registry’s WHOIS/RDAP records, the transfer request is made within 60 days after the initial registration of the domain name;
   f. The domain name is within 60 days, or any shorter period to be determined, of a previous inter-Registrar transfer, except where the domain name is transferred back to the original Registrar by agreement of both Registrars and/or pursuant to a decision in a dispute resolution proceeding. For the purposes of this provision, “transferred” refers only to an inter-Registrar transfer conducted in accordance with the procedures under the ICANN Transfer Policy.
3. The losing Registrar must deny a transfer request under the following circumstances:
   a. The Registrar has received notice of a pending UDRP proceeding;
   b. There is a court order issued by a court of competent jurisdiction;
   c. There is a pending dispute relating to a previous transfer under the Transfer Dispute Resolution Policy;
   d. The Registrar has imposed a 60-day inter-Registrar transfer lock following a Change of Registrant in accordance with the procedures set forth in this Policy;
   e. The Registrar has imposed a 60-day inter-Registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of such 60-day inter-Registrar transfer lock before the Change of Registrant request.
4. The losing Registrar may not deny a domain name transfer request on grounds including, but not limited to, the following:
   a. Non-payment for a pending or future registration period;
   b. No response has been received from the Registered Name Holder or the administrative contact;
   c. The domain name is in “Registrar Lock” status, unless the Registered Name Holder has been provided with a reasonable opportunity and a reasonably accessible method to remove the lock before submitting the transfer request;
   d. Restrictions based on the length of the registration period of the domain name, except for the first 60 days after initial registration, the first 60 days after an inter-Registrar transfer, or a 60-day lock period following a Change of Registrant, as provided under the ICANN Transfer Policy;
   e. A general payment default between the Registrar and its business partner or affiliate, where the Registered Name Holder of the domain name concerned has paid for the domain name registration.

5. Renewal upon Transfer

Upon transfer of a domain name, the user shall renew the domain name for an additional one-year registration term with the gaining Registrar.

6. ICANN-Approved Transfers

1. If a Registrar initiates the transfer of all registered domain names under its sponsorship due to either:
   i. the acquisition of such Registrar or its assets by another Registrar; or
   ii. the loss of Registrar accreditation or the loss of authorization from the Registry Operator,
   the transfer shall be carried out in accordance with the following procedures:
   a. The gaining Registrar must be ICANN-accredited and must have entered into a valid Registry-Registrar Agreement with the Registry Operator for the relevant TLD;
   b. ICANN must provide written assurance to the Registry Operator that the transfer would promote the interests of the community, for example, by avoiding risks to stability that may arise from the actual or imminent business failure of the Registrar.
2. If the Registry Operator is satisfied that the above two conditions have been met, then for a transfer involving no more than 50,000 registered domain names, the Registry Operator shall make a one-time modification to the Registry database at no charge. For a transfer involving more than 50,000 registered domain names, the Registry may charge the gaining Registrar a one-time fixed fee of USD 50,000.

7. Transfer Dispute Resolution Policy

The Transfer Dispute Resolution Policy prescribed by ICANN sets forth the procedures for handling disputes relating to inter-Registrar transfers of domain names. The relevant Registrars and ICANN-accredited Registrars must comply with the procedures outlined in that policy.

1. General Provisions

This Anti-Abuse Policy forms part of the .FANS Registry Policies and applies to the .FANS top-level domain managed by the Registry.

Unless otherwise defined herein, capitalized terms used in this document shall have the meanings assigned to them in the ICANN Registrar Accreditation Agreement, the Registry Agreement, or the Registry-Registrar Agreement, as applicable.

This document is provided in both Chinese and English. In the event of any inconsistency or conflict between the two language versions, the English version shall prevail.

2. General Terms

The registration and use of domain names under this top-level domain must comply with applicable laws and regulations, the Registry Policies, and the requirements imposed by ICANN under the Registry Agreement and the Registrar Accreditation Agreement, including ICANN Consensus Policies and Temporary Policies.

The Registry reserves the right to amend this Policy from time to time in accordance with applicable laws and regulations, ICANN requirements, or operational management needs. Any amendment or update to this Policy shall take effect thirty (30) days after publication on the Registry website, and shall be binding upon Registrars and Registrants.

3. Required Provisions in the Domain Name Registration Agreement

Registrars must require each domain name Registrant to enter into a Domain Name Registration Agreement. The Domain Name Registration Agreement must include the following provisions:

a. All relevant provisions expressly required under applicable laws and regulations, the Registrar Accreditation Agreement, and the Registry-Registrar Agreement;

b. Provisions prohibiting Registered Name Holders from distributing malware, operating botnets, engaging in phishing, piracy, trademark or intellectual property infringement, fraud or deceptive practices, counterfeiting, or otherwise engaging in activities contrary to applicable law, and provisions allowing the suspension of abusive domain names subject to applicable law and any relevant procedures.

3(A). Registration of Two-Character ASCII Labels

When offering the registration of two-character ASCII labels, the Registrar must obtain a written representation from the Registrant stating that, if the Registrant is not affiliated with, sponsored by, or endorsed by the government of the country or territory represented by the two-character label, or by the manager of the corresponding country-code top-level domain, the Registrant shall take measures to ensure that the registration of such two-character domain name does not create confusion or an improper implication of such affiliation, sponsorship, or endorsement.

3(B). URS High-Level Technical Requirements

In addition to other requirements under the Uniform Rapid Suspension procedure, where a complainant prevails in a URS proceeding, the Registrar must accept payment from the complainant and renew the domain name subject to the URS proceeding. Where the prevailing complainant’s right to renew has exceeded one year, the Registrar shall not further renew the URS domain name, assuming the domain name has not already reached the maximum allowable registration term.

3(C). Rights Protection Mechanisms

The Registrar acknowledges and agrees to comply with the rights protection mechanisms required under Specification 7 of the Registry Agreement, as well as any additional rights protection mechanisms established and implemented by the Registry pursuant to the relevant provisions of the Registry-Registrar Agreement.

4. Prohibited Use

The Registry expressly prohibits the use of domain names for any illegal or fraudulent purpose, including but not limited to distributing malware, operating botnets, engaging in phishing, piracy, trademark or intellectual property infringement, fraud, counterfeiting, or participating in any activity prohibited by law.

The Registry shall periodically conduct technical analysis to assess whether any domain name presents a security threat, including pharming, phishing, malware, botnets, or other forms of abuse.

5. Measures Against Domain Name Abuse

The Registry reserves all rights to deny or cancel a domain name registration, deny or cancel a transfer, place a domain name on “lock” or a similar status, or take other appropriate measures with respect to any domain name that violates any of the following:

a. The Registry Policies, including this Policy, and ICANN requirements;

b. Any threat posed by the domain name to the security and stability of the Registry, its operations, or the top-level domain;

c. Any requirement to comply with applicable laws and regulations, court orders, orders of administrative authorities, or decisions of arbitral bodies;

d. Any need to protect the rights of the Registry or third parties, or to protect the rights of the Registry and its affiliates, subsidiaries, owners, officers, directors, representatives, employees, contractors, or shareholders;

e. Any need to correct errors made by the Registry or a Registrar in connection with domain name registration or domain name reservation.

The Registry shall provide an abuse reporting channel through which the public may monitor and report abuse involving domain names under .FANS. Details of the abuse reporting channel may be found on the Registry’s official website.

1. General Provisions

This Sunrise Period Registration Policy forms part of the Registry’s Registration Policies and sets forth the domain name registration policy applicable to the Sunrise Period for the .fans top-level domain.

Unless otherwise defined herein, terms used in this document shall have the meanings assigned to them in ICANN’s Trademark Clearinghouse Rights Protection Mechanism Requirements, also known as the TMCH Requirements.

For more information regarding the TMCH Requirements, please visit: https://www.icann.org/resources/pages/tmch-requirements-2014-01-09-en.

This document is provided in both Chinese and English. In the event of any inconsistency or conflict between the two language versions, the English version shall prevail.

2. Sunrise Period and Notice

The Registry will offer a thirty (30)-day Sunrise Period registration service for .fans, followed by a Quiet Period and the General Availability period. The Registry will publish the start date and end date of the Sunrise Period on its official website.

During the Sunrise Period, trademark holders, or their authorized agents, may apply to register domain names under .FANS that match trademarks validated by the Trademark Clearinghouse.

3. Registration Requirements

Privacy registrations and proxy registrations are not available during the Sunrise Period. In addition, Sunrise Period registration applications must satisfy the following requirements:

a. The eligible trademark rights holder, or its authorized trademark agent, must submit a valid Signed Mark Data file, also known as an SMD file, issued by the Trademark Clearinghouse. The SMD file must be validated through the verification process prescribed by ICANN, and the information contained in the SMD file must match the applied-for domain name;

b. The registration application must comply with the Registry Policies, including the Registry’s String Policy and Reserved Names Policy.

4. Application Allocation

All applications submitted during the Sunrise Period shall be timestamped by the Registry system.

After the close of the Sunrise Period, valid Sunrise Period applications shall be allocated to the corresponding applicants. If multiple applications for the same domain name are received during the Sunrise Period, the domain name shall be allocated on a first-come, first-served basis.

5. Representations and Warranties

By submitting a Sunrise Period application, the applicant shall be deemed to:

a. Agree to be bound by this Sunrise Period Registration Policy, other Registry Policies, and the requirements imposed by ICANN under the Registry Agreement and the Registrar Accreditation Agreement, including ICANN Consensus Policies and Temporary Policies;

b. Represent and warrant that it is a trademark holder eligible to participate in the Sunrise Period, or an authorized agent of such trademark holder;

c. Agree to be bound by the Sunrise Dispute Resolution Policy adopted by the Registry for the resolution of disputes relating to Sunrise Period domain name registrations; and

d. Acknowledge, agree, and accept that it shall be solely and directly responsible for any damage caused to any third party arising from the Sunrise Period registration of a domain name, and shall indemnify, defend, and hold harmless the Registry and its employees, directors, managers, representatives, agents, affiliates, and contractors from and against any claims, damages, and liabilities, including those arising from any act, omission, or error.

6. Sunrise Dispute Resolution

Where a dispute arises in connection with a domain name registered during the Sunrise Period, the disputing party may submit the dispute to an ICANN-approved domain name dispute resolution service provider in accordance with the Registry’s Sunrise Dispute Resolution Policy.

The following three types of Sunrise Period domain name disputes may be subject to dispute resolution:

a. At the time the domain name was registered, the Registrant did not hold a valid national or regional trademark registration, the trademark relied upon by the Registrant had not been validated by a court of law, or the trademark was not protected by a statute or treaty in effect at the time;

b. The registered domain name is not an exact match to the trademark name on which the Registrant relied during the Sunrise Period;

c. The trademark registration relied upon by the Registrant at the time of domain name registration was not valid in any country or region, had not been validated by a court of law, or was not protected by an applicable statute or treaty.

1. General Provisions

This General Availability Registration Policy forms part of the Registry’s Registration Policies and sets forth the domain name registration policy applicable to the General Availability Period for the .FANS top-level domain.

Unless otherwise defined herein, terms used in this document shall have the meanings assigned to them in ICANN’s Trademark Clearinghouse Rights Protection Mechanism Requirements, also known as the TMCH Requirements.

For more information regarding the TMCH Requirements, please visit: https://www.icann.org/resources/pages/tmch-requirements-2014-01-09-en.

This document is provided in both Chinese and English. In the event of any inconsistency or conflict between the two language versions, the English version shall prevail.

2. General Availability

The General Availability Period refers to the period following the Sunrise Period and Quiet Period of the TLD, during which any Registrant that satisfies the registration eligibility requirements of the TLD may register domain names on a publicly available basis.

Registrants registering domain names during the General Availability Period must comply with all Registry Policies, including the String Policy, as well as the requirements imposed by ICANN under the Registry Agreement and the Registrar Accreditation Agreement.

Domain names during the General Availability Period shall be allocated on a first-come, first-served basis.

3. Landrush Period

The “Landrush Period” refers to the initial phases at the beginning of the General Availability Period, during which different domain name registration fees may apply to different phases.

4. Trademark Claims Service

As one of the trademark rights protection mechanisms under the Trademark Clearinghouse, the Registry will provide the Trademark Claims Service to domain name Registrants during the first ninety (90) days of the General Availability Period.

The purpose of the Trademark Claims Service is to provide prospective domain name Registrants with clear notice of the scope of rights held by relevant trademark holders.

When a domain name Registrant applies to register a domain name that matches a trademark record validated and recorded in the Trademark Clearinghouse, the domain name Registrant will receive a TMCH Trademark Claims Notice. The domain name Registrant may complete the domain name registration only after reviewing and accepting the Trademark Claims Notice.

After a domain name subject to a Trademark Claims Notice is registered, the relevant trademark holder will also receive a TMCH notice.

The relevant domain name dispute resolution policies prescribed by ICANN are available at the following links:

1. Uniform Domain Name Dispute Resolution Policy (UDRP)
   https://www.icann.org/resources/pages/help/dndr/udrp-en
2. Uniform Rapid Suspension System (URS)
   https://newgtlds.icann.org/en/applicants/urs
3. Transfer Dispute Resolution Policy (TDRP)
   https://www.icann.org/resources/pages/tdrp-2012-02-25-en
4. Sunrise Dispute Resolution Policy
   Please refer to the official website of the .fans Registry.

For more information, please refer to the DNSSEC Practice Statement available at:
https://www.centralnic.com/support/dps

ICANN Policies

• ICANN Consensus Policies
  https://www.icann.org/resources/pages/registrars/consensus-policies-en
• Uniform Domain Name Dispute Resolution Policy (UDRP)
  https://www.icann.org/resources/pages/help/dndr/udrp-en
• WHOIS Data Reminder Policy (WDRP)
  https://www.icann.org/resources/pages/registrars/consensus-policies/wdrp-en
• Inter-Registrar Transfer Policy
  https://www.icann.org/resources/pages/registrars/transfers-en
• WHOIS Marketing Restriction Policy (WMRP)
  https://www.icann.org/resources/pages/registrars/consensus-policies/wmrp-en
• Expired Registration Recovery Policy (ERRP)
  https://www.icann.org/resources/pages/registrars/consensus-policies/rnap-en
• Expired Domain Deletion Policy (EDDP)
  https://www.icann.org/resources/pages/registars/accreditation/eddp-en
• Registry Services Evaluation Policy (RSEP)
  https://www.icann.org/resources/pages/registries/rsep/policy-en
• Add Grace Period (AGP) Limits Policy
  https://www.icann.org/resources/pages/agp-policy-2008-12-17-en
• Expired Registration Recovery Policy (ERRP)
  https://www.icann.org/resources/pages/errp-2013-02-28-en
• Additional WHOIS Information Policy (AWIP)
  https://www.icann.org/resources/pages/policy-awip-2014-07-02-en
• Registry Registration Data Directory Services Consistent Labeling and Display Policy
  https://www.icann.org/resources/pages/rdds-labeling-policy-2017-02-01-en
• Protection of IGO and INGO Identifiers in All gTLDs Policy
  https://www.icann.org/resources/pages/igo-ingo-protection-policy-2018-01-16-en
• Interim Registration Data Policy for gTLDs
  https://www.icann.org/resources/pages/interim-registration-data-policy-en
• Uniform Rapid Suspension System (URS)
  https://newgtlds.icann.org/en/applicants/urs
• Trademark Clearinghouse (TMCH)
  https://newgtlds.icann.org/en/about/trademark-clearinghouse
• Post-Delegation Dispute Resolution Procedures (PDDRP)
  https://newgtlds.icann.org/en/program-status/pddrp

PRC Laws, Regulations, and Regulatory Documents

• Measures for the Administration of Internet Domain Names (Order No. 43 of the Ministry of Industry and Information Technology of the People’s Republic of China)
  http://www.miit.gov.cn/n1146295/n1146557/n1146624/c5778555/content.html
• Interpretation of the Measures for the Administration of Internet Domain Names
  http://www.miit.gov.cn/n1146295/n1652858/n1653018/c5778697/content.html
• Notice of the Ministry of Industry and Information Technology on Regulating the Use of Domain Names for Internet Information Services (MIIT ICT Administration [2017] No. 264)
  http://www.miit.gov.cn/n1146285/n1146352/n3054355/n3057709/n3057722/c5930543/content.html
• Cybersecurity Law of the People’s Republic of China (Order No. 53 of the President of the People’s Republic of China)
  http://www.miit.gov.cn/n1146295/n1146557/n1146614/c5345009/content.html
• Notice of the General Office of the Ministry of Industry and Information Technology on Issuing the Special Action Plan for Enhancing Network Data Security Protection Capabilities in the Telecommunications and Internet Industries
  http://www.miit.gov.cn/n1146295/n1652858/n1652930/n3757016/c7021335/content.html
• Notice of the Ministry of Industry and Information Technology on Issuing the Emergency Response Plan for Public Internet Cybersecurity Incidents
  http://www.miit.gov.cn/n1146285/n1146352/n3054355/n3057724/n3057729/c5920874/content.html
• Notice of the Ministry of Industry and Information Technology on Issuing the Measures for Monitoring and Handling Public Internet Cybersecurity Threats
  http://www.miit.gov.cn/n1146285/n1146352/n3054355/n3057724/n3057729/c5799583/content.html

1. General Provisions

These Implementation Rules for Domain Name Registration set forth the detailed rules relating to the registration of second-level domain names under .FANS.

These Rules are available in Chinese only and apply to users who submit registration requests for .fans second-level domain names through Registrars located in Mainland China.

2. Domain Name Registration Procedure

2.1 Selection of Registration Term

The registration of second-level domain names under .FANS follows the “first-come, first-served” principle.

The registration term of a domain name shall be calculated in years. The minimum registration term is one (1) year, and the maximum registration term is ten (10) years.

2.2 Checking Domain Name Availability

A Registrant may check whether a domain name is available for registration through the WHOIS lookup system on the official website of the .fans Registry or its authorized Registrars.

Scenario 1: If the queried domain name has not been registered, the query result will indicate that “the information you queried does not exist.” In this case, the Registrant may attempt to submit a registration application through a Registrar for the top-level domain.

Scenario 2: If the queried domain name has already been registered, the registration information of the domain name will be displayed. In this case, the Registrant may take the following actions:

1. Add a hyphen “-”, letters, or digits to the registered domain name, or use another combination, and then conduct another availability check;
2. Contact the “Registrant” shown in the WHOIS query result and seek to resolve any domain name dispute through negotiation.

Scenario 3: If the queried domain name is subject to protected registration, it means that only the corresponding protected entity may apply to register such domain name. If the queried domain name is prohibited from registration, it means that no user may apply to register such domain name.

For further details, please contact the .fans Registry or its accredited/authorized Registrars.

2.3 Checking Authorized Registrars

An authorized Registrar refers to an organization authorized by the .fans Registry to accept domain name registration applications from Registrants and directly complete the registration of domain names in the .fans top-level domain database.

Authorized Registrars of the .FANS Registry may be checked through the official website of the .fans Registry.

2.4 Contacting an Authorized Registrar to Submit a Registration Application

When applying to register a domain name, the Registrant shall submit the following domain name registration information to an authorized .fans Registrar in written or electronic form:

1. The domain name applied for;
2. The hostnames and IP addresses of the domain name servers;
3. If the applicant is a natural person, information or materials including but not limited to the applicant’s name, mailing address, telephone number, and email address; if the applicant is an organization, information or materials including but not limited to the entity name, organization code, mailing address, email address, and telephone number;
4. The names, mailing addresses, email addresses, and telephone numbers of the administrative contact, technical contact, billing contact, and handling person for the domain name;
5. The registration term of the domain name.

2.5 Entering into a Domain Name Registration Agreement with the Registrar

When handling domain name services, it is recommended that the Registrant enter into a Domain Name Registration Agreement with the authorized .fans Registrar and retain the relevant supporting documents to better protect the Registrant’s rights and interests.

2.6 Submission of Domain Name Verification Materials

When submitting a domain name registration application to the Registrar, the Registrant shall also submit relevant domain name verification materials, which generally include:

1. Identity documentation of the Registrant;
2. Identity documentation of the registered organization or institution;
3. Other relevant materials.

2.7 Verification of Domain Name Registration Information

The Registrant may verify the submitted registration information through the following channels:

1. The WHOIS lookup system on the official website of the .fans Registry;
2. The WHOIS lookup system on the official website of an authorized .fans Registrar.

2.8 Domain Name Verification

The domain name registered by the Registrant must satisfy the following requirements to pass review:

1. The domain name must comply with the requirements of the Measures for the Administration of Internet Domain Names, Order No. 43 of the Ministry of Industry and Information Technology of the People’s Republic of China;
2. The domain name registration information must be true, accurate, and complete, and must be capable of being verified through data from competent national authorities;
3. The application materials must match the registration information shown in the WHOIS lookup system.

The standard review period is five (5) business days from the date on which the online application for the domain name is submitted.

First, the Registrar shall conduct a preliminary review of the domain name registration information and materials. After the domain name passes the Registrar’s preliminary review, the Registrar shall submit the application materials to the .fans Registry, and the .fans Registry shall conduct a secondary review.

If the application fails the review, the system will delete the domain name information. The .FANS Registry will notify the technical service provider and the Registrar of the result, and the Registrar will notify the Registrant that the registration has failed.

If the application passes the review, the applied-for string will proceed to the next stage. The Registrant may monitor the review progress and domain name status through the Registrar.

3. Website Filing

After the Registrant’s domain name passes review, the domain name registration is deemed successful.

The domain name itself does not require filing. However, if the Registrant uses the domain name for a website, the Registrant shall complete website filing, also known as ICP filing, in accordance with the relevant website administration requirements of the Ministry of Industry and Information Technology.

Website filing is not handled or approved by the .fans Registry. The user shall contact the Internet access service provider associated with the domain name and submit the filing application to the provincial communications administration.

In accordance with the requirements of MIIT Document Dian Guan [2009] No. 672, domain names used for websites that have not completed website filing shall not be resolved, including forwarding. If a newly registered .fans second-level domain name has not completed website filing, it cannot be resolved or used temporarily.

After the Registrant obtains the website filing number, the Registrant may provide such number to the Registrar of the domain name, and the Registrar shall process the Registrant’s application to activate the domain name.

4. Domain Name Resolution

After successfully registering a domain name, the Registrant must configure domain name resolution before the domain name can be used. The specific activation steps are as follows:

Step 1: The user configures the relevant DNS resolution settings with the DNS service provider;

Step 2: The user configures the domain name server, or NS, settings in the domain name management panel provided by the Registrar.

5. Change of Domain Name Holder

If the domain name holder applies to transfer the domain name to a new holder, the new domain name holder shall submit all required registration information and materials.

The Registry shall conduct real-name verification of the relevant materials submitted by the new domain name holder. Applications that pass verification shall be approved, and the WHOIS information shall be updated promptly after the change of holder is completed.

For applications that fail real-name verification, the change of domain name holder shall be rejected.

6. Domain Name Cancellation

The Registry has the right to cancel domain names that are not renewed upon expiration or that violate applicable rules or policies.

7. User Supervision

If the user fails to submit the relevant registration information and domain name verification materials promptly, the registration system will be unable to ensure successful domain name registration.

During the registration process, the technical platform will conduct both system verification and manual verification to ensure the authenticity and accuracy of the registration information and verification materials submitted by the user.