• String Policy
  • Reserved Names Policy
  • Privacy Protection and WHOIS/RDAP Policy
  • Domain Name Transfer Policy
  • Anti-Abuse Policy
  • Sunrise Registration Policy
  • General Availability Registration Policy
  • Domain Name Dispute Resolution Policies
  • DNSSEC Practice Statement
  • ICANN Policies
  • Domain Name Registration Implementation Rules
  • Website Privacy Policy
  • Website Terms of Use

1. General

This Registry String Policy is incorporated by reference into the Registration Agreement between the Registrar and the Registrant. It forms an integral part of the Registry Policies and establishes the requirements governing the registration of second-level domain names under the .REN Top-Level Domain (TLD).


2. Technical Requirements for Domain Name Strings

A domain name consists of one or more labels (each referred to in this Policy as a "string"). Each domain name label must comply with the requirements set forth in Section 3.5 of RFC 1034. Any application for a domain name that does not comply with this String Policy (or any other applicable Registry Policy) shall not be accepted for registration.


3. ASCII Strings

ASCII domain names, including A-labels derived from Internationalized Domain Names (IDNs), must comply with the following requirements:

  1. The second-level domain label must not exceed 63 ASCII characters.

  2. The string may contain only the letters a–z (case-insensitive), the digits 0–9, and the ASCII hyphen (-).

  3. A hyphen (-) must not appear at the beginning or end of the string.

In addition, the third and fourth characters of an ASCII domain label must not both be hyphens. For example, a domain name such as ad--cd.ren is not eligible for registration.


4. Internationalized Domain Name (IDN) Strings

Internationalized Domain Names (IDNs) enable domain names to be represented in languages and scripts other than English.

All IDN labels must satisfy the "IDNA-valid" requirements specified in Section 2.3.2.1 of RFC 5890. The .REN Registry supports Chinese-language IDN strings in accordance with RFC 4713. Only Chinese characters included in the following IDN tables are supported:

CNNIC IDN Table

http://www.iana.org/domains/idn-tables/tables/cn_zh-cn_4.0.html;

TWNIC IDN Table

http://www.iana.org/domains/idn-tables/tables/tw_zh-tw_4.0.1.html

1. General

This Reserved Names Policy forms part of the .REN Registry Policies and sets forth the rules governing reserved domain names within the .REN Top-Level Domain (TLD).


2. Reserved Domain Names

In addition to the strings that must be reserved pursuant to ICANN requirements, the Registry reserves the right, at its sole discretion, to reserve (including refusing registration, allocating to the Registry, withholding from delegation in the DNS, or otherwise withholding from public registration or use) or prohibit the registration of additional strings.

The Registry maintains a Reserved Names List in accordance with applicable laws, regulations, and Registry policies. Every domain name application is checked against this list. If the requested domain name appears on the Reserved Names List, the registration request will be rejected.


3. Categories of Reserved Domain Names

The Registry's Reserved Names List includes, but is not limited to, the following categories:

  1. Names reserved pursuant to ICANN requirements;

  2. Names reserved under applicable laws and regulations;

  3. Names reserved by the Registry for marketing, promotional, or operational purposes.

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


3(A). ICANN Reserved Names

The following categories of names are reserved in accordance with ICANN requirements:

  1. The English word "example";

  2. Certain two-character labels;

  3. Registry Operator Reserved Names;

  4. Country and Territory Names;

  5. Names relating to the International Olympic Committee (IOC), the International Red Cross and Red Crescent Movement, and related protected identifiers;

  6. Names of Intergovernmental Organizations (IGOs);

  7. Any names prohibited from registration under ICANN's Name Collision management policies applicable to the .REN TLD.


3(B). Names Reserved Under Applicable Laws

Pursuant to the applicable laws and regulations of the People's Republic of China, including the Administrative Measures for Internet Domain Names issued by the Ministry of Industry and Information Technology (MIIT Order No. 43), the .REN Registry does not permit the registration of domain names that contain content prohibited by applicable law.

This includes, without limitation, names that:

  1. Oppose the fundamental principles established by the Constitution of the People's Republic of China;

  2. Endanger national security, disclose state secrets, subvert state power, or undermine national unity;

  3. Harm the honor or interests of the State;

  4. Incite ethnic hatred or discrimination or undermine ethnic unity;

  5. Undermine the State's religious policies or promote cults or superstition;

  6. Spread rumors, disrupt public order, or undermine social stability;

  7. Contain obscene, pornographic, gambling-related, violent, terrorist, or criminal content, or encourage criminal activities;

  8. Defame others or infringe upon the lawful rights and interests of others; or

  9. Contain any other content prohibited by applicable laws or administrative regulations.

The Registry will reject the registration of any domain name that falls within the above categories, including obvious character variants or equivalent representations.


3(C). Registry Marketing Reserved Names

The Registry may reserve certain domain names for marketing, promotional, strategic, or commercial purposes.

Such reserved names may be released through direct allocation, premium sales, auctions, or other distribution mechanisms determined by the Registry. Once allocated, a reserved name will be removed from the Reserved Names List.


4. Updates to the Reserved Names List

The Reserved Names List may be updated from time to time as follows:

Names reserved pursuant to ICANN requirements will be updated in accordance with applicable ICANN policies, specifications, and notices.

Names reserved under applicable laws or regulations will be updated to reflect requirements issued by the relevant telecommunications authorities or other competent governmental authorities.

Names reserved for Registry marketing or operational purposes may be added to or removed from the Reserved Names List at the Registry's discretion.


5. Registration or Activation of Reserved Names

Where a reserved domain name may be registered or activated under applicable policies, an applicant may submit a request through a Registry-accredited Registrar together with documentation demonstrating the necessary authorization or rights granted by the relevant rights holder.

For additional information, please contact your Registrar or the Registry.

1. General

This Privacy Protection and WHOIS/RDAP Policy forms part of the .REN Registry Policies and sets out the Registry's policies regarding the collection, use, disclosure, storage, and management of registration data, as well as the operation of the WHOIS and RDAP services for the .REN Top-Level Domain (TLD).


2. Purpose

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

2.1 Inform Registrants that certain personal information they provide may be collected, processed, stored, disclosed, and otherwise handled by the Registry, and to obtain the Registrant's consent to such processing, including that:

  1. Personal Information may be collected, used, maintained, updated, and otherwise processed in accordance with this Policy and other applicable Registry Policies or established Registry practices.

  2. Personal Information is collected by the Registry through the Registrar for the purposes of storage, maintenance, use, and disclosure. Except for ICANN and the Registry's Data Escrow Agent, such information may be disclosed or transferred to third parties only under the circumstances described in the Use and Disclosure section of this Policy.

  3. The Registrant acknowledges and agrees that the personal information provided to the Registry or the Registrar may be made available to third parties through publicly accessible Whois or RDAP services, as required by:

   the Registry Policies;

   ICANN Consensus Policies; and/or

   applicable laws, regulations, and governmental requirements.

2.2 This Privacy Policy describes the Registry's practices regarding the appropriate collection, retention, use, correction, disclosure, and transfer of Registrants' personal information.

To provide Registry Services for the TLD, ICANN requires the Registry to collect and publish certain registration data associated with each registered domain name, including data relating to the identity of the Registrant.



3. Definitions

For the purposes of this Policy, the following terms shall have the meanings set out below.

3.1 Data Escrow Agent

Data Escrow Agent means a third-party service provider contracted by the Registry to provide data escrow services.

The data escrow agreement ensures that all relevant DNS data and registration information, including Personal Information, are securely transferred to ICANN and, where required, to an ICANN-designated Emergency Back-End Registry Operator (EBERO). It also ensures the integrity, availability, and security of the Registry's TLD database.

The Data Escrow Agent shall not use or disclose Registry data except where necessary to maintain the stability, security, or continuity of the Registry's operations.

3.2 Personal Information

Personal Information means any information relating to an identified or reasonably identifiable natural person, including a Registrant.

Personal Information does not include aggregated or indexed information that cannot reasonably identify an individual, such as DNS zone files, system logs, databases, or backup data.

Personal Information may include, without limitation: Registrant name; Postal address; Telephone number; Email address; and Residential address or personal email address where such information is provided as the primary contact for a domain name registration.

3.3 Primary Purpose of Collection

The primary purpose of collecting Personal Information is to maintain registration records in the Registry's WHOIS/RDAP database in accordance with ICANN requirements.

A copy of this registration data is also provided to the Registry's Data Escrow Agent as required by ICANN.

Certain registration data is made publicly accessible through WHOIS and/or RDAP services. Without the collection and publication of the required registration data, the Registry would be unable to process or maintain domain name registrations.


4. WHOIS/RDAP Services

The Registry operates publicly accessible WHOIS and/or Registration Data Access Protocol (RDAP) services.

WHOIS is the traditional protocol used by domain name registries and Regional Internet Registries (RIRs) to provide information about registered domain names.

RDAP is the modern successor to WHOIS and provides substantially the same registration information in a structured, standardized, and machine-readable format.

In accordance with applicable ICANN Consensus Policies, the Registry's WHOIS/RDAP services may provide the following information for registered domain names, as amended from time to time:

  1. DNS name server information;

  2. Domain name creation date;

  3. Last updated date;

  4. Expiration date;

  5. Current domain status;

  6. Registrar information;

  7. Registrant name;

  8. Registrant address;

  9. Registrant email address and telephone number;

  10. Registrant state or province;

  11. Registrant country; and

  12. Administrative, technical, and billing contact information provided by the Registrant.


5. Data Collection

5.1 Collection of Personal Information

Where necessary, the Registry may collect Personal Information for one or more of the following purposes:

  1. Identifying and maintaining contact information for Registrants and their designated representatives;

  2. Providing appropriate access to registration data for the public and other parties with a legitimate interest;

  3. Providing registry services and maintaining registration databases;

  4. Operating WHOIS and/or RDAP services;

  5. Communicating with Registrants, including the delivery of notices required under Registry Policies; and

  6. Assisting law enforcement authorities, government agencies, and recognized Internet security organizations in the investigation or prevention of suspected unlawful or malicious activities.

5.2 Website Information

The Registry's website may use technologies such as cookies and similar tracking mechanisms to collect information regarding website usage and improve user experience.

The Registry's website may also contain links to third-party websites. The Registry is not responsible for the content, privacy practices, or security of any third-party websites.


6. Data Storage

Domain name registration data is stored in the Registry's centralized database.

The database is hosted within secure hosting facilities and protected by enterprise-grade firewalls and information security management systems certified to ISO/IEC 27001 standards.

The Registry performs regular backups to ensure business continuity and service availability.

All backup data is encrypted and stored securely. Encrypted communication channels are used when transferring backup data to off-site storage locations to protect against unauthorized access, disclosure, or loss.


7. Use and Disclosure

7.1 The Registry may use or disclose a Registrant's Personal Information for purposes other than the primary purpose of collection where permitted or required, including where:

  1. the Personal Information relates to contact details associated with Registrars, Internet service providers (ISPs), Internet service resellers, or their directors, managers, employees, representatives, or other authorized contacts;

  2. the Registrant has consented to such use or disclosure; or

  3. the Registry reasonably believes that the use or disclosure is necessary for one or more of the following purposes:

  • to lessen or prevent a serious and imminent threat to the life, health, or safety of any individual;

  • to lessen or prevent a serious threat to public health or public safety;

  • where the Registry reasonably suspects that unlawful activity or a violation of any Registry Policy has occurred, is occurring, or may occur, and the use or disclosure is reasonably necessary to investigate the matter or report it to affected parties or competent authorities;

  • where such use or disclosure is required or authorized by applicable laws, regulations, or governmental requirements;

  • where disclosure to, or use by, law enforcement authorities is reasonably necessary for:

  1. the prevention, detection, investigation, prosecution, or punishment of criminal offenses or other violations of law, including the enforcement of penalties or sanctions; or

  2. the preparation for, conduct of, or enforcement of judicial or administrative proceedings or court orders;

  • pursuant to an order issued by an approved dispute resolution provider under ICANN's Uniform Domain Name Dispute Resolution Policy (UDRP) or Uniform Rapid Suspension (URS) procedure; or

  • for any other lawful purpose arising from a dispute resolution process recognized by the Registry.

7.2 Nothing in this Section 7 (Use and Disclosure) requires the Registry to disclose any Personal Information. Unless disclosure is required by applicable law or a binding legal obligation, the Registry reserves the right to decline any request for disclosure.

7.3 Where Personal Information is transferred to individuals or organizations located outside the People's Republic of China, such transfers shall be subject to applicable cross-border data transfer laws, regulations, and policies, including any future amendments thereto.

7.4 The Registry operates servers and supporting infrastructure in multiple geographic locations. Accordingly, Personal Information may be transferred between servers, data centers, and communication networks as necessary for the operation, maintenance, and security of Registry Services.


8. Data Deletion

When a domain name registration is deleted and the associated registration information is no longer required for any other domain name maintained within the Registry database, the related contact information will be deleted, unless the sponsoring Registrar has elected to retain expired registration data in accordance with applicable Registry Policies.

Registrars that retain expired registration data are responsible for deleting obsolete contact information when it is no longer required. The Registry may require periodic reporting regarding retained expired registration data and reserves the right to remove obsolete contact information where a Registrar fails to manage such data appropriately.

9. Data Quality

The Registry may, but is not obligated to, take reasonable steps to ensure that the Personal Information it collects, uses, or discloses is accurate, complete, and current.

Such measures may include verification or confirmation of registration data through the sponsoring Registrar by means of email, telephone, SMS, or other appropriate communication methods.


10. Data Security

The Registry shall implement appropriate technical, administrative, and organizational measures required by ICANN and applicable laws of the People's Republic of China to protect Personal Information against unauthorized access, misuse, loss, alteration, disclosure, or destruction.


11. Publication of this Policy

This Privacy Protection and WHOIS/RDAP Policy describes the Registry's practices regarding the management of Personal Information.

The Registry shall make this Policy publicly available on its official website and provide a copy to any person upon reasonable request.


12. Access and Correction

12.1 Where the Registry holds Personal Information relating to a Registrant, the Registrant may submit a written request to access such information. The Registry may refuse access where it reasonably believes that:

  1. granting access would pose a serious and imminent threat to the life or health of any individual;

  2. granting access would unreasonably affect the privacy of another individual;

  3. the request is frivolous or vexatious;

  4. the requested information relates to existing or anticipated legal proceedings;

  5. granting access would be unlawful;

  6. applicable laws, regulations, governmental requirements, or a court order require or authorize the Registry to deny access;

  7. granting access would prejudice the investigation of suspected unlawful activity; or

  8. granting access would prejudice:

the prevention, detection, investigation, prosecution, or punishment of criminal offenses or other unlawful conduct;

judicial or administrative proceedings or the enforcement of court orders; or

any request from a law enforcement authority or recognized Internet security organization directing the Registry not to disclose the requested information.

12.2 Except where required by ICANN, applicable law, or a valid court order, the Registry is under no obligation to disclose DNS zone files, payment records, email archives, backup data, or other internal operational records.

12.3 Where providing access would reveal confidential commercial information relating to the Registry's internal decision-making processes, the Registry may provide an explanation of the relevant decision rather than granting direct access to such information.

12.4 Where the Registry holds Personal Information relating to a Registrant, the Registrant may request the correction of information that is inaccurate, incomplete, or no longer current.

Upon receiving such a request, the Registry shall take reasonable steps to correct the Personal Information, unless the information forms part of historical records, archived data, or records that are required to be retained by law or applicable Registry Policy.


13. Policy Review

The Registry reserves the right to review, revise, amend, or update this Privacy Protection and WHOIS/RDAP Policy from time to time in accordance with applicable ICANN Consensus Policies, contractual obligations, or applicable laws and regulations.

By providing Personal Information to the Registry, each Registrant acknowledges and agrees to this Policy, including any amendments that may be adopted from time to time.

The most current version of this Policy will be published on the Registry's official website.

This Policy applies to all domain names registered under the .REN Top-Level Domain, regardless of when or through which Registrar the domain name was registered, renewed, or transferred.

Where a Registrant licenses, leases, or otherwise permits the use of a .REN domain name or any of its subdomains, the Registrant shall remain fully responsible for such domain name or subdomain in accordance with applicable Registry Policies, and the Registry and the sponsoring Registrar may require the Registrant to assume all related responsibilities.


1. General

This Domain Name Transfer Policy forms part of the .REN Registry Policies and sets out the rules governing the transfer of domain name registrations within the .REN Top-Level Domain (TLD).


2. Domain Name Transfers

A domain name transfer refers to the transfer of a domain name registration from the current sponsoring Registrar (the Losing Registrar) to another Registrar (the Gaining Registrar).

A Registered Name Holder may transfer its domain name registration between ICANN-accredited Registrars, provided that the transfer process implemented by the Gaining Registrar complies with the minimum requirements of the ICANN Transfer Policy and the transfer is not otherwise prohibited by ICANN policies or applicable Registry Policies.


3. Transfer Authorization

Only the Registered Name Holder and the Administrative Contact identified in the publicly accessible WHOIS/RDAP records (collectively, the Transfer Contacts) are authorized to approve or reject a transfer request submitted by the Gaining Registrar.

In the event of any conflict between the Registered Name Holder and the Administrative Contact, the decision of the Registered Name Holder shall prevail.


4. Registrar Responsibilities

4.1 Provision of Authorization Code

Upon verifying the identity of the Registered Name Holder, the Losing Registrar shall provide the required Authorization Code (AuthInfo Code) without unreasonable delay.

4.2 Grounds for Rejecting a Transfer Request

Where the Losing Registrar rejects a transfer request for any of the reasons set out below, it must provide the Registered Name Holder and the Gaining Registrar with the reason for the rejection.

A transfer request may only be rejected where:

  1. the transfer request is reasonably believed to be fraudulent;

  2. there is a reasonable dispute concerning the identity of the Registered Name Holder or the Administrative Contact;

  3. the domain name has expired and the previous registration period has not been paid for, or the domain name has not expired but the previous or current registration period remains unpaid;

  4. the Transfer Contact has expressly objected to the transfer;

  5. according to the Registry's WHOIS/RDAP records, the transfer request is submitted within 60 days of the initial registration of the domain name; or

  6. the domain name has been transferred between Registrars within the previous 60 days (or any shorter period permitted under applicable ICANN policies), except where the transfer is a return to the original Registrar by mutual agreement of both Registrars or pursuant to an applicable dispute resolution procedure.

For the purposes of this Policy, a "transfer" refers solely to an inter-Registrar transfer carried out in accordance with the ICANN Transfer Policy.

4.3 Mandatory Rejection of Transfer Requests

The Losing Registrar must reject a transfer request where:

  1. it has received notice of a pending Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding;

  2. the transfer is prohibited by an order of a court of competent jurisdiction;

  3. the domain name is subject to a pending dispute under the applicable Transfer Dispute Resolution Policy (TDRP);

  4. the domain name is subject to a mandatory 60-day inter-Registrar transfer lock following a Change of Registrant, as required under this Policy; or

  5. the Registrar has imposed a mandatory 60-day transfer lock following a Change of Registrant and the Registered Name Holder did not opt out of such lock before the Change of Registrant request was completed.

4.4 Circumstances That Shall Not Constitute Grounds for Denial

The Losing Registrar shall not refuse a transfer request solely because:

  1. fees for a pending or future registration period have not been paid;

  2. no response has been received from the Registered Name Holder or Administrative Contact;

  3. the domain name is subject to Registrar Lock, provided that the Registered Name Holder has been given a reasonable and readily available means to remove the lock before requesting the transfer;

  4. the registration term is within a particular period, except for the ICANN-mandated 60-day lock following initial registration, an inter-Registrar transfer, or a Change of Registrant; or

  5. the Registrar has a payment dispute with its reseller, business partner, or affiliate, provided that the Registered Name Holder has paid all applicable registration fees for the domain name.


5. Transfer Renewal

Upon completion of an inter-Registrar transfer, the domain name registration shall be renewed for an additional one-year registration term through the Gaining Registrar, subject to applicable ICANN and Registry Policies.


6. ICANN-Approved Bulk Transfers

6.1 Where all domain name registrations sponsored by a registrar are transferred due to either:

  1. the registrar or its assets being acquired by another registrar; or

  2. the registrar losing its ICANN accreditation or its authorization from the Registry Operator,

the following procedures shall apply:

  1. The gaining registrar must be an ICANN-accredited registrar and must have a valid Registry-Registrar Agreement (RRA) in effect with the Registry Operator for the applicable TLD.

  2. ICANN must provide written assurance to the Registry Operator that the transfer is in the best interests of the Internet community, for example, to preserve the stability of the DNS in the event that the registrar has ceased or is about to cease operations.

6.2 Registry Processing Fee

If the Registry Operator is satisfied that the above conditions have been met:

For a bulk transfer involving 50,000 or fewer domain name registrations, the Registry Operator shall make a one-time modification to the Registry database at no charge.

For a bulk transfer involving more than 50,000 domain name registrations, the Registry Operator shall charge the gaining registrar a one-time fixed fee of USD 50,000 for processing the transfer.


7. Transfer Dispute Resolution Policy

The ICANN Transfer Dispute Resolution Policy (TDRP) governs disputes arising from inter-Registrar domain name transfers.

All affected Registrars, including ICANN-accredited Registrars, shall comply with the procedures and requirements established under the applicable ICANN Transfer Dispute Resolution Policy.

1. General

This Anti-Abuse Policy forms part of the .REN Registry Policies and applies to the .REN Top-Level Domain (TLD) operated by the Registry.

Unless otherwise defined herein, terms used in this Policy shall have the meanings assigned to them in the ICANN Registrar Accreditation Agreement (RAA), the Registry Agreement, or the Registry-Registrar Agreement (RRA).


2. General Provisions

The registration and use of domain names within the .REN TLD must comply with all applicable laws and regulations, Registry Policies, and the requirements established by ICANN under the Registry Agreement, the Registrar Accreditation Agreement, including all applicable ICANN Consensus Policies and Temporary Policies.

The Registry reserves the right to amend, revise, or update this Policy from time to time in order to comply with applicable laws, ICANN requirements, or operational needs.

Any amendment or update to this Policy shall become effective 30 days after publication on the Registry's official website, and shall be binding upon all Registrars and Registrants.


3. Required Provisions in the Registration Agreement

Each Registrar shall require every Registrant to enter into a Domain Name Registration Agreement.

Such agreement must include, at a minimum:

  1. all applicable provisions required by applicable laws and regulations, the ICANN Registrar Accreditation Agreement, and the Registry-Registrar Agreement; and

  2. provisions prohibiting the use of domain names for malware distribution, botnet operations, phishing, copyright infringement, trademark or other intellectual property infringement, fraud, deceptive practices, counterfeiting, or any other activity prohibited by applicable law, and permitting the suspension of domain names engaged in abusive conduct where permitted by applicable law and due process.

3(A). Registration of Two-Character ASCII Domain Names

Before registering a two-character ASCII domain name, the Registrar shall obtain a written representation from the Registrant confirming that, unless the Registrant has an affiliation with, sponsorship from, or endorsement by the government of the corresponding country or territory, or by the manager of the corresponding country-code top-level domain (ccTLD), the Registrant will take reasonable steps to avoid creating any false impression, misleading association, or implied endorsement in connection with the registration or use of the domain name.

3(B). URS Technical Requirements

In addition to all other requirements of the Uniform Rapid Suspension (URS) procedure, where a complainant prevails in a URS proceeding, the Registrar shall:

  • accept payment from the prevailing complainant for the renewal of the suspended domain name; and

  • renew the registration for the duration permitted under the URS requirements.

The Registrar shall not renew a URS-suspended domain name where the prevailing suspension period has exceeded one year, provided that the maximum allowable registration term has been reached in accordance with applicable policies.

3(C). Rights Protection Mechanisms

Each Registrar acknowledges and agrees to comply with all Rights Protection Mechanisms (RPMs) required under Section 7 of the ICANN Registry Agreement, together with any additional Rights Protection Mechanisms implemented by the Registry pursuant to the Registry-Registrar Agreement.


4. Prohibited Use

The Registry expressly prohibits the use of .REN domain names for any unlawful, fraudulent, or abusive purpose, including, without limitation: distributing malware; operating botnets; phishing; copyright infringement; trademark or other intellectual property infringement; fraud or deceptive practices; counterfeiting; or any other activity prohibited under applicable law.

The Registry may conduct periodic technical analysis and monitoring to identify domain names associated with DNS abuse or other security threats, including, without limitation, phishing, malware distribution, botnet activity, domain hijacking, or similar malicious conduct.


5. Enforcement Measures

The Registry reserves the right to deny, suspend, lock, cancel, transfer, or otherwise restrict a domain name registration where necessary, including where:

  1. the domain name or its use violates any Registry Policy (including this Policy) or applicable ICANN requirements;

  2. the domain name threatens the security, stability, or operation of the Registry or the .REN TLD;

  3. such action is necessary to comply with applicable laws, regulations, court orders, governmental directives, or arbitration decisions;

  4. such action is necessary to protect the rights or legitimate interests of the Registry, third parties, or the Registry's affiliates, subsidiaries, owners, officers, directors, representatives, employees, contractors, or shareholders; or

  5. such action is necessary to correct errors made by the Registry or a Registrar in connection with the registration, reservation, or administration of a domain name.

The Registry maintains abuse reporting procedures to enable members of the public to report suspected abuse involving .REN domain names.

Information on how to submit abuse reports is available on the Registry's official website.


1. General

This Sunrise Registration Policy forms part of the .REN Registration Policies and governs the registration of domain names during the Sunrise Period for the .REN Top-Level Domain (TLD).

Unless otherwise defined herein, terms used in this Policy shall have the meanings assigned to them in the ICANN Trademark Clearinghouse Rights Protection Mechanism Requirements (TMCH Requirements).

The TMCH Requirements are available at:

https://www.icann.org/resources/pages/tmch-requirements-2014-01-09-en


2. Sunrise Period

The Registry will conduct a 30-day Sunrise Period, followed by a Quiet Period (if applicable) and General Availability.

The Registry will publish the official opening and closing dates of the Sunrise Period on its official website.

During the Sunrise Period, verified trademark holders (or their authorized agents) may apply to register domain names that exactly match trademarks validated through the Trademark Clearinghouse (TMCH).


3. Eligibility Requirements

Privacy or proxy registrations are not permitted during the Sunrise Period. In addition, every Sunrise application must satisfy all of the following requirements:

  1. The trademark holder or its authorized trademark agent must submit a valid Signed Mark Data (SMD) file issued by the Trademark Clearinghouse (TMCH). The SMD file must successfully pass the validation procedures required by ICANN and correspond exactly to the applied-for domain name.

  2. The requested domain name must comply with all applicable Registry Policies, including the String Policy and the Reserved Names Policy.


4. Allocation of Applications

All Sunrise applications submitted during the Sunrise Period will receive an official Registry timestamp.

Following the close of the Sunrise Period, all valid Sunrise applications will be allocated to the respective applicants.

Where multiple valid Sunrise applications are received for the same domain name, the domain name shall be allocated on a first-come, first-served basis according to the Registry timestamp.


5. Representations and Warranties

By submitting a Sunrise application, the applicant represents and warrants that:

  1. it agrees to comply with this Sunrise Registration Policy, all applicable Registry Policies, and all ICANN requirements, including the Registry Agreement, the Registrar Accreditation Agreement (RAA), ICANN Consensus Policies, and Temporary Policies;

  2. it is either the eligible trademark holder or an authorized representative acting on behalf of the trademark holder;

  3. it agrees to resolve any Sunrise-related disputes in accordance with the Registry's Sunrise Dispute Resolution Policy (SDRP); and

  4. it acknowledges and accepts sole responsibility for any claims, losses, or damages arising from its Sunrise registration that may affect third parties, and agrees to indemnify and hold harmless the Registry and its affiliates, officers, directors, employees, representatives, agents, contractors, and service providers against any claims, liabilities, damages, costs, or expenses arising from such registration, including those resulting from any act, omission, or error by the applicant.


6. Sunrise Dispute Resolution

Any dispute concerning a domain name registered during the Sunrise Period may be submitted to an ICANN-approved dispute resolution provider in accordance with the Registry's Sunrise Dispute Resolution Policy (SDRP).

A Sunrise registration may be challenged on one or more of the following grounds:

  1. At the time of registration, the Registrant did not hold a valid trademark registration recognized within a jurisdiction, or the asserted trademark had not been validated by a competent court or protected under applicable laws or treaties.

  2. The registered domain name is not an exact match to the trademark on which the Sunrise registration was based.

  3. The trademark relied upon for the Sunrise registration was not validly registered within a recognized jurisdiction, or was not otherwise protected by applicable law, treaty, or a final decision of a competent court at the time of registration.


1. General

This General Availability Registration Policy forms part of the .REN Registration Policies and governs the registration of domain names during the General Availability (GA) phase of the .REN Top-Level Domain (TLD).

Unless otherwise defined herein, terms used in this Policy shall have the meanings assigned to them in the ICANN Trademark Clearinghouse Rights Protection Mechanism Requirements (TMCH Requirements).

The TMCH Requirements are available at:

https://www.icann.org/resources/pages/tmch-requirements-2014-01-09-en


2. General Availability

The General Availability (GA) period begins following the completion of the Sunrise Period and any applicable Quiet Period.

During General Availability, any eligible Registrant may register available .REN domain names, subject to all applicable Registry Policies and the requirements established by ICANN under the Registry Agreement and the Registrar Accreditation Agreement (RAA), including the Registry's String Policy.

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


3. Early Access Period (EAP)

The Early Access Period (EAP) refers to the initial stages of General Availability during which domain names are available for registration at premium registration fees.

Registration fees decrease in successive EAP phases until standard General Availability pricing becomes effective.


4. Trademark Claims Service

As part of the Trademark Clearinghouse (TMCH) Rights Protection Mechanisms, the Registry will provide the Trademark Claims Service during the first 90 days of the General Availability period.

The purpose of the Trademark Claims Service is to notify prospective Registrants when a requested domain name matches a trademark record validated in the Trademark Clearinghouse.

If a prospective Registrant applies to register a domain name that matches a trademark record in the TMCH, the Registrant will receive a Trademark Claims Notice before completing the registration.

The domain name registration may proceed only after the Registrant acknowledges and accepts the Trademark Claims Notice.

Once the registration is successfully completed, the corresponding trademark holder will also receive a Trademark Claims Notification from the TMCH.

The following ICANN dispute resolution policies apply to the .REN Top-Level Domain (TLD):


1. Uniform Domain Name Dispute Policy (UDRP)

https://www.icann.org/resources/pages/help/dndr/udrp-en


2. Uniform Rapid Suspension Policy (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

For details, please refer to the .REN Registry official website.


DNSSEC Practice Statement of .ren.pdf——

https://20433407.s21i.faiusr.com/61/ABUIABA9GAAg_Ob1lQYosNm7ugc.pdf


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


Registration Renewal Policy (RRP) (formerly Registration Renewal Operational Policy)

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


Registration Data Directory Services (RDDS) Labeling and Display Policy

https://www.icann.org/resources/pages/rdds-labeling-policy-2017-02-01-en


IGO and INGO Identifier Protection Policy for All gTLDs

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 Procedure (PDDRP)

https://newgtlds.icann.org/en/program-status/pddrp


Ⅰ. General Provisions

Article 1

These Implementation Rules are established to regulate the registration and administration of .REN domain names, protect the legitimate rights and interests of users, ensure the secure and reliable operation of the .REN domain name system, safeguard cybersecurity and user interests, and promote the development and use of domain names, in accordance with the Cybersecurity Law of the People's Republic of China, the Administrative Measures for Internet Domain Names, applicable ICANN Policies, and other relevant laws and regulations.

Article 2

.REN is a generic Top-Level Domain (gTLD) delegated by the Internet Corporation for Assigned Names and Numbers (ICANN).

Any person applying to register a second-level .REN domain name (hereinafter referred to as a "Domain Name"), and any entity providing domain name registration services in connection with .REN, shall comply with these Implementation Rules.

Article 3

ZDNS is the designated registry administration service provider for the .REN Top-Level Domain in the People's Republic of China and is responsible for the operation and administration of the .REN domain name system within China in accordance with applicable laws and regulations.

Article 4

The domain name system governed by these Implementation Rules shall comply with the announcements and requirements issued by the Ministry of Industry and Information Technology (MIIT) concerning China's Internet domain name system.


Ⅱ. Domain Name Registration Service Providers

Article 5

Any Domain Name Registration Service Provider offering .REN domain name registration services within the People's Republic of China shall obtain all licenses and approvals required under applicable laws and regulations.

Article 6

A Domain Name Registration Service Provider offering .REN registration services shall comply with all applicable requirements established by ZDNS.

Article 7

A Domain Name Registration Service Provider shall enter into a valid agreement with ZDNS before providing .REN registration services.

Article 8

A Domain Name Registration Service Provider shall conduct its registration services in a standardized and lawful manner, strengthen network and information security protection, operate with integrity, implement appropriate compliance and anti-corruption measures, and properly supervise any authorized registration agents.

Article 9

A Domain Name Registration Service Provider shall prominently display its licensing information and domain name complaint procedures on its official website and at its business premises.

A Domain Name Registration Agent shall prominently identify the accredited Registration Service Provider it represents on its website and at its business premises.

Article 10

A Domain Name Registration Service Provider shall retain all correspondence and records relating to ZDNS, domain name applicants, and Registrants in connection with domain name registration services.

Unless otherwise required by law or regulation, such records shall be retained for a minimum period of 3 years.

Article 11

A Domain Name Registration Service Provider shall not:

a. provide registration services under the name of any government authority, enterprise, public institution, social organization, or other entity without authorization;

b. register domain names using false or misleading information or otherwise improperly occupy domain name resources;

c. induce or compel others to register domain names through fraud, coercion, or other improper means;

d. require Registrants to extend registration terms or purchase additional services against their will;

e. submit registration information to ZDNS that is inconsistent with the actual registration term requested by the Registrant;

f. refuse, without reasonable justification, to provide an authorization code (AuthInfo Code) requested by the Registrant, prevent the Registrant from transferring the domain name to another registrar, or charge any fee for such transfer request;

g. renew a domain name for a period inconsistent with the Registrant's instructions or perform unauthorized renewals;

h. unlawfully disclose registration information or improperly use such information for commercial gain; or

i. engage in any other conduct that violates applicable laws, regulations, ZDNS policies, or infringes upon the legitimate rights and interests of users.

Where a Registration Service Provider violates any of the above provisions, ZDNS may impose contractual remedies in accordance with the applicable agreement, including termination of the agreement where the violation is serious.

Article 12

ZDNS may terminate its agreement with a Registration Service Provider if:

a. the provider loses the administrative authorization or license required to provide domain name registration services;

b. the provider encounters significant operational difficulties that materially affect its ability to provide registration services; or

c. the provider materially violates the Administrative Measures for Internet Domain Names, these Implementation Rules, applicable ICANN Policies, ZDNS policies, or any applicable agreements.

Article 13

Where a Registration Service Provider's accreditation is terminated by ZDNS, it shall, within ten (10) days, transfer responsibility for its registered domain names to one or more ZDNS-accredited Registration Service Providers.

If the provider fails to do so, ZDNS may arrange such transfer at its discretion.

Article 14

Where a Registration Service Provider authorizes a Domain Name Registration Agent to submit domain name registration applications on its behalf, resulting in the indirect registration of domain names within the .REN Registry database, such activities shall comply with the Administrative Measures for Internet Domain Names, these Implementation Rules, applicable ICANN Policies, ZDNS policies, and all applicable agreements.

The Registration Service Provider shall supervise and manage the activities of its Registration Agents.

Registration Agents shall clearly disclose the agency relationship and provide services in accordance with applicable requirements. Any violation committed by a Registration Agent shall remain the responsibility of the Registration Service Provider under its agreement with ZDNS.


Ⅲ. Domain Name Registration Applications and Review

Article 15

Unless otherwise provided by ZDNS, domain name registrations shall generally be processed on a first-come, first-served basis and shall comply with applicable laws and regulations, ICANN Policies, and these Implementation Rules.

Article 16

The maximum registration term for a domain name shall be 10 years.

Following renewal, the total remaining registration period shall not exceed 10 years, except where an additional one-year renewal results automatically from an approved registrar transfer.

Article 17

In accordance with the Administrative Measures for Internet Domain Names and applicable ICANN Policies, ZDNS shall establish and maintain a Reserved Names List.

Article 18

Natural persons, legal entities, and unincorporated organizations may apply to register .REN domain names unless otherwise provided in these Implementation Rules.

Article 19

To register a domain name, an applicant shall enter into a Registration Agreement with a Registration Service Provider and submit, in written or electronic form:

a. proof of identity of the applicant; and

b. any additional documentation required by ZDNS.

The Registration Service Provider shall verify the authenticity, accuracy, and completeness of the submitted materials and shall submit the verified materials to ZDNS within 1 business day.

Article 20

The applicant shall provide the following registration information:

a. the requested domain name;

b. the hostnames and IP addresses of the primary and secondary name servers;

c. if the applicant is an individual, the applicant's name, identification number, identification document type, mailing address, telephone number, and email address;

d. if the applicant is a legal entity or unincorporated organization, its legal name, organization identification number, document type, mailing address, email address, and telephone number;

e. the names, mailing addresses, email addresses, and telephone numbers of the Registrant Contact, Administrative Contact, Technical Contact, Billing Contact, and authorized representative; and

f. the requested registration term.

The Registration Service Provider shall submit the above registration information to ZDNS within 1 business day after receiving the application.

Article 21

The applicant shall represent and warrant in the Registration Agreement that it shall:

a. comply with the Cybersecurity Law of the People's Republic of China and other applicable laws governing Internet activities

b. comply with the Administrative Measures for Internet Domain Names and all applicable regulatory requirements;

c. comply with applicable ICANN Consensus Policies and other policies governing generic Top-Level Domains;

d. comply with these Implementation Rules, the .REN Domain Name Dispute Resolution Policy, and applicable ZDNS policies; and

e. ensure that all registration information submitted is true, accurate, and complete.

Article 22

The date on which ZDNS receives the first valid registration application shall be deemed the Application Date.

Both ZDNS and the Registration Service Provider shall notify the applicant of the Application Date.

Article 23

Registration Service Providers shall review all registration applications to ensure compliance with the Administrative Measures for Internet Domain Names.

ZDNS may conduct post-registration reviews of registered domain names.

Neither ZDNS nor a Registration Service Provider shall provide registration services for domain names containing content prohibited under Article 28 of the Administrative Measures for Internet Domain Names.

Where registration information is found to be false, inaccurate, or incomplete, the Registration Service Provider shall require the applicant to correct such information. If the applicant fails to do so or continues to provide inaccurate registration information, registration services shall be refused.

ZDNS may require the Registration Service Provider to cancel any such registration in accordance with the Administrative Measures for Internet Domain Names.


IV. Modification and Deletion of Domain Names

Article 24

If any registration information other than the domain name holder's information changes, the domain name holder shall apply to the registrar to update the registration information within 7 days of the change, using the confirmation method selected at the time of registration.

The registrar shall submit the updated registration information to ZDNS within 3 working days after receiving the registrant's request.

A registrar shall not modify any registration information without the consent of the domain name holder.

Article 25

An applicant wishing to transfer ownership of a domain name shall complete the transfer procedures through the registrar.

The registrar shall establish and publicly disclose its domain name ownership transfer procedures, and shall verify the transfer application and the identity documents of both the transferor and the transferee. The registrar shall complete the review within 3 working days after receiving the required documents and, upon successful verification, update the domain name holder in accordance with its procedures.

The transferee shall comply with all applicable domain name registration requirements under these Rules.

Article 26

To delete a domain name, the domain name holder shall submit a valid deletion request together with proof of identity to the registrar.

The registrar shall review the submitted materials within 3 working days. If the application is approved, the registrar shall delete the domain name registration and notify the domain name holder.

Article 27

A registrar shall delete a registered domain name if:

the domain name falls under any circumstance requiring deletion pursuant to the Administrative Measures for Internet Domain Names; or the domain name otherwise violates the requirements of ZDNS.

Where a court, domain name dispute resolution provider, or competent governmental authority orders the cancellation of a domain name, the registrar shall comply with such judgment, decision, award, or order.

Article 28

During any judicial proceeding, arbitration proceeding, or domain name dispute resolution proceeding concerning a domain name, the registrar shall not process any request to transfer or delete the disputed domain name, unless the proposed transferee has agreed in writing to be bound by the final judgment, arbitral award, or dispute resolution decision.


V. Change of Registrar

Article 29

A domain name holder may not request a change of registrar under any of the following circumstances:

a. The domain name has been registered for less than 60 days;

b. Fewer than 60 days have elapsed since the last registrar transfer;

c. The domain name is subject to outstanding registration fees;

d. The identity of the domain name holder is unclear or disputed;

e. The domain name is involved in pending litigation, arbitration, or domain name dispute resolution proceedings;

f. A competent governmental authority has lawfully required suspension of DNS resolution for the domain name; or

g. Any other circumstances specified by ZDNS.

Article 30

Each registrar shall establish and publicly disclose its registrar transfer procedures. ZDNS reserves the right to require a registrar to amend any unreasonable transfer procedures.

Article 31

After verifying both the identity of the domain name holder and the holder's intention to transfer, the current registrar (the Losing Registrar) shall provide the correct transfer authorization code (AuthInfo Code) to the domain name holder within 3 working days, and shall not charge any fee for the transfer request.

If the Losing Registrar fails to provide the transfer code within the required period or provides an incorrect code, the domain name holder may submit supporting evidence to ZDNS. Upon verification, ZDNS may directly process the registrar transfer.

Article 32

Upon receiving a registrar transfer request from the domain name holder, the new registrar (the Gaining Registrar) shall submit the transfer request to ZDNS.

Article 33

After receiving the transfer request from the Gaining Registrar, ZDNS shall notify both the Gaining Registrar and the Losing Registrar in writing or electronically.

If the Losing Registrar expressly approves the transfer, or fails to respond within 5 days after receiving the notice, ZDNS shall complete the registrar transfer.

Article 34

If the Losing Registrar rejects the transfer request, it shall promptly notify both ZDNS and the Gaining Registrar in writing or electronically, stating the reasons for the rejection.

Article 35

If the reason for rejection falls within any of the circumstances listed in Article 29, ZDNS shall terminate the transfer request.

If the stated reason does not fall within Article 29, ZDNS may proceed with the registrar transfer.

Article 36

Upon completion of the registrar transfer, ZDNS shall notify both the Losing Registrar and the Gaining Registrar in writing or electronically.

Article 37

After the registrar transfer is completed, the Gaining Registrar shall pay ZDNS one additional year of domain name service fees. The registration term of the domain name shall be extended by 1 year beyond its current expiration date.

VI. Network and Information Security

Article 38

A registrar shall, at a minimum, satisfy the following network and information security requirements:

a. Designate a person responsible for network and information security, appoint two emergency contacts available on a 24×7 basis, and notify ZDNS of any personnel changes within five (5) working days;

b. Maintain dedicated network and information security personnel appropriate to the scale of its domain name registration services;

c. Establish a network and information security management function with clearly defined responsibilities and implement internal policies, requirements, and contingency plans;

d. Establish and maintain a comprehensive network and information security management system, including accountability mechanisms, performance evaluation, emergency response procedures, employee training, and emergency drills;

e. Implement technical security measures in accordance with applicable governmental standards and requirements, including capabilities for infrastructure management, real-time handling of domain names associated with illegal websites, blacklist management, real-name verification of registrants, and mechanisms to prevent illegal or unlawful activities conducted through domain names, and cooperate with inspections by competent authorities; and

f. Comply with any other network and information security requirements imposed by the competent governmental authorities.

Article 39

For the purposes of domain name registration management, registration services, and related business operations, ZDNS and registrars may, with the user's consent, collect, use, provide, disclose, and otherwise process users' personal information in accordance with the Administrative Measures for Internet Domain Names, other applicable laws and regulations, ICANN policies, these Rules, and ZDNS requirements.

User consent shall not be required where collection, use, disclosure, or processing is otherwise authorized or required by applicable laws, regulations, judicial authorities, or competent governmental authorities.

By applying for or holding a .REN domain name, the user is deemed to have consented to the collection, use, provision, disclosure, and management of the user's information, including personal information, as described above.

Registrars shall clearly inform users of the purposes, methods, and scope of collecting, using, providing, disclosing, and processing personal information, and shall obtain the user's consent where required.

Article 40

ZDNS and registrars shall securely store and protect user information in accordance with applicable laws, ensure the security of stored user data, properly retain user information, and take appropriate measures to prevent unauthorized disclosure, damage, or loss.

Article 41

Registrars are primarily responsible for protecting user information.

The domain name registration agreement entered into with users shall expressly provide that the registrar is responsible for protecting user information and shall specify the security measures to be implemented.

If a registrar discloses user information, it shall compensate the affected user in accordance with the applicable registration agreement.

Article 42

To ensure the security and stability of the .REN Top-Level Domain, ZDNS may conduct inspections, audits, or assessments of registrars' network and information security measures.

Where violations are identified, ZDNS may impose appropriate sanctions in accordance with applicable rules and agreements.

Article 43

ZDNS and registrars shall cooperate with the competent governmental authorities in handling domain names used for unlawful activities.

Pursuant to the Administrative Measures for Internet Domain Names, ICANN policies, and applicable ZDNS rules, ZDNS shall establish and implement measures for handling domain names used for illegal activities.

Registrars shall also take appropriate actions against such domain names in accordance with the Administrative Measures for Internet Domain Names, ICANN policies, and ZDNS requirements.

For the purposes of this Article, domain names used for unlawful activities include, without limitation, domain names used to publish or transmit content prohibited by laws or administrative regulations, to compromise Internet security, or otherwise determined by the competent governmental authorities or ZDNS to have been used for illegal activities or activities that endanger Internet security.


VII. Domain Name Dispute Resolution

Article 44

Registrars shall actively cooperate with courts, arbitration institutions, and domain name dispute resolution providers in resolving domain name disputes.

Upon receiving a request from a domain name dispute resolution provider pursuant to the .REN Domain Name Dispute Resolution Policy and any supplemental rules adopted by that provider, the registrar shall respond within 3 working days. If the registrar is unable to respond within the prescribed period, it shall provide the reasons for the delay.

Article 45

During the pendency of a domain name dispute resolution proceeding, the registrar shall take all necessary measures to ensure that the disputed domain name is not deleted or transferred.

Article 46

Where a domain name dispute resolution provider orders the cancellation of a domain name or its transfer to the complainant, the registrar shall implement the decision 10 days after the decision is officially published on the dispute resolution provider's website.

If, within 10 days following publication of the decision, the respondent submits valid evidence that a court or arbitration institution with competent jurisdiction has accepted the dispute for adjudication, implementation of the dispute resolution decision shall be suspended.


VIII. Domain Name Fees

Article 47

Domain name registrants shall pay the applicable domain name registration and maintenance fees to the registrar in a timely manner.

Registrars shall charge such fees in accordance with the principles of reasonableness, transparency, and proportionality to the services provided.

Article 48

Registrars shall pay the applicable domain name service fees to ZDNS on a timely basis.

Article 49

Prior to the expiration of a domain name registration, the registrar shall notify the domain name holder of the upcoming expiration by email or other effective means, reminding the holder to renew the registration.

A domain name holder may not refuse to renew a domain name on the grounds that no renewal notice was received.

The registrar shall retain records of all renewal notices.

Upon expiration, the domain name shall automatically enter a Renewal Confirmation Period. During the 30 days following expiration, the domain name holder may confirm whether to renew the registration.

If the holder expressly notifies the registrar in writing that the domain name will not be renewed, the registrar shall delete the domain name.

If the holder neither provides written notice declining renewal nor renews the domain name within the thirty-day period, the registrar shall delete the domain name after the expiration of the thirty-day Renewal Confirmation Period.

During the Renewal Confirmation Period, the registrar shall not suspend or modify DNS resolution services solely due to non-payment, unless otherwise agreed between the registrar and the domain name holder.


IX. User Complaint Mechanism

Article 50

ZDNS shall establish a telephone hotline and email address for complaints regarding the quality of domain name registration services and shall prominently publish such contact information on its official website.

ZDNS shall respond to complaints within 5 working days after receipt.

Article 51

Registrars shall establish a complaint handling mechanism and prominently publish complaint procedures on the homepage of their websites.

Registrars shall process complaints promptly. Where a complaint cannot be resolved in a timely manner, the registrar shall explain the reason for the delay and provide an estimated resolution timeframe.

If a complaint is determined to be unfounded, the registrar shall explain the reasons to the complainant.

Registrars shall implement any decision issued by ZDNS within 3 working days after receiving notice of such decision.

Article 52

ZDNS shall supervise the registration service activities of registrars.

Where a registrar violates these Rules, ZDNS may take appropriate enforcement measures in accordance with the applicable agreements entered into between ZDNS and the registrar.


X. Supplementary Provisions

Article 53

ZDNS shall maintain a domain name registration information lookup service through the official .REN website.

Article 54

Registrars shall provide public access to domain name registration information in accordance with the Administrative Measures for Internet Domain Names, applicable ICANN policies, and ZDNS requirements.

Article 55

ZDNS reserves the right to amend these Rules from time to time in response to developments in the Internet and domain name system, changes in applicable laws, regulations, or policies, and other relevant circumstances.

Article 56

These Rules shall be interpreted by ZDNS.

Article 57

These Rules shall enter into force on 28 June 2019.

Website Privacy Policy

This Privacy Policy forms an integral part of the Registration Agreement between the Registrant and the Registrar.

As part of the Registry Policies, this Privacy Policy applies to the .REN Top-Level Domain ("TLD").


In this Privacy Policy, "we," "us," and "our" refer to the .REN Registry Operator and its affiliates.

This Privacy Policy explains how we collect, use, disclose, transfer, and protect your personal information, including why we collect it, how we use it, and how you may access and correct the personal information we hold about you.


1. Collection of Personal Information

When you access or browse our website, we may request that you provide certain personal information, including your name, email address, telephone number, and any other information that you voluntarily provide to us, either directly or indirectly (such as through a third party).

We may also collect your personal information through:

Forms you complete;

Face-to-face meetings;

Business cards you provide;

Telephone conversations; and

Information collected or obtained from third parties.

Please note that we will not require you to provide personal information without your consent and confirmation.

However, if you choose not to provide the requested personal information, you may be unable to access or browse our website or use our services, including, without limitation, registry services.

2. Purposes of Collecting Personal Information

We collect your personal information for the following purposes:

a. To provide registry services;

b. To facilitate your access to and use of our website;

c. To operate and administer the Top-Level Domains under our management;

d. To respond to your inquiries and requests;

e. To verify your identity and information;

f. To improve communications and customer support;

g. To evaluate the effectiveness and usability of our website, assess the performance of advertisements relating to our products or services, and conduct analytics and research;

h. To develop and improve products and services;

i. To provide newsletters, promotional offers, and information regarding products or services offered by us or selected third parties that may be of interest to you (including by email or other communication channels for marketing purposes);

j. To comply with applicable laws, regulations, local rules, policies, and ICANN requirements.


3. Information Obtained Through Registrars

As required by ICANN, when you register a domain name, we will also obtain your personal information from the registrar with whom you entered into your Domain Name Registration Agreement.

We require registrars to obtain your consent, in an appropriate manner, to comply with ICANN requirements and applicable laws and regulations.

If you do not agree to, or are uncertain about, such requirements, you should contact your registrar directly.

For the avoidance of doubt, unless otherwise required by applicable law, we shall not share joint or several liability with your registrar regarding the collection or protection of your personal information.


4. Disclosure of Personal Information

We may disclose your personal information to the following parties where appropriate:

a. ICANN, where required to comply with its policies and contractual requirements;

b. Registrars responsible for the registration or administration of your domain name;

c. Third-party providers that supply products or services to you;

d. Third parties engaged by us to provide registry back-end services, data processing (including information processing and internal analysis), internal administration, or business development services;

e. Third parties authorized by you;

f. Third parties where disclosure is necessary to prevent harm to the lawful interests of others or to protect the public interest;

g. Third parties where disclosure is necessary to protect your legitimate interests;

h. Third parties where disclosure serves a significant public interest without materially harming your legitimate interests; and

i. Government authorities, regulatory agencies, courts, arbitration tribunals, or other competent authorities where disclosure is required by law or pursuant to a lawful request.


5. Direct Marketing

For direct marketing purposes, we may send you information regarding:

a. Registry or registrar products and services; and

b. Telecommunications, Internet, networking, and social media-related products and services.


6. Marketing Providers

The products and services described in Section 5 may be provided either by us or by carefully selected third parties associated with those products or services.


7. Marketing Opt-Out

We may receive compensation from third parties described in Section 4(c) in connection with providing marketing information.

If you do not wish us to use your personal information for direct marketing purposes, or do not wish us to disclose your personal information to third parties for such purposes, you may notify us of your decision to opt out using the contact details provided in the "Contact Us" section.

Please note that if you opt out, you may no longer be able to access or browse this website or use certain services, including, without limitation, our registry services.


8. Cookies

When you visit our website, our servers may automatically place and store cookies on your computer or device.

When you access pages on our website, information stored in cookies may be transmitted back to our servers, including:

Your browser type;

Your operating system;

Your method of Internet access;

Your IP address;

Your geographic location;

Your Internet Service Provider (ISP) domain name; and

Other technical information.

We use two types of cookies:

Session Cookies, which are deleted when you close your browser; and

Persistent Cookies, which remain stored on your device until deleted or until they expire.

Most web browsers allow you to refuse or disable cookies.

However, disabling cookies may negatively affect the functionality and usability of this website.


9. International Data Transfers

We may store and process your personal information anywhere in the world and may transfer such information to countries or regions outside the country in which it was originally collected.

Unless you notify us in writing prior to such transfer that you object, your provision of personal information shall constitute your consent to such international transfers.


10. Consent

By providing your personal information to us, you acknowledge and consent to our collection, use, disclosure, and transfer of your personal information as described in this Privacy Policy.


11. Access to Your Personal Information

You may request access to the personal information we hold about you.

If you have any questions regarding this Privacy Policy or our privacy practices, please contact us using the contact information provided in the "Contact Us" section.


*We reserve the right to charge a reasonable administrative fee for processing requests to access personal information.

These Terms of Use (as amended from time to time), together with this Website Privacy Policy (as amended from time to time), govern your access to and use of this Website. By accessing or using this Website, you expressly agree to be bound by these Terms of Use. If you do not agree to these Terms of Use, you must not access or use this Website.

By using this Website and accepting these Terms of Use, you represent and warrant that:

You are at least 18 years of age;

You otherwise have the legal capacity to enter into binding agreements under applicable law; and

You are not prohibited under the laws of the People's Republic of China ("China", for the purposes of these Terms only, excluding Hong Kong SAR, Macau SAR, and Taiwan) from purchasing or receiving the products or services offered through this Website.


License to Use the Website

Unless otherwise stated, the Registry and/or its licensors own all intellectual property rights in this Website and the materials published on it. All such intellectual property rights are reserved.

Subject to these Terms of Use, you may view, download, and print pages from this Website solely for your personal, non-commercial use.

You must not:

Republish material from this Website (including republication on another website);

Sell, rent, or sublicense material from this Website;

Publicly display any material from this Website;

Reproduce, duplicate, copy, or otherwise exploit material from this Website for commercial purposes;

Edit or otherwise modify any material on this Website; or

Redistribute material from this Website, except for content expressly made available for redistribution.


Acceptable Use

You must not use this Website in any manner that causes, or may cause, damage to the Website or impairment of its availability or accessibility, or in any unlawful, illegal, fraudulent, or harmful manner or for any unlawful, illegal, fraudulent, or harmful purpose.

You must not use this Website to copy, store, host, transmit, send, publish, distribute, or otherwise process any material consisting of (or linked to) spyware, computer viruses, Trojan horses, worms, keystroke loggers, rootkits, or other malicious software.

You must not conduct any systematic or automated data collection activities (including, without limitation, scraping, data mining, data extraction, or data harvesting) on or in relation to this Website without the Registry's prior written consent.

You must not use this Website to transmit unsolicited commercial communications.

You must not use this Website for any marketing-related purposes without the Registry's prior written consent.


Restricted Access

Access to certain areas of this Website may be restricted. The Registry reserves the right, at its sole discretion, to restrict access to any part of this Website or the Website as a whole.

If you are provided with a user ID and password to access restricted areas or services, you are responsible for maintaining the confidentiality and security of your credentials. You are solely responsible for all activities conducted using your user ID and password.

The Registry reserves the right to disable your user ID and password at any time without notice or explanation.


User Content

For the purposes of these Terms, "User Content" means any material you submit to this Website, including but not limited to text, images, audio, video, and audiovisual materials.

You grant the Registry a worldwide, irrevocable, non-exclusive, royalty-free license to use, reproduce, adapt, publish, translate, and distribute your User Content in any existing or future media.

You also grant the Registry the right to sublicense these rights and to bring legal action against infringement of these rights.


Your User Content must not:

Be unlawful or illegal;

Infringe the legal rights of any third party;

Give rise to any legal proceedings against you, the Registry, or any third party.

You must not submit any User Content that is or has been the subject of any threatened or actual legal proceedings.

The Registry reserves the right to edit or remove any material submitted to, stored on, hosted on, or published through this Website.


Compliance Requirements

Your use of this Website and your User Content must comply with all applicable laws, regulations, and policies of China and must not:

Violate the basic principles established by the Constitution of the People's Republic of China;

Endanger national security, disclose state secrets, subvert state power, or undermine national unity;

Damage national honor or interests;

Incite ethnic hatred or discrimination or undermine ethnic unity;

Undermine state religious policies or promote cults or superstition;

Spread rumors, disrupt public order, or undermine social stability;

Disseminate obscene, pornographic, gambling-related, violent, terrorist, or criminally instructive content;

Insult, defame, or infringe upon the lawful rights and interests of others; or

Contain any content prohibited by applicable laws or administrative regulations.


No Warranties

This Website is provided "as is" without any representations or warranties, express or implied.

The Registry makes no representations or warranties regarding this Website or the information and materials provided on it.

Without limiting the foregoing, the Registry does not warrant that:

This Website will be continuously available or available at all times; or

The information provided on this Website is complete, accurate, reliable, or non-misleading.

Nothing on this Website constitutes legal, financial, medical, or other professional advice.


Professional Advice

You must not rely on information contained on this Website as a substitute for professional legal advice.

If you have specific legal questions, you should consult a qualified legal professional.

You should never delay seeking legal advice, disregard legal advice, or commence or discontinue legal proceedings because of information contained on this Website.

Additional Terms for Products and Services

In addition to these Terms of Use, any products or services made available through this Website may be subject to additional terms, conditions, Registry Policies, acknowledgements, and disclaimers (collectively, the "Service Agreement"), as published on the Registry's official website and amended from time to time.

By electronically accepting such additional terms, you acknowledge that you have read, understood, and agreed to be bound by the applicable Service Agreement.


Limitation of Liability

To the fullest extent permitted by applicable law, the Registry shall not be liable to you for any loss arising out of or in connection with this Website, whether in contract, tort, or otherwise, including but not limited to:

Any direct loss;

Any indirect, special, incidental, or consequential loss;

Any business losses;

Loss of revenue, income, profits, or anticipated savings;

Loss of contracts or business relationships;

Loss of reputation or goodwill; or

Loss or corruption of information or data.

These limitations apply even if the Registry has been advised of the possibility of such losses.


Reasonableness

By using this Website, you acknowledge that the exclusions and limitations of liability contained in these Terms of Use are reasonable.

If you do not consider them reasonable, you must not use this Website.


Third Parties

You agree that you will not bring any claim personally against any directors, officers, employees, agents, advisers, successors, licensors, or contractors of the Registry (collectively, the "Registry Parties") in respect of any losses arising from your use of this Website.

The warranties and limitations of liability set out in these Terms shall apply equally to the Registry Parties.


Indemnification

You agree to indemnify and hold harmless the Registry and the Registry Parties from and against any and all losses, damages, liabilities, costs, and expenses (including reasonable legal fees) arising from your breach of these Terms of Use or any claim alleging such a breach.


Breach of These Terms

If you breach these Terms of Use, the Registry may take such action as it considers appropriate, including but not limited to:

Suspending your access to the Website;

Prohibiting your access to the Website;

Blocking computers using your IP address from accessing the Website;

Contacting your Internet service provider to request that access be blocked; or

Commencing legal proceedings against you.


Amendments

The Registry reserves the right to amend these Terms of Use at any time without prior notice.

Any revised Terms of Use shall become effective immediately upon publication on this Website. You are responsible for reviewing these Terms periodically.


Assignment

The Registry may assign, transfer, subcontract, or otherwise deal with its rights and obligations under these Terms without notice or your consent.

You may not assign, transfer, subcontract, or otherwise deal with any of your rights or obligations under these Terms.


Severability

If any provision of these Terms is determined by a court or other competent authority to be unlawful or unenforceable, the remaining provisions shall remain in full force and effect.

If any unlawful or unenforceable provision would become lawful or enforceable if part of it were deleted, that part shall be deemed deleted, and the remainder shall continue in effect.


Entire Agreement

These Terms of Use, together with any other terms, conditions, policies, acknowledgements, and disclaimers published on this Website, constitute the entire agreement between you and the Registry regarding your use of this Website and supersede all prior agreements relating to such use.

Governing Law and Jurisdiction

These Terms of Use shall be governed by and construed in accordance with the laws of the People's Republic of China.

Any dispute arising out of or in connection with these Terms of Use shall be submitted to the courts of competent jurisdiction in China.


Contact Information

You may contact the Registry using the contact details published on the Registry's official website, as updated from time to time.