> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xpanse/inventory/asset-types/domains.md).

# Domains

Cortex Xpanse gets its domains and DNS data from a combination of active and passive global collection techniques.

The **Domains** tab displays a list view of all domains that Cortex Xpanse has attributed to your organization and whether each domain has a recent resolution. If you have configured cloud accounts (such as AWS or Google Cloud Platform), this tab will show you which domains have associated managed cloud resources.

Cortex Xpanse displays root domains and subdomains as separate entries in the Inventory. However, if an organization owns a wildcard DNS entry, we group all subdomains of that wildcard that resolve to the same IP under that one wildcard domain asset entry. We also collapse subdomains under the parent domain if we observe more than 1,000 subdomains.

Cortex Xpanse gets its domains and DNS data from a combination of active and passive global collection techniques. For DNS scanning, Cortex Xpanse sends a BIND version query as the payload. This approach still identifies DNS servers that are not BIND compliant as their response informs Cortex Xpanse of a DNS server’s existence.

Navigate to **Asset Inventory** → **Domains** to see the domains list view. Domains are also included in the **All Assets** list view.

Select a row in the **Domains** or **All Assets** list view pages to open the details pane for that domain.

The table below lists the fields in the **Domains** list view that are unique to **Domains**. The other fields are described in the [Unified Inventory](/cortex-xpanse/inventory/unified-inventory.md) section.

| Field                | Description                                        |
| -------------------- | -------------------------------------------------- |
| **Date Added**       | Date the asset was first added to the inventory.   |
| **Domain Registrar** | Name of the domain registrar for the domain.       |
| **Resolves**         | Indicates whether the domain has a DNS resolution. |

If you don't see all your domains in your Inventory, reach out to Customer Success. It could be a subdomain that was collapsed under a domain or the domain could be considered out of scope.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xpanse/inventory/asset-types/domains.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.