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.

TRS SRS protects its authoritative DNS services against DDoS attacks through a multi-vendor, multi-layered strategy combined with substantial over-provisioning: First, all DNS servers are deployed on a global anycast network across multiple independent clouds, each backed by a large number of geographically dispersed nodes. Anycast routing ensures that queries automatically flow to the healthiest, nearest node and that volumetric loads are distributed evenly across the entire network, preventing any single site from becoming overwhelmed. Second, we partner with two distinct leading DDoS-mitigation providers. One offers volumetric scrubbing at the network edge to absorb massive flood attacks, while the other specializes in application-layer DNS protections. In the event of an attack, BGP steering directs suspicious traffic through these scrubbers, which filter out malicious packets and forward only legitimate DNS requests back to our anycast clouds. Using multiple vendors avoids a single point of failure and leverages the strongest defenses against both large-scale amplification attacks and sophisticated application-level floods. Third, a joint security operations team composed of CERT and NOC personnel monitors traffic patterns in real time. Automated thresholds trigger rapid responses—such as BGP remote-triggered blackholing or on-demand scaling of scrubbing capacity—without waiting for manual intervention. This means mitigation can begin in seconds after detection. Fourth, protocol-level controls on our authoritative servers enforce per-source and per-query-type rate limits, drop abnormally large or malformed UDP packets, and require TCP fallback for oversized responses. These flow-control measures harden the service against both UDP-based floods and TCP connection exhaustion attacks. Finally, we participate actively in industry forums—DNS-OARC, ICANN security groups, M3AAWG and other security communities—and maintain working relationships with law-enforcement agencies in every region where we operate. Threat intelligence shared through these channels allows us to update our defenses and scrubbing rules proactively, while law-enforcement cooperation helps trace and disrupt attack sources when necessary. By combining a globally distributed anycast fabric, partnerships with multiple mitigation vendors, automated detection and response, protocol-level defenses, and ongoing intelligence sharing, TRS SRS maintains uninterrupted DNS availability even in the face of the largest and most complex DDoS campaigns.

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?

Yes

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

Yes

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

TRS implements multiple complementary layers ensuring DNS resiliency with all components under TRS direct operational control: 1. Anycast Distribution: All authoritative zones served over global anycast fabric spanning 75+ locations across 6 continents (NetActuate 50+ locations, Vultr 25+ locations); identical IP prefixes advertised from each location via BGP ensuring queries route to nearest healthy node; if any node becomes unreachable, BGP automatically steers traffic to next available site. 2. Primary and Secondary Authoritative Servers: Each zone supported by primary servers (accept updates) and secondary servers (replicate zone data); both always online actively answering queries; secondaries pull zone transfers at regular intervals or upon notification of changes to zone data, maintaining full synchronization and immediately handling full query load if any primary experiences issues. 3. Hidden Master Servers: Hidden masters (not publicly announced) store authoritative write-enabled copy of each zone; provide updates to all public-facing authoritative servers through TSIG-authenticated zone transfers; keeping masters hidden safeguards data origin and prevents direct attacks on write infrastructure. 4. Multi-Vendor Redundancy: Infrastructure split across NetActuate and Vultr independent providers announcing identical DNS prefixes creates parallel redundancy layers; complete failure of one provider leaves other operational. 5. Automated Monitoring and Failover: Centralized monitoring continuously checks health and performance of every name server; routing automatically bypasses servers falling below thresholds; regular failover drills validate zone transfers, anycast rerouting, and synchronization. TRS controls all DNS software and operations; infrastructure providers supply anti-DDoS, connectivity and hardware resources only.

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).

TRS SRS has not experienced any service disruption.