> For the complete documentation index, see [llms.txt](https://docs.thehemera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thehemera.com/hemera-indexer/use-cases/ens.md).

# ENS

The Ethereum Name Service (ENS) is a decentralized naming system built on the Ethereum blockchain, allowing users to register and manage human-readable domain names (like `yourname.eth`) that can be linked to Ethereum addresses, smart contracts, and other decentralized resources. ENS simplifies the process of interacting with blockchain addresses and resources by replacing complex alphanumeric strings with easy-to-remember names, enhancing the user experience in the Ethereum ecosystem.

## Key Features

* Current primary name
* ENS holdings (All the ENS names holds by an Address)
* Resolved ENS names (All the ENS names resolved to the Address)
* First registration time
* First primary name set time


---

# 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://docs.thehemera.com/hemera-indexer/use-cases/ens.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.