Applicant Information

Does or will this RSP have a publicly verifiable, 3rd party certification (e.g. ISO 27001) held directly by the organization and relevant to the registry services under application?

Yes

Does or will this RSP have processes and controls to manage physical access to infrastructure and systems, including building access controls, security cameras and/or other sensors, physical environmental monitoring and safety equipment, and alarm systems related to the physical infrastructure?

Yes

Does or will this RSP have processes and controls to manage non-physical access to infrastructure, including network access from both internal systems and external Internet systems, intrusion detection systems, security information and event management systems, network firewalls, network segmentation and isolation, user identification and authentication, and authorization schemes?

Yes

Does or will this RSP have processes and controls pertaining to the selection of vendors and equipment suppliers, management and maintenance of assets while in use, procurement of assets, and safe disposal of assets?

Yes

Does or will this RSP routinely renew and keep safe all cryptographic material necessary for the operation of the RSP?

Yes

Does or will this RSP secure (e.g. encryption, tamper detection, etc…) at-rest data relevant to the operation of the RSP, including but not limited to DNSSEC if applicable?

Yes

Does or will this RSP secure (e.g. encryption, tamper detection, etc…) in-transit data relevant to the operation of the RSP, including but not limited to DNSSEC if applicable?

Yes

If applicable, does or will this RSP have security controls for data in virtualized environments, including controls relevant to both on-premises or private virtualization environments as well as public clouds, network isolation, memory isolation, process isolation, and hypervisor access controls?

Yes

Does or will this RSP have a senior executive primarily in charge of and responsible for security?

Yes

Does or will this RSP conduct background checks, both initial and on-going, of personnel and vendors relevant to the registry services under application?

Yes

Describe the solutions and mitigations to be used to thwart Distributed Denial of Service (DDOS) attacks against the authoritative DNS services.

We primarily rely on the traffic cleaning services (7x24 on-call manual intervention) and intelligent protection functions (routinely enabled) provided by upstream network service providers. At the same time, we combine our own network technical means (such as Access Control Lists (ACLs), route blackhole policies, Anycast technology, and elastic emergency bandwidth) to comprehensively achieve DDoS attack protection against DNS. In daily operations, the DNS domain name system infrastructure has achieved real-time monitoring, and all monitoring alert information is integrated into a centralized monitoring system. The monitoring system possesses the capability to identify traffic anomalies, enabling it to capture risk signals such as sudden spikes in abnormal query volumes, unusual access frequencies, and abnormal traffic sources in real time, rather than only triggering alerts when the domain name system service is interrupted. For different attack scenarios, the monitoring system has preset corresponding traffic thresholds. Additionally, a professional 7x24-hour duty team is available to ensure timely response to emergency handling related to distributed denial of service attacks. When the system receives alert information exceeding the preset threshold, the duty personnel will conduct a secondary verification of the traffic anomalies, and then analyze and initiate a matching protection strategy based on the type of attack, traffic scale, and impact scope. For example, external traffic cleaning services are not continuously enabled and require manual intervention from the 7x24-hour duty team to activate. The traffic is redirected through a Border Gateway Protocol (BGP) announcement, directing the target traffic to the cleaning center. After completing the attack protection operation, the 7x24 duty personnel will produce an event handling report. The relevant service operation and maintenance team will comprehensively analyze and process the incident for continuous optimization, and the report will be reviewed and commented by leaders.

Does or will this RSP comply with BCP 38?

Yes

Does or will this RSP implement routing security of some nature, such as automated route filters, RPKI route origin validation, or other operational practices defined by the Internet Society and Global Cyber Alliance's Mutually Agreed Norms for Routing Security (MANRS)?

Yes

Does or will this RSP have documented, regular, and active practices for the maintenance of hardware relevant to the registry services under application?

Yes

Does or will this RSP have documented, regular, and active practices for the maintenance, upgrading, and patching of software relevant to the registry services under application?

Yes

Does or will this RSP have documented, regular, and active practices for the lifecycle of hardware relevant to the registry services under application?

Yes

Does or will this RSP have documented, regular, and active practices for the secure development of software?

Yes

Does or will this RSP have documented contingency plans for extraordinary scenarios regarding the maintenance of hardware relevant to the registry services under application?

Yes

Does or will this RSP have documented contingency plans for extraordinary scenarios regarding the maintenance, upgrading, and patching of software relevant to the registry services under application?

Yes

Does or will this RSP have documented contingency plans for extraordinary scenarios regarding the lifecycle of hardware relevant to the registry services under application?

Yes

Does or will this RSP have documented contingency plans for extraordinary scenarios regarding the development of software?

Yes

Does or will this RSP use Infrastructure-as-Code (IaC) to manage all systems relevant to operation of the registry services under application?

No - Currently, although we have not introduced IaC into the field of operation and maintenance management, we have implemented numerous measures and processes aimed at reducing the potential security and stability risks arising from manual operations in operation and maintenance management. Firstly, through service process management, we strictly regulate every aspect of the service delivery, service launch, service change, and service decommissioning processes, involving multi-level approval processes. These processes are executed after being approved by the technical supervisor. For major operations involving the overall stability of the system, they must be reported to senior management for final confirmation before implementation, and we ensure that every delivery and change of the service deployment package is traceable and reversible. The service deployment package undergoes unit testing, integration testing, security testing, and other stages in the R&D department to ensure that the code deployment does not affect system stability. After being delivered to the operation and maintenance management department, the operation and maintenance management department verifies the functions of the service deployment after launch through gray release, and can perform rollback operations at any time if there are issues. In addition, for operations involving changes to database metadata or business data, the DBA strictly controls the change statements, performs change and deployment verification in the OT&E environment, and then deploys and upgrades in the production environment. Secondly, a log audit system is deployed on the execution operation terminal and server to record all manual operations in their entirety and ensure they cannot be tampered with. And through real-time monitoring, core indicators related to manual operations (such as DNS resolution success rate, system response time, key status, etc.) are monitored in real-time, with multi-level alarm thresholds set. In the event of operational anomalies (such as resolution failure due to configuration errors), the system alarm is immediately triggered to ensure that operation and maintenance personnel respond promptly.

Does or will this RSP use automated orchestration to manage all systems relevant to the operation of the registry services under application?

No - We have adopted Ansible for configuration management to enhance work efficiency, reduce the risks associated with manual operations, and ensure consistency, repeatability, and verifiability in executing large-scale operations and maintenance tasks. Some services utilize Docker containerization technology to simplify service deployment and launch processes, but we have not yet employed Kubernetes for container orchestration and management.

Describe the methods resiliency for DNS, including the use of anycast, primary and secondary DNS authoritative servers, and hidden DNS zone transfer servers.

The elastic design leveraging IP Anycast technology enables the DNS system to dynamically expand or contract nodes based on real-time network status and traffic demands, automatically optimizing routing and allocating traffic to ensure high availability and fault tolerance. The DNS zone data updating employs a multi-layered primary-secondary update mechanism, wherein the leaf nodes at the outer layer exclusively provide resolution query services, while the hidden DNS zone servers are responsible for data transmission. This architecture bolsters the stability and consistency of DNS resolution services. Refer to Annex 5.

Does or will this RSP have at least two Tier III (as defined here: https://uptimeinstitute.com/tiers) or equivalent data centers having no inter-dependencies for DNS zone distribution?

Yes

Does or will this RSP have at least two Tier III or equivalent data centers having no inter-dependencies for global DNS anycast service?

Yes

Does or will this RSP have enough coverage of DNS service to accommodate failures of any DNS point-of-presence to maintain minimum Service Level Requirements?

Yes

Does or will this RSP implement RFC 1034 (“DOMAIN NAMES - CONCEPTS AND FACILITIES”)?

Yes

Does or will this RSP implement RFC 1035 (“DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION”)?

Yes

Does or will this RSP implement RFC 1123 (“Requirements for Internet Hosts -- Application and Support”)?

Yes

Does or will this RSP implement RFC 1982 (“Serial Number Arithmetic”)?

Yes

Does or will this RSP implement RFC 2181 (“Clarifications to the DNS Specification”)?

Yes

Does or will this RSP implement RFC 3226 (“DNSSEC and IPv6 A6 aware server/resolver message size requirements”)?

Yes

Does or will this RSP implement RFC 3596 (“DNS Extensions to Support IP Version 6”)?

Yes

Does or will this RSP implement RFC 3597 (“Handling of Unknown DNS Resource Record (RR) Types”)?

Yes

Does or will this RSP implement RFC 4343 (“Domain Name System (DNS) Case Insensitivity Clarification”)?

Yes

Does or will this RSP implement RFC 6891 (“Extension Mechanisms for DNS (EDNS(0)))”?

Yes

Does or will this RSP implement RFC 7766 (“DNS Transport over TCP - Implementation Requirements”)?

Yes

Does or will this RSP implement RFC 5001 (“DNS Name Server Identifier (NSID) Option”)?

Yes

Does or will this RSP operate DNS service according to RFC 6168 (“Requirements for Management of Name Servers for the DNS”)?

Yes

Does or will this RSP operate DNS service according to RFC 8906 (“A Common Operational Problem in DNS Servers: Failure to Communicate”)?

Yes

Does or will this RSP operate DNS service according to RFC 9199 (“Considerations for Large Authoritative DNS Server Operators”)?

Yes

Does or will this RSP operate DNS service according to RFC 9210 (“DNS Transport over TCP - Operational Requirements”)?

Yes

Does or will this RSP meet the standards established in the Service Level Agreements defined in Specification 10 of the ICANN Registry Agreement (version 2024) with regard to DNS?

Yes

Does or will this RSP compartmentalize (e.g. virtualization) the DNS service in such a manner that each compartment (e.g. containers, virtual machines, physical machines) is dedicated to DNS (excluding system services such as monitoring, remote access and NTP)?

Yes

Does or will this RSP monitor all unique DNS servers of all anycast nodes?

Yes

Does or will this RSP operate authoritative DNS servers according to the IANA Technical Requirements for Authoritative Name Servers (https://www.iana.org/help/nameserver-requirements)?

Yes

Does or will this RSP meet the standards established in Specification 10 of the ICANN Registry Agreement (version 2024) with regard to DNS and IPv4?

Yes

Does or will this RSP meet the standards established in Specification 10 of the ICANN Registry Agreement (version 2024) with regard to DNS and IPv6?

Yes

Does or will this RSP regularly exercise DNS Service continuity actions?

Yes

Does or will this RSP be capable of transferring all applicable operations to another RSP as defined by the Material Subcontracting Arrangement Technical Questions?

Yes

Does or will this RSP participate in coordinated Emergency Back-end Registry Operator (EBERO) transitions, including but not limited to maintaining the DNSSEC chain of trust, of hosted gTLDs when the business relationship of this RSP and the Registry Operator is not in good standing?

Yes

Does or will this RSP monitor for faults inside its own network?

Yes

Does or will this RSP monitor for faults from a point outside any of its own networks?

Yes

Does or will this RSP have documented processes for aggregation and triage of faults?

Yes

Does or will this RSP have documented processes to mitigate faults once detected?

Yes

Does or will this RSP have processes to minimize faults during maintenance of systems, including both automated processes and manual change control processes?

Yes

Does or will this RSP have personnel capable of reacting to and mitigating faults 24 hours per day of every day of every year of service?

Yes

Provide documentation regarding any RSP functions currently being served for any gTLD, the domain names of the gTLDs, and all service disruptions for each gTLD in the past six months, where a service disruption is defined by Specification 10 of the ICANN Registry Agreement (2024).

Provide DNS RSP services for the new generic top-level domains (.xn--xhq521b/.xn--1qqw23a), without any service interruptions in the past six months.