> 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-responsive-ips.md). # Owned Responsive IPs Owned responsive IPs provide a single IP reference point when an active service is detected on an IPv4 or IPv6 range that has been attributed to an organization. An **Owned Responsive IP** is a construct created by Cortex Xpanse to provide a single IP reference point when an active service is detected on an IP range that has been attributed to an organization. Owned responsive IPs provide a link back to their associated IPv4 or IPv6 range. Navigate to **Asset Inventory** → **Owned Responsive IPs** to view the complete list of certificates discovered by Cortex Xpanse. Owned responsive IPs are also included in the **Unified Inventory** table. Click on a row in the **Owned Responsive IPs** table to display details, including asset attribution evidence, related services, and ASN information, in the details pane on the right. Refer to the [Unified Inventory](/cortex-xpanse/inventory/unified-inventory.md) section for descriptions of all the fields displayed in the **Owned Responsive IPs** list view. --- # 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-responsive-ips.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.