> 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/domains-as-nfts.md).

# Domains as NFTs

The `NameRegistry` is an FA2-compliant smart contract ([TZIP-12](https://gitlab.com/tzip/tzip/-/blob/master/proposals/tzip-12/tzip-12.md)). All 2nd-level domains can be used as non-fungible tokens, with a few caveats:

* After a domain expires, the owner's balance of the token is always `0`. That means that a domain will "disappear" as a token once it expires (although the `token_id` continues to be valid).
* We don't implement the optional `all_tokens` view, because the number of tokens is too large to be returned in one call.
* When a domain changes owners, all existing operators are automatically dropped.

See the [TZIP-12](https://gitlab.com/tzip/tzip/-/blob/master/proposals/tzip-12/tzip-12.md) specification for more information about the FA2 standard.


---

# 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/domains-as-nfts.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.