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

# The Name Registry

Solana can be viewed as a key-value database, where everything, including domains, is uniquely identifiable by a public key. The data inside a domain account contains an object called the Name Registry. The Name Registry is made of a header and payload.

<figure><img src="/files/feDI2Vk5Eij5oYv7X6kX" alt=""><figcaption><p>Name Registry</p></figcaption></figure>

### Name Registry Struct

#### Header

The header contains three public keys that define the domain's properties:

* `Parent`: Represents the parent domain in the hierarchy.
* `Owner`: Indicates the entity that has control over the domain.
* `Class`: A special key that enables advanced use-cases, such as third-party verification in a badge system.

#### Data: Flexible Data Storage <a href="#data-flexible-data-storage" id="data-flexible-data-storage"></a>

The data section can hold arbitrary binary data. Its length is set during domain registration, and the domain owner can decide what to store in this part of the Name Registry.

In simple terms, the Name Registry data structure provides a way to organize and store information about a domain on Solana, including its relationships, ownership, and any additional data the owner wishes to include.