> 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-ipv4-ranges.md).
# Owned IPv4 Ranges
View all the IPv4 addresses, in the form of ranges, that Cortex Xpanse has attributed to your organization.
The **Owned IPv4 Ranges** page displays a list view of all IPv4 addresses, in the form of ranges, that Cortex Xpanse has attributed to your organization. Owned IPv4 range information is also available on the asset details panel when an owned IP address is used to attribute an asset to your organization.
Cortex Xpanse collects IP registration information from various publicly available sources including ARIN, RIPE, APNIC, LACNIC, and AFRINIC. Registry information in your Cortex Xpanse is updated approximately biweekly.
The Registration Record for an IP range includes the following information:
* **Network**—Name, Handle, Start Address, End Address, and Last Refreshed
* **Organization Name**—Name, Handle, Email, Phone, Address, Last Changed
Navigate to **Inventory** → **Owned IPv4 Ranges** to view the complete list of owned IPv4 ranges discovered by Cortex Xpanse. Click on a row in the **Owned IPv4 Ranges** table to display the IP range details, including asset attribution evidence, registration records, and ASN information, in the details panel on the right.
The table below describes the fields displayed on the **Owned IPv4 Ranges** page.
| Field | Description |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active Owned Responsive IPs Count** | Number of active IP addresses in the range. |
| **ASN Countries** | ASN countries associated with an owned responsive IP or IP range. |
| **ASN Handles** | ASN handles associated with an owned responsive IP or IP range. |
| **ASN Record Names** | ASN record names associated with an owned responsive IP or IP range. |
| **ASN Registries** | ASN registries associated with an owned responsive IP or IP range. |
| **Business Unit** | The organization that owns the asset. |
| **Date Added** | The first time that Cortex Xpanse identified this IP Range. |
| **First IP Address** | First IP address value of the defined range. |
| **Last IP Address** | Last IP address value of the defined range. |
| **IPs Count** | Number of IP addresses in the range. |
| **Notes** | Notes that were manually added to the asset in Expander. |
| **Tags** | The following types of tags can be applied to Owned IP Ranges:
- AR—Attribution reason tags. Indicates whether the IP range was attributed to you because it Has your Content or is Registered to You.
- IPR—IP range tag. Custom tag that can be applied to Owned IPv4 or IPv6 ranges.
- TR—Rules-based tag.
|
You can use asset tag rules to define custom IPv4 ranges. Asset tag rules apply tags automatically to assets that match your rule criteria, including any new assets that are attributed to your organization. Define asset tag rules on the **Policies and Rules** → **Asset Tag Rules** page. See [Asset Tagging](/cortex-xpanse/inventory/asset-tagging.md) for more information.
---
# 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-ipv4-ranges.md?ask=&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.