MMX

General

This Registry String Policy is incorporated by reference into the registration agreements between registrars and registrants. It forms part of the “Registry Policies” and applies to each of the top level domains listed below (individually, the "TLD"):

• TLD：.购物(xn--g2xx48c)

Technical and Basic Requirements/h3>

Multiple level labels combined together form a domain name (also known as a “string”). All domain names in the TLD must comply with RFC 1034 Section 3.5.

Registry Operator will not accept a registration request for a domain name unless the applied-for string meets the requirements set out in this policy and any other applicable Registry Policies.

ASCII Strings

An ASCII domain name label (string) or its translated A-Label string:

• a.must not exceed 63 characters (not including the TLD);
• b.must consist of A-Z (case insensitive), the digits (0-9) and hyphen (-) only;
• c.must not start or end with a hyphen (-);
• d.must not contain hyphens in the third and fourth character positions (-), e.g. “ab--cd” is not allowed.

IDN Strings

IDN strings must be “IDNA-valid” as defined in RFC 5890 Section 2.3.2.1.

Registry Operator supports Chinese (ZH) IDNs as defined in RFC 4713. Specifically, only one subset of Chinese characters is allowed as specified in:

• "IDN Character Table for CNNIC",http://www.iana.org/domains/idn-tables/tables/cn_zh-cn_4.0.html
• "IDN Character Table for TWNIC",http://www.iana.org/domains/idn-tables/tables/tw_zh-tw_4.0.1.html

IDN Variant Bundling Rules

Many Chinese characters have several acceptable written forms that are known as “variants”. These variants are regarded as having the same meaning as their primary form.

Registry Operator adopts the following sub-level IDN variant bundling rules:

• a.When an IDN domain name is registered, either simplified or traditional Chinese characters may be registered and activated as the primary domain name while all other variants will be reserved to the registrant and blocked from registration.
• b.The primary domain name and all of its variants constitute a bundle set. Deletion of any of the strings of the bundle set will render all the other variants deleted at the same time.
• c.The reserved variants in the bundle set may be activated upon request by the registrant (via the sponsoring registrar).
• d.Active variant IDNs must be provisioned in the TLD’s DNS zone file as zone cuts using the same NS resource records as the primary (canonical) domain name.

The above sub-level IDN bundling rules are subject to change if and when ICANN implements delegation of variants of IDN TLDs.

1.General

This Registry Anti-Abuse Policy is incorporated by reference into the registration agreements between registrars and registrants. It forms part of the “Registry Policies” and applies to each of the top level domains listed below (individually, the “TLD):

• TLD：.购物(xn--g2xx48c)

Unless otherwise defined herein, capitalized terms used in this document have the meanings given to them in the Registrar Accreditation Agreement (“RAA”), the Registry Agreement or the Registry-Registrar Agreement (“RRA”)

2.Basic Requirements

Registration and use of domain names in the 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.

Registry Operator 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 Registry Operator’s website at http://www.nic.购物.

3.Provisions to be Included 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 all the provisions specified in any applicable law, the RAA and the RRA.

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.

4.Prohibited Use

Registry Operator 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.

Registry Operator 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.Consequences for Contravention of Anti-Abuse Policy

Registry Operator 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;
• e.to correct mistakes made by Registry Operator or a registrar in connection with a registration or reservation of the domain name.