> For the complete documentation index, see [llms.txt](https://developers.tezos.domains/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.tezos.domains/interoperability/.tez-tld.md).

# .tez TLD

Currently, the only supported top-level domain is `.tez`. On testnets, it's always named after the name of the protocol (e.g. `.delphi`, `.edo`, etc.) to avoid potential confusion between a testnet and the mainnet. You can find the corresponding TLDRegistrar addresses in the Deployed Contracts section.

### Label Validation for .tez

In addition to the rules specified in [Name Validation and Normalization](/interoperability/name-resolution.md#name-validation-and-normalization), the top-level domain requires all labels to only contain the Latin characters `a-z`, `0-9`, and hyphens (`-`). Hyphens cannot appear as the first or the last character.


---

# 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://developers.tezos.domains/interoperability/.tez-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.