> For the complete documentation index, see [llms.txt](https://docs.thoth.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thoth.id/web-app/domain-page.md).

# The Name Page

The public page of a name, and Manage mode for its owner or manager.

Every name has a page at **/domain/\<name>.htr**. It is **public**: anyone can open it, with or without a wallet, and see where the name points, its links, who controls it and when it expires. Send the link to anyone who should know your name.

![The public page of vulture.htr, whose token is currently withdrawn](https://2559695096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8NQqK3W76Bj7LGhFgkFC%2Fuploads%2Fgit-blob-2715c751ca29f8e39193289e113626d4edf59e4f%2Fname-public.jpg?alt=media)

## The header

* The **avatar**, the **name**, and a **Primary** pill if it's its manager's primary name.
* The **bio**, if there is one.
* A status line: **Active**, **Expiring soon** (the last 30 days) or **Expired**, with the expiry date.

On the right, visitors get:

* **Copy address**: copies the address the name resolves to.
* **Show QR**: the same address as a QR code, so someone can scan it to pay you.
* **Share**: shares the page's link, or copies it.

![The QR code dialog](https://2559695096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8NQqK3W76Bj7LGhFgkFC%2Fuploads%2Fgit-blob-313045bf1a10648962823adcf895f0ce6ed7d720%2Fname-qr.jpg?alt=media)

If your connected wallet is the name's **owner or manager**, you get a **Public page | Manage** switch and a **Renew** button instead. See [Manage mode](#manage-mode) below and [Renew a Name](/web-app/renew.md).

![The same page seen by the name's manager, with the Public page | Manage switch and Renew](https://2559695096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8NQqK3W76Bj7LGhFgkFC%2Fuploads%2Fgit-blob-aa80a84f23601e4d0509d685711c3acaf863897e%2Fname-public-owner.jpg?alt=media)

## The panels

**Resolves to.** The full address the name points to, with **Copy** and **View on explorer**. This is the address wallets and apps get when they look the name up. An expired name resolves to nothing until it's renewed.

**Links.** The name's [records](/web-app/domain-page/records.md). Known keys (X, GitHub, Telegram, Discord, Website, Email) are shown with their icon and open as links; anything else is listed under **Other records**.

**Details.** Everything else the contract knows about the name:

| Row                     | Meaning                                                                                             |
| ----------------------- | --------------------------------------------------------------------------------------------------- |
| **Owner**               | The [owner](/web-app/domain-page/ownership.md). Marked **Last owner** while the token is withdrawn. |
| **Manager**             | The [manager](/web-app/domain-page/addresses.md#manager)                                            |
| **Expires**             | The expiry date and how long is left                                                                |
| **Renewal window ends** | The last day the name can be renewed after expiry, before anyone can register it                    |
| **Token**               | The name's token symbol and ID, linking to the Hathor explorer                                      |
| **Contract**            | The thoth.id contract, linking to the Hathor explorer                                               |

## Raw contract data

At the bottom of **Details**, **Raw contract data** expands to show the record exactly as the contract returns it, plus the name's profile. It's the quickest way to confirm what's actually stored on-chain, and handy when you're reporting a problem.

![The raw contract data](https://2559695096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8NQqK3W76Bj7LGhFgkFC%2Fuploads%2Fgit-blob-011ffa090a2b313faaaf0c08094f0ada3d44aa38%2Fname-raw-data.jpg?alt=media)

| Field               | Meaning                                                                                    |
| ------------------- | ------------------------------------------------------------------------------------------ |
| `token_uid`         | The token minted for this name                                                             |
| `owner_address`     | Current [owner](/web-app/domain-page/ownership.md)                                         |
| `is_deposited`      | `"True"` when the contract holds the token, `"False"` when it's withdrawn                  |
| `manager_address`   | Current [manager](/web-app/domain-page/addresses.md#manager)                               |
| `resolving_address` | The address the name resolves to                                                           |
| `expiration_date`   | Expiry as a Unix timestamp, in seconds                                                     |
| `profile`           | Every [record](/web-app/domain-page/records.md), including `avatar_link` and `description` |

The same record is available to applications through the SDK's [`getNameData`](/sdk-reference/name-methods/getnamedata.md).

## Other states

**Not registered.** The page says *Nobody has registered this name yet*, shows its price, and offers **Register**.

![The page of a name nobody has registered](https://2559695096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8NQqK3W76Bj7LGhFgkFC%2Fuploads%2Fgit-blob-89ab2328cddd05a33a1e7a954af4e7dd51ab6ad4%2Fname-available.jpg?alt=media)

**Expired.** During the renewal window the page shows only the dates, the owner and the renewal price, with a **Renew** button for anyone. Renewing doesn't change the owner.

**Token in a wallet.** When the name's token has been withdrawn, a panel says so and offers **Deposit token**. Whoever deposits it becomes the owner. See [Ownership](/web-app/domain-page/ownership.md#deposited-and-withdrawn).

## Manage mode

The owner and the manager edit a name in **Manage mode**, at **/domain/\<name>.htr/manage**. Open it with the **Manage** switch on the name's page.

It has four sections, listed on the left:

| Section                                            | What's in it                                                  | Who can edit                   |
| -------------------------------------------------- | ------------------------------------------------------------- | ------------------------------ |
| [**Profile**](/web-app/domain-page/profile.md)     | Avatar and bio                                                | Manager                        |
| [**Records**](/web-app/domain-page/records.md)     | Links and other key/value data                                | Manager                        |
| [**Addresses**](/web-app/domain-page/addresses.md) | Where the name resolves to, the primary name, and the manager | Manager, and owner for manager |
| [**Ownership**](/web-app/domain-page/ownership.md) | The owner, the name's token, and transferring ownership       | Owner                          |

If you open Manage mode as the owner but not the manager, Profile and Records are read-only and tell you who the manager is. If you're neither, or not connected, the page explains why and links back to the public page.

## Live updates

Every change is a transaction. While one is confirming, the value it changes shows a **Pending** pill and is locked in Manage mode. Once it confirms, the page reloads the name's data by itself, so the new value appears without refreshing the browser. If the transaction fails, the old value simply stays.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thoth.id/web-app/domain-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.