Information required for national entity lists
Article 3(3) requires Member States to establish lists of essential and important entities and entities providing domain-name registration services. Article 3(4) specifies information those entities must provide: their name, address, up-to-date contact details including email addresses, IP ranges and telephone numbers, their relevant sector or subsector where applicable, and the Member States where they provide services falling within the Directive. This is a minimum EU requirement, not a universal template for every country's registration form.
A covered entity should confirm how national law implements the obligation, including which authority receives the information. The information must describe the legal provider rather than only its group trading name.
How Article 27 differs
Article 27 establishes an ENISA registry for specified digital infrastructure, ICT service-management and digital-provider entities. The separate information set includes the provider's name, sector, address of main establishment or representative, contact details, and the Member States in which services are provided. It also addresses further technical information relevant to certain provider categories. Submission is channelled through the Member States' competent authorities and single points of contact.
A provider should check whether Article 3, Article 27 or both apply to its activities. The existence of an ENISA registry does not make ENISA the universal filing destination for all NIS2 entities.
Keeping contacts and service territories accurate
Regulatory contacts must be usable during an incident and when an authority seeks clarification. Confirm the listed email addresses and telephone numbers have monitored owners. Keep the service-country list aligned with the actual organisation and delivery model. Do not use a parent company's address as a substitute for the relevant legal entity without a documented basis.
Article 3(4) calls for notification of changes without delay and in any event within two weeks. Separate Article 27 update rules and national deadlines should be examined where relevant.
Information governance and security
The required data can include operationally sensitive technical information, particularly IP ranges and other provider-specific identifiers. Give internal owners clear instructions about preparing, approving and transmitting accurate information through a recognised channel. Keep copies of submissions with restricted access appropriate to their content.
Records should show the submission date, who approved it, the relevant authority, any reference number and the next planned review. Registration data should remain distinct from incident notifications under Article 23.
An evidence checklist for internal review
Create an entity register that includes legal name, legal address, service category, essential or important status, regulatory contacts, applicable Member States and the jurisdiction analysis. Track Article 27 attributes separately if the business supplies one of the named digital or ICT services. Cross-check the data against customer contracts, service inventories and company filings.
Assign a responsible person to review changes following relocation, a merger, service expansion or replacement of an incident-response contact. An accurate record is more valuable than an unmaintained one-time submission.
Questions on the text
Must every NIS2 entity submit an IP address range?
Article 3(4) includes IP ranges in the listed contact details, but the exact national collection process and applicability should be checked.
Do Article 3 and Article 27 ask for the same information?
No. Article 27 establishes additional information duties for defined digital and ICT provider categories.
When should Article 3 information be updated?
Relevant changes must be notified without delay and, under Article 3(4), within two weeks at the latest.