This Naming Policy is incorporated by reference into the Registration Agreements between registrars and registrants. It specifies the naming policy for .FANS TLD and forms part of the Registry Policy. It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
A domain name is a combination of multiple lables (or "string" herein). Any domain label must meets the requirements of section 3.5 in RFC 1034. The Registry won’t accept a registration request unless the requested string meets the requirements set out in this policy and any other applicable Registry Policies.
An ASCII string or a A-Label string transformed from Chinese:
a.a second level domain must have at least 1 character and not more than 63;
b.may contain the 26 letters of the Latin alphabet,“a-z”(case insensitive), the ten digits, "0-9" , and a hyphen, "-";
c.cannot start or end with a hyphen, "-";
d.must not have two hyphens appearing in the third and fourth positions, e.g. "ab--cd" is not permitted.
IDNs, also known as internationalized domain names or multilingual domain names, are a general term of domain name systems for non-English speaking countries to promote their own languages. For example, a domain name containing Japanese is a Japanese domain name, a domain name containing Chinese is a Chinese domain name.
The registry does not support IDNs for the time being, and whether it will be open later, please see the registry official website.
This Reserved Names Policy specifies the reserved names policy for .FANS TLD and forms part of the Registry Policy. It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
In addition to ICANN's requirement to reserve certain strings, the Registry will reserve(i.e., withhold from registration or allocate to the Registry, but not register to third parties, delegate, use, activate in the DNS or otherwise make available) or block additional character strings within .fans TLD at its discretion. The Registry establishes a system for key words in registered domain names in accordance with relevant laws and regulations. Each registration request is checked against the Reserved Names list. If the request is for a Reserved Name, it will not be accepted by the Registry.
3.Reserved Names List
The Registry shall maintain a Reserved Names list consisting of names, labels or additional character strings:
a.mandated by ICANN to be reserved or blocked ( “ICANN Requirements”);
b.reserved under applicable laws or regulations (“Local Laws or Regulatory Requirements”); and
c.reserved under Registry’s marketing or strategic programs (“Marketing Programmes”).
The Registry reserves the right to add to or remove names from the Reserved Names list at its discretion, provided that such change is not inconsistent with the ICANN Requirements and the Local Laws or Regulatory Requirements.
3(a). ICANN Requirements
Unless ICANN expressly authorizes in writing, the following labels are reserved or blocked from registration:
a.The ASCII label “EXAMPLE”.
b.Some two-character ASCII labels.
c.Labels reserved for registry operations.
d.Country and Territory Names.
e.International Olympic Committee; International Red Cross and Red Crescent Movement.
g.Certain strings within .fans TLD reserved according to Name Collision Occurrence Assessment provided by ICANN.
3(b). Local Laws or Regulatory Requirements
The Internet Domain Name Regulations promulgated by the Ministry of Industry and Information Technology of the People's Republic of China stipulate: “No organization or individual may register or use names containing elements that:
a.Oppose the fundamental principles of the Constitution;
b.Compromise national security, divulge state secrets, subvert the government or damage national unity;
c.Damage national honor and interest;
d.Incite ethnic hatred or ethnic discrimination, undermining people unity;
e.Violate state religion policies or propagate heretical teachings or feudal superstitions;
f.Spread rumors, disturb social order or undermine social stability;
g.Spread obscenity, pornography, gambling, violence, murder, terrorism or incite the commission of crimes;
h.Insult or slander others or infringe upon the legitimate rights and interests of a third party; or
i.Contain other content prohibited by laws and administrative regulations.”
Accordingly, names that are deemed in violation of the Regulations are blocked from registration.
Names that are reserved under a .fans marketing programmes are also considered Reserved Names. The Registry may allocate these Reserved Names under such Marketing Programmie sale or aucton from time to time. Once a Reserved Name is allocated, it will be removed from the Reserved Names list.
4.Update to Reserved list
Name reserved under ICANN policy will be updated upon ICANN’s notification or update to policies from time to time.
Name reserved under Local Laws or Regulatory Requirements will be updated according to the regulations of the telecommunications authorities and relevant national authorities.
Name reserved upon the Registry's own marketing programmes will be updated from time to time at registry’s sole discretion.
5.Activation of Reserved Names
A Reserved Name may be registered and activated provided the intended registrant presents the Registry a letter of consent issued by the rights holder authorizing the intended registrant to register the domain name.
For more information, contact .fans registry or its accredited registrars.
This Privacy & Whois/RDAP Policy specifies the privacy & whois/RDAP policy for .FANS TLD and forms part of the Registry Policy. It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
The objectives of this Privacy & Whois/RDAP Policy are:
a.To disclose to the Registrant, and in doing so obtain the Registrant’s consent to, the fact that certain Personal Information provided by the Registrant may be dealt with in the following manner by the Registry:
1)Personal Information shall be collected and may be used, maintained, and/or corrected from time to time in accordance with this and/or other Registry Policies or practices;
2)Personal Information shall be collected by the Registry through the Registrar for the purpose of the storage, maintenance, disclosure, and/or use of such Personal Information. The Registry may disclose or transfer such Personal Information to any third party (in addition to ICANN and the Registry Escrow Agent), under the circumstances detailed in the “Use and Disclosure” section of this Privacy & Whois/RDAP Policy;
3)All Personal Information about the Registrant which is supplied to the Registry, or a Registrar, may be available to third parties by way of a public “Whois” and/or “RDAP” service, consistent with:
• Privacy principals of the Registry;
• The Registry Policies;
• ICANN Consensus Policies; and/or
• Applicable laws, rules and regulations.
b.To outline the Registry’s procedures for the appropriate collection, holding, use, correction, disclosure, and transfer of a Registrant’s Personal Information by the Registry.
In order to provide Registry services in any TLD, the Registry is required by ICANN to collect and publish data pertaining to the identity of the Registrant of any domain name.
The following terms are used in this Privacy & Whois/RDAP Policy as defined below.
a.“Data Escrow Agent” means a third party contracted to perform data escrow services for the Registry. The data escrow agreement with the Escrow Agent ensures the transfer of all relevant DNS data and Registrant information, including Personal Information, to ICANN and an ICANN-mandated back-up registry operator (“EBERO” or Emergency Back End Registry Operator), and will ensure the safety and integrity of the Registry’s TLD database. The Escrow Agent is prohibited from use or disclosure of the Registry’s TLD data unless that use or disclosure is deemed essential to ensure the stability and integrity of the Registry’s TLD.
b.“Personal Information” means information about an individual person, including any Registrant, whose identity can reasonably be ascertained from such information, but does not include indexes or aggregations of Personal Information relating to more than one person, such as logfiles, DNS Zone Files, databases or backups. This information may include the name, address, telephone number, and email address of the Registrant. This may include the home address and personal email of the Registrant, if the Registrant uses those as their primary contact information for the domain name.
c.The “Primary Purpose” of the collection of Personal Information is the storage and maintenance of such information in the Whois/RDAP database (a copy of which ICANN requires is provided to the Escrow Agent) as required by ICANN, which is searchable and publicly available. No domain name can be registered without the Registry collecting such Personal Information and making it publicly available in the Whois/RDAP database.
4.“Whois/RDAP” Server Implications
The Registry will maintain a publicly accessible information service known as the Registry’s “Whois” and/or a “RDAP” service. The Whois system is a standard service operated by all domain name registries and Regional Internet Registries (RIRs) and is used by third parties to obtain information about registered domain names. RDAP is a replacement for Whois which is gradually being phased in, and provides the same information but in a structured, machine-readable data format.Whois and/or RDAP service provides the following information pertaining to a domain name, pursuant to ICANN’s Consensus Policies, which may be amended at any time and from time to time:
a.Technical information on the DNS servers resolving a domain name;
b.The date the domain name was inserted into the Registry’s database;
c.The date of last modification;
d.The date of expiration;
e.The current status of the domain name;
f.The Registrar’s contact details;
g.The Registrant’s name;
h.The Registrant’s physical address and/or alternate address;
i.The Registrant’s email and phone numbers and/or alternate address;
j.The Registrant’s state and/or alternate address;
k.The Registrant’s country and/or alternate address.
l.Details of nominated administrative, technical and billing contacts.
5.Collectiona.The Registry collects Personal Information for one or more of its functions and/or activities including, where required:
1)to identify and maintain contact details of domain name Registrants and their duly appointed agents;
2)to provide access to that data to the public and persons connected with Registrants;
3)to provide services to Registrants and maintain its database;
4)for the provision of Whois and/or RDAP service;
5)to contact the Registrant, including notifications in accordance with the Registry Polices; and/or,
6)to provide law enforcement, government agencies, and relevant Internet security organisations with information required to investigate or prevent an alleged crime.
b.The Registry’s website utilizes technology that collects user information and tracks usage (e.g., via “cookies”). The Registry’s website may feature links to other third party websites but the Registry is not responsible for the content and privacy practices of any such third party websites.
Domain name registration information is stored in a central database. This database is hosted in secure colocation facilities and is protected by enterprise-grade firewalls and an Information Security Management System certified against ISO 27001.
We take regular backups of the database to ensure continuity of service. All backups are stored in an encrypted format and are transmitted to secure off-site locations using encrypted communications channels to prevent unauthorized access.
7.Use and Disclosurea.The Registry may use or disclose Personal Information about a Registrant for a purpose other than the Primary Purpose of collection where:
1)The Personal Information consists of the contact details of a person connected to a Registrar, Internet service provider, Internet service reseller, or persons connected thereto, such as directors, managers or other points of contact;
2)The Registrant has consented to such use or disclosure; or
3)The Registry believes in its sole judgment that the 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
• Because the Registry has reason to suspect that unlawful activity or a violation of the any of the Registry's Policies has been, is being, or may be engaged in, and uses or discloses the Personal Information as a necessary part of its investigation of the matter or in reporting its concerns to relevant persons (including parties affected by that violation) or authorities; or
• Because the use or disclosure is required or authorised by or under law, rule or regulation; or
• Because the Registry believes that the use or disclosure is necessary for one or more of the following, by or on behalf of an enforcement body:
• The prevention, detection, investigation, prosecution, or punishment of criminal offences, breaches of a law imposing a penalty or sanction, or breaches of a prescribed law;
• The preparation for, or conduct of, proceedings before any court or tribunal, or implementation of the orders of a court or tribunal; or
• As ordered by a dispute resolution provider in connection with a Uniform Domain Name Dispute Resolution Policy (UDRP) or Universal Rapid Suspension (URS) proceeding, as mandated by ICANN.
• As decided by parties resulting from a CRS dispute.
• For any other legal purpose.
b.Nothing in this Section 7 “Use and Disclosure” requires the Registry to disclose any Personal Information; the Registry is always entitled not to disclose Personal Information in the absence of a legal obligation to disclose it.
c.The Registry may also be subject to the requirements of present, and any future, policy dealing with cross-border data flows if it transfers Personal Information to a person or entity in a foreign country situated outside of the People’s Republic of China.
d.The Registry maintains and uses servers in diverse locations internationally, necessitating transfer of data, including Personal Information, between servers and data networks.
When a domain name is deleted, unless the registrar has opted out, any contact information associated with the domain will be deleted, if the records are no longer needed for other domains in the database. This also occurs if a domain is updated to use different contact information (such as when a domain changes ownership).
Registrars who have chosen to opt-out of this system are expected to delete their own unused contact information and the Registry enforces this requirement by providing monthly reports, and reserves the right to opt registrars back in to automatic purging if they fail to manage their contact information properly.
The Registry may—but is not obligated to—take steps to make sure that the Personal Information it collects, uses or discloses is accurate, complete, and up-to-date. This may include active email, SMS, or phone communication from the Registry to the Registrant that bypasses the sponsoring Registrar.
The Registry shall take the steps required by ICANN and by the laws of the People’s Republic of China to protect the Personal Information it holds from misuse and loss and from unauthorised access, modification or disclosure to the extent required by law.
This Privacy & Whois/RDAP Policy sets out the Registry’s policies concerning its management of Personal Information. The Registry shall make this document available to anyone who asks for it and on its website.
12.Access and Correction
a.If the Registry holds Personal Information about a Registrant, it shall provide that Registrant with access to such information upon receipt of written request by the Registrant, except to the extent that the Registry believes in its sole discretion:
1)In the case of Personal Information, providing access may pose a serious and imminent threat to the life or health of any individual; or
2)Providing access may have an unreasonable impact upon the privacy of other individuals; or
3)The request for access is frivolous or vexatious; or
4)The information relates to existing or anticipated legal proceedings and the information would not be accessible by the process of discovery in those proceedings; or
5)Providing access may be unlawful; or
6)Denying access may be required or authorised by or under law, rule or regulation, including, but not limited to, the order of any court having appropriate jurisdiction; or
7)Providing access may prejudice an investigation of possibly unlawful activity; or
8)Providing access may prejudice:
• The prevention, detection, investigation, prosecution or punishment of criminal offences, or other breaches of law; or
• The preparation for, or conduct of, proceedings before any court or tribunal, or implementation of its orders; or
• A law enforcement body or relevant Internet security organisation performing a lawful security function requests that the Registry not provide access to the information on the basis that providing access would be likely to cause harm.
b.The Registry shall not in any event be under any obligation to disclose DNS Zone Files, payment logs, email archives, or data backups to any party, except as required by ICANN, law, or court order.
c.Where providing access would reveal evaluative information generated within the Registry in connection with a commercially sensitive decision-making process, the Registry may give the Registrant an explanation for the commercially sensitive decision rather than access to the information.
d.If the Registry holds Personal Information about a Registrant and the Registrant is able to establish that the information is not accurate, complete, and up-to-date, upon notice of such fact from the Registrant, the Registry shall take reasonable steps to correct the information so that it is accurate, complete, and up-to-date as requested by the Registrant, except where the data is contained in an historical record or archive.
13.Review of Policy
The Registry reserves the right to review or revise this Privacy & Whois/RDAP Policy at its sole discretion at any time and from time to time, including to maintain compliance with ICANN Consensus Policy or other applicable law or regulation; Registrants who have provided their Personal Information to the Registry are deemed to acknowledge and be bound by this Privacy & Whois/RDAP Policy and any changes made to it. The current version of the Privay & Whois/RDAP Policy will made available on the Registry website. It applies to any domain name registered in the TLD, no matter when or how registered, renewed, or transferred. Where a Registrant licenses or leases the domain name or any sub-domain names obtained under these Registry Policies, the Registry and the sponsoring Registrar shall hold the Registrant solely liable for activity in the domain name and in any sub-domain, if applicable.
This Transfer Policy specifies the transfer policy for .FANS TLD and forms part of the Registry Policy. It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
Domain transfer means a domain to tranfer from a the Registrar of Record to a ganing registrar. Registered Name Holders must be able to transfer their domain name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum standards of ICANN Transfer policy and that such transfer is not prohibited by ICANN or Registry policies.
The Administrative Contact and the Registered Name Holder, as listed in the Losing Registrar's or applicable Registry's (where available) publicly accessible Whois/RDAP service are the only parties that have the authority to approve or deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registered Name Holder's authority supersedes that of the Administrative Contact.
4.Obligations of the Registrar of Record
a.The losing registrar shall provide the transfer password unconditionally after confirming the identity of the user.
b.Upon denying a transfer request for any of the following reasons, the Registrar of Record must provide the Registered Name Holder and the potential Gaining Registrar with the reason for denial. The Registrar of Record may deny a transfer request only in the following specific instances:
1)Evidence of fraud.
2)Reasonable dispute over the identity of the Registered Name Holder or Administrative Contact.
3)No payment for previous registration periodif the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired.
4)Express objection to the transfer by the authorized Transfer Contact.
5)The transfer was requested within 60 days of the creation date as shown in the registry Whois/RDAP record for the domain name.
6)A domain name is within 60 days (or a lesser period to be determined) after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision in the dispute resolution process so directs). "Transferred" shall only mean that an inter-registrar transfer has occurred in accordance with the procedures of this policy.
c.The Registrar of Record must deny a transfer request in the following circumstances:
1)A pending UDRP proceeding that the Registrar has been informed of.
2)Court order by a court of competent jurisdiction.
3)Pending dispute related to a previous transfer pursuant to the Transfer Dispute Resolution Policy.
4)URS proceeding or URS suspension that the Registrar has been informed of.
5)The Registrar imposed a 60-day inter-registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request.
d.Instances when the requested change of Registrar may not be denied include, but are not limited to:
1)Nonpayment for a pending or future registration period.
2)No response from the Registered Name Holder or Administrative Contact.
3)Domain name in Registrar Lock Status, unless the Registered Name Holder is provided with the reasonable opportunity and ability to unlock the domain name prior to the Transfer Request.
4)Domain name registration period time constraints, other than during the first 60 days of initial registration, during the first 60 days after a registrar transfer, or during the 60-day lock following a Change of Registrant pursuant to ICANN Transfer Policy.
5)General payment defaults between Registrar and business partners / affiliates in cases where the Registered Name Holder for the domain in question has paid for the registration.
When domain transfer, the user need to extended expiration date for another year through the ganing registrar
a.Transfer of the sponsorship of all the registrations sponsored by one Registrar as the result of (i) acquisition of that Registrar or its assets by another Registrar, or (ii) lack of accreditation of that Registrar or lack of its authorization with the Registry, may be made according to the following procedure:
1)The gaining Registrar must be accredited by ICANN for the Registry TLD and must have in effect a Registry-Registrar Agreement with Registry Operator for the Registry TLD.
2)ICANN must certify in writing to Registry Operator that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual or imminent business failure of a Registrar.
b.Upon satisfaction of these two conditions, the Registry will make the necessary one-time changes in the Registry database for no charge, for transfers involving 50,000 name registrations or fewer. If the transfer involves registrations of more than 50,000 names, the Registry will charge the gaining Registrar a one-time flat fee of US$ 50,000.
7.Transfer Dispute Resolution Policy
Procedures for handling disputes concerning inter-registrar transfers are set forth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operators and ICANN accredited Registrars.
This Anti-abuse Policy specifies the anti-abuse policy for .FANS TLD and forms part of the Registry Policy. Unless otherwise defined, the terms used in this document are consistent with the meaning of the ICANN Registrar Accreditation Agreement, the Registry Agreement, or the Registry-Registrar Agreement. It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
Registration and use of domain names in .fans TLD are subject to all applicable laws and regulations, all Registry Policies and ICANN requirements set out in the Registry Agreement and the RAA, including all ICANN Consensus Policies and Temporary Policies.
The Registry reserves the right to amend or update this policy from time to time to take into account new laws or ICANN requirements, changes to technology or Registry’s operations and practices. Any amendments or update to this policy shall be effective and binding upon registrars and registrants thirty (30) days after the initial date of posting on the Registry’s official website.
3.Terms in Registration Agreements
Registrars must require all Registered Name Holders to enter into an electronic or paper Registration Agreement with the sponsoring registrar. Each Registration Agreement must include:
a.all the provisions specified in any applicable law, the RAA(Registry Accreditation Agreement) and the RRA(Registry-Registrar Agreement).
b.Registered Name Holders are prohibited from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name.
3A. Registration of Two-character ASCII Labels
Registrar must require a Registered Name Holder of a two-character ASCII label at the second level to represent and warrant in writing that the Registered Name Holder will take steps to ensure against misrepresentation or falsely implying that the Registered Name Holder or its business is affiliated with a government or a country-code manager if such affiliation, sponsorship or endorsement does not exist.
3B.URS High-Level Technical Requirements
In addition to any other requirement under the URS, Registrar must accept and process payments for the renewal of a Registered Name by a URS Complainant in cases where the URS Complainant prevailed and Registrar must not renew a Registered Name to a URS Complainant who prevailed for longer than one year (if allowed by the maximum validity period of the TLD).
3C.Rights Protection Mechanisms
Registrar acknowledges and agrees that all RPMs required by Specification 7 to each of the Registry Agreement and any additional RPMs developed and implemented by Registry Operator are incorporated by reference into the RRA.
The Registry expressly prohibits abusive use of a domain name for any illegal or fraudulent activities, including but not limited to, distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law.
The Registry will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets.
5.Contravention of Anti-Abuse Policy
The Registry reserves the right to deny, cancel or transfer any registration or transaction, or place any domain name(s) on registry lock, hold or similar status, that it deems necessary, in its discretion:
a.to enforce any Registry Policies (including this policy) and ICANN requirements, as amended from time to time;
b.to protect the integrity and stability of Registry Operator, its operations, and the TLD;
c.to comply with any applicable law, regulation, holding, order, or decision issued by a court, administrative authority, or dispute resolution service provider with jurisdiction over Registry Operator or registrants;
d.to establish, assert, or defend the legal rights of Registry Operator or a third party, or to avoid any liability, civil or criminal, on the part of Registry Operator as well as its affiliates, subsidiaries, owners, officers, directors, representatives, employees, contractors, and stockholders; and
e.to correct mistakes made by Registry Operator or a registrar in connection with a registration or reservation of the domain name.
The Registry will provide abuse contact for the public to supervise and report on domain name abuse under .FANS TLD, which can be found on the Registry’s official website.
This Registry Sunrise Registration Policy specifies the registry sunrise registration policy for .FANS TLD and forms part of the Registry Policy. Unless otherwise defined herein, capitalized terms used in this document have the meanings given to them in the ICANN’s Trademark Clearinghouse Rights Protection Mechanism Requirements available at https://www.icann.org/resources/pages/tmch-requirements-2014-01-09-en. It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
The Registry will offer a Start-Date Sunrise for thirty (30) calendar days (“Sunrise Period”), followed by a quiet period prior to the start of General Registration. The start-date and end-date for the Sunrise Period will be published on the Registry’s official website. During the Sunrise Period, holders of eligible trademarks that have been validated by the Trademark Clearinghouse may apply to register domain names in the TLD.
Privacy or proxy services may not be used in connection with applications submitted during the Sunrise Period. In addition, an application for a Sunrise Registration must meet the following criteria (a “Valid Sunrise Application”):
a.valid SMD file from the Sunrise-Eligible Rights Holder (or its agent) matching the applied-for domain name was provided and the validation procedures described in the Functional Specifications were performed; and
b.it complies with all applicable Registry Policies(including the Registry’s Naming policy and Reserved Names Policy).
All applications received during the Sunrise Period will be time-stamped as they are received in the registry system. After the Sunrise Period ends, the applied-for domain name will be allocated to the applicant of a Valid Sunrise Application and if two or more Valid Sunrise Applications are received, it will be allocated on a first-come, first-served basis.
5.Representations and Warranties
By making a Sunrise Registration application, the applicant:
a.agrees to be bound by this Sunrise Policy, all other Registry Policies and ICANN requirements set out in the Registry Agreement, including all ICANN Consensus Policies and Temporary Policies;
b.represents and warrants that it is a Sunrise-Eligible Rights Holder or its duly authorized agent;
c.agrees to submit to any challenges filed in accordance with the Registry’s Sunrise Dispute Resolution Policy; and
d.acknowledges, agrees, and accepts sole and direct liability for damages suffered by any third party injured as a consequence of an application and/or the Sunrise Registration under this Sunrise Policy, and agrees to indemnify and hold the Registry and its employees, directors, officers, representatives, affiliates, agents, and contractors harmless for any claims, causes of action, damages, or injuries resulting from actions, omissions, or errors.
6.Sunrise Dispute Resolution
Challenges to Sunrise Registrations on the following grounds may be filed with ICANN accredited Dispute agents.
a.at the time the challenged domain name was registered, the registrant did not hold a trademark registration of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty;
b.the domain name is not identical to the mark on which the registrant based its Sunrise Registration; or
c.the trademark registration on which the registrant based its Sunrise Registration is not of national effect (or regional effect) or the trademark had not been court-validated or protected by statute or treaty.
This Registry General Registration Policy specifies the registry general registration policy for .FANS TLD and forms part of the Registry Policy. Unless otherwise defined herein, capitalized terms used in this document have the meanings given to them in the ICANN’s Trademark Clearinghouse Rights Protection Mechanism Requirements available at https://www.icann.org/resources/pages/tmch-requirements-2014-01-09-en.It’s available in Chinese and English, and the English version prevails in the event of inconsistencies or inconsistencies between two versions.
2.General Registration Commencement
After conclusion of the Sunrise Period and any subsequent quiet period, General Registration commences when available domain names in the TLD are open to the general public for registration.
A General Registration application must meet all Registry Policies (including the Registry’s Naming Policy) and ICANN requirements set out in the Registry Agreement and the Registrar Accreditation Agreement to be considered a valid application. Valid applications will be allocated on a first-come, first-served basis.
Variable initial registration fees apply to first few weeks of General Registration (known as the “Landrush Period”). During the Landrush Period, interested parties may apply for available domain names in the TLD. After conclusion of the Landrush Period, available domain names in the TLD are open to the general public for registration at a regular initial registration fee.
4.Trademark Claims Services
As part of the TMCH Requirements, Registry Operator will provide the Claims Services for the first ninety (90) calendar days of General Registration.
The “Claims Services” provide (i) a notice to potential domain name registrants that a domain name they are seeking to register in the TLD matches a Trademark Record (a “Claims Notice”); and (ii) a notification to the Trademark Holder.
A Claims Notice is intended to provide clear notice to the potential domain name registrant of the scope of the Trademark Holder’s rights. Accordingly, during the first 90 days of General Registration, a potential domain name registrant may only complete the domain name registration following acknowledgement of the receipt of a Claims Notice.
• Notice of the General Office of the Ministry of Industry and Information Technology on Printing and Distributing the Special Action Plan for Enhancing Network Data Security Protection Capabilities in the Telecom and Internet Industry