> For the complete documentation index, see [llms.txt](https://docs.alldomains.id/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alldomains.id/protocol/overview/what-is-a-web3-domain-tld.md).

# What is a Web3 domain/TLD

A **Web3 domain** is a human-readable and unique address that is easy to remember & communicate and can be used in place of a Public Key (more commonly known as a Wallet Address).

A **TLD** is the final component of a domain name and it’s the highest level in the hierarchical **AllDomains** registry.

{% hint style="info" %}
**\<human readable domain>.\<top-level-domain>**
{% endhint %}

Unlike Web 2 domains that are hosted on the global network of Domain Name System (DNS) servers, **Web3** domains leverage blockchain technology making them decentralized and more importantly allowing them to interact with blockchain apps and smart contracts.


---

# 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.alldomains.id/protocol/overview/what-is-a-web3-domain-tld.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.