> 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/owned-ipv6-ranges.md).

# Owned IPv6 Ranges

View all the IPv6 addresses that you have provided or Cortex Xpanse has attributed to your organization.

Cortex Xpanse supports the discovery and monitoring of IPv6 assets in your Inventory. The **Owned IPv6 Ranges** page displays a list of the IPv6 addresses that Cortex Xpanse has attributed to your organization or that you have provided. IPv6 address information is also available on list-view pages and asset details panels in your Inventory for Domains, Certificates, Owned Responsive IPs, and Services when an owned IPv6 address is used to attribute the asset to your organization. IPv6 addresses are also displayed in Incidents, Alerts, and Dashboards.

{% hint style="info" %}

### Note

Currently, the **Owned IPv6 Ranges** page displays single IPv6 addresses that you have provided or Xpanse has attributed to your organization. IPv6 address ranges are not displayed.
{% endhint %}

Navigate to **Asset Inventory** → **Owned IPv6 Ranges** to view the complete list of owned IPv6 addresses. Click on a row in the **Owned IPv6 Ranges** list view to display more information about the address in the details panel on the right.

The table below describes the fields displayed in the **Owned IPv6 Ranges** list view.

<table data-header-hidden><thead><tr><th width="263"></th><th></th></tr></thead><tbody><tr><td>Field</td><td>Description</td></tr><tr><td><strong>Active Responsive IPs Count</strong></td><td>Number of active IPv6 addresses in the range.</td></tr><tr><td><strong>Business Unit</strong></td><td>The organization that owns the asset.</td></tr><tr><td><strong>Date Added</strong></td><td>The first time that Cortex Xpanse identified this IPv6 range.</td></tr><tr><td><strong>First IPv6 Address</strong></td><td>Xpanse displays single IPv6 addresses only, so the range will appear as a range of one address.</td></tr><tr><td><strong>Last IPv6 Address</strong></td><td>Xpanse displays single IPv6 addresses only, so the range will appear as a range of one address.</td></tr><tr><td><strong>IPs Count</strong></td><td>Number of IPv6 addresses in the range.</td></tr><tr><td><strong>Notes</strong></td><td>Notes that were manually added to the asset in Expander.</td></tr><tr><td><strong>Organization Handles</strong></td><td>Organizational identifier that comes from registration records.</td></tr><tr><td><strong>Tags</strong></td><td><p>The following types of tags can be applied to Owned IPv6 Ranges:</p><ul><li>AR—Attribution reason tags. Indicates whether the IP range was attributed to you because it <strong>Has your Content</strong> or is <strong>Registered to You</strong>.</li></ul></td></tr></tbody></table>


---

# 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/owned-ipv6-ranges.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.