Legal sources with official primary sources

Printed ·

Skip to main content
Skip to the answer

Source status and reading dates are reported separately. A reading date is not source verification.

Back to the act

EU regulatory register · NIS2

Article 28Database of domain name registration data

CELEX 32022L2555 · Read on 2026-08-18 · Chapter V

Share this page

Short answer

1. For the purpose of contributing to the security, stability and resilience of the DNS, Member States shall require TLD name registries and entities providing domain name registration services to collect and maintain accurate and complete domain name registration data in a dedicated database with due diligence in accordance with Union data protection …

Verbatim from the article. Source: NovaCopilot · https://legal.exploreworldai.com/eu/rattsakter/nis2-2022-2555/artikel-28 · Short answer as data · Official text

NIS2, cybersecurity in short

Essential and important entities must take security measures, report significant incidents within 24 hours, and management is personally accountable.

Source: NovaCopilot

Official text

Read from the EU Publications Office for this CELEX number. The wording stands as published; nothing here is rewritten or summarised.

1. For the purpose of contributing to the security, stability and resilience of the DNS, Member States shall require TLD name registries and entities providing domain name registration services to collect and maintain accurate and complete domain name registration data in a dedicated database with due diligence in accordance with Union data protection law as regards data which are personal data.

2. For the purposes of paragraph 1, Member States shall require the database of domain name registration data to contain the necessary information to identify and contact the holders of the domain names and the points of contact administering the domain names under the TLDs. Such information shall include:

(a)

the domain name;

(b)

the date of registration;

(c)

the registrant’s name, contact email address and telephone number;

(d)

the contact email address and telephone number of the point of contact administering the domain name in the event that they are different from those of the registrant.

3. Member States shall require the TLD name registries and the entities providing domain name registration services to have policies and procedures, including verification procedures, in place to ensure that the databases referred to in paragraph 1 include accurate and complete information. Member States shall require such policies and procedures to be made publicly available.

4. Member States shall require the TLD name registries and the entities providing domain name registration services to make publicly available, without undue delay after the registration of a domain name, the domain name registration data which are not personal data.

5. Member States shall require the TLD name registries and the entities providing domain name registration services to provide access to specific domain name registration data upon lawful and duly substantiated requests by legitimate access seekers, in accordance with Union data protection law. Member States shall require the TLD name registries and the entities providing domain name registration services to reply without undue delay and in any event within 72 hours of receipt of any requests for access. Member States shall require policies and procedures with regard to the disclosure of such data to be made publicly available.

6. Compliance with the obligations laid down in paragraphs 1 to 5 shall not result in a duplication of collecting domain name registration data. To that end, Member States shall require TLD name registries and entities providing domain name registration services to cooperate with each other.

Open the article on EUR-Lex

Follow-up questions

Other articles in this chapter

The text is quoted from the official source and is not legal advice. A national court reads the language version that binds in its jurisdiction.

Verifiable trust signals

  • Source-linked answers and explicit evidence gaps
  • Obligations, controls, risks and consequences
  • Stable objects and verifiable checksums
  • Rule-based objects, optional source-linked reasoning
  • Model card, source status and audit

Model cardAudit