An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 Requirements for TLD Name Registries
Implementing Regulation 2024 2690 / 2026-10-11

NIS2 Requirements for TLD Name Registries

Top-level domain registries are expressly identified in Commission Implementing Regulation (EU) 2024/2690. The regulation details technical cybersecurity measures and TLD registry-specific significant-incident criteria, in addition to the applicable NIS2 Directive obligations.

Service definition and covered entity

A top-level domain registry operates a TLD. This is not the same legal category as a retail registrar, reseller or business registering a domain for itself. Identify the operator responsible for registry functions and the legal entity that delivers them. Map external registry service providers and dependencies without assuming all commercial participants share one regulatory status.

Applying the detailed Annex requirements

Regulation 2024/2690 requires the covered provider to address the technical and methodological measures in its Annex. The control programme should encompass security policies, incident processes, business continuity, access governance, system security and supplier controls. Assign owners and retain evidence of implementation. Management approval under NIS2 Article 20 does not replace operational testing.

Operational security and resilience

Registry operations can be disrupted by privileged-account compromise, unauthorised record changes, failure of provisioning systems or the unavailability of name servers and outsourced systems. Assess integrity and availability risks at each stage of the service. Test recovery and emergency change procedures so teams know how to restore trusted records and registry operation.

Incident significance under the regulation

Article 6 contains significant-incident conditions tailored to TLD registries. Consider those alongside the Article 3 common conditions and the Article 4 repeated-incident provision. Incident responders should preserve evidence of affected domain operations, duration and consequences. Reportability requires a legal criteria assessment, not merely classification as a high-priority internal ticket.

Governance, evidence and regulatory coordination

Record registry scope, classification, relevant jurisdiction, Article 27 information requirements and regulator contacts. Exercises should bring together registry operations, suppliers, legal advisers and incident responders. Update records after changes to service architecture, outsourced registry functions or corporate responsibility.

Points of clarification

Does this regulation apply to every NIS2 entity?

No. Its Article 1 identifies specific provider categories.

Does it replace the NIS2 Directive?

No. The Directive and the implementing regulation serve different, complementary roles.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.