> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/nis2/chapter-v-jurisdiction-and-registration-art.-26-28/27.md).

# Art. 27 — Registry of entities

NIS2 Article 27 — Registry of entities. Directive (EU) 2022/2555, Chapter V — Jurisdiction and registration.

1. ENISA shall create and maintain a registry of DNS service providers, TLD name registries, entities providing domain name registration services, [cloud computing service](https://headlesslaw.com/definitions/nis2/cloud-computing-service/) providers, [data centre service](https://headlesslaw.com/definitions/nis2/data-centre-service/) providers, [content delivery network](https://headlesslaw.com/definitions/nis2/content-delivery-network/) providers, managed service providers, managed security service providers, as well as providers of online marketplaces, of online search engines and of social networking services platforms, on the basis of the information received from the single points of contact in accordance with paragraph 4. Upon request, ENISA shall allow the competent authorities access to that registry, while ensuring that the confidentiality of information is protected where applicable.
2. Member States shall require entities referred to in paragraph 1 to submit the following information to the competent authorities by 17 January 2025:
   1. the name of the [entity](https://headlesslaw.com/definitions/nis2/entity/);
   2. the relevant sector, subsector and type of entity referred to in Annex I or II, where applicable;
   3. the address of the entity’s main establishment and its other legal establishments in the Union or, if not established in the Union, of its [representative](https://headlesslaw.com/definitions/nis2/representative/) designated pursuant to [Article 26(3)](/nis2/chapter-v-jurisdiction-and-registration-art.-26-28/26.md);
   4. up-to-date contact details, including email addresses and telephone numbers of the entity and, where applicable, its representative designated pursuant to [Article 26(3)](/nis2/chapter-v-jurisdiction-and-registration-art.-26-28/26.md);
   5. the Member States where the entity provides services; and
   6. the entity’s IP ranges.
3. Member States shall ensure that the entities referred to in paragraph 1 notify the competent authority about any changes to the information they submitted under paragraph 2 without delay and in any event within three months of the date of the change.
4. Upon receipt of the information referred to in paragraphs 2 and 3, except for that referred to in paragraph 2, point (f), the single point of contact of the Member State concerned shall, without undue delay, forward it to ENISA.
5. Where applicable, the information referred to in paragraphs 2 and 3 of this Article shall be submitted through the national mechanism referred to in [Article 3(4)](/nis2/chapter-i-general-provisions-art.-1-6/3.md), fourth subparagraph.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/nis2/chapter-v-jurisdiction-and-registration-art.-26-28/27.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.