> 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-xsoar-8-faqs/cortex-xsoar-8-faqs/cortex-xsoar-8-on-prem-faqs/url-requirements.md).

# URL Requirements

You need to allow the following URLs for Cortex XSOAR to operate properly.

{% hint style="info" %}
If you use SSL inspection and experience difficulty connecting to the required URLs or to integration URLs, exclude the required URLs from SSL offloading on the firewall/proxy.
{% endhint %}

| Function                             | Service                                          | Access                       |
| ------------------------------------ | ------------------------------------------------ | ---------------------------- |
| Web interface                        | HTTPS                                            | Inbound · 443                |
| Engine connectivity                  | HTTPS                                            | Inbound · 443 (configurable) |
| Integrations                         | Integration-specific ports                       | Outbound                     |
| Unit42 Intel Inventory (TIM license) | `https://unit42intel.xsoar.paloaltonetworks.com` | Outbound · 443               |
| Marketplace                          | Required endpoints listed below                  | Outbound · 443               |
| On-prem Gateway                      | `onpremgw.crtx.[region].paloaltonetworks.com`    | Outbound · 443               |
| Package downloads for installation   | `deb.debian.org`, `security.debian.org`          | Outbound · 80                |

#### Marketplace endpoints

* `https://marketplace.xsoar.paloaltonetworks.com/` : Download content packs and access the Marketplace. To view content pack images, this domain must also be reachable from the browser.
* `storage.googleapis.com` : Download content packs and access the Marketplace. This domain stores content pack artifacts. You can further limit the URL prefix to `https://storage.googleapis.com/marketplace-dist/`. To view content pack images, this domain must also be reachable from the browser.
* `api.demisto.com` : Download content packs and access the Marketplace. This file maps the Marketplace URL to the Cortex XSOAR version.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You must add <code>marketplace.xsoar.paloaltonetworks.com</code>, <code>storage.googleapis.com</code>, and <code>api.demisto.com</code> otherwise you cannot access the Marketplace.</p></div>
* `xsoar-contrib.pan.dev` : Contribute content packs.

### Cortex XSOAR DNS records

You need to add the following DNS records to your DNS server to resolve hostnames to the cluster IP address (only static, DHCP is not supported). These DNS records (for a given tenant) should all point to the same cluster IP address to ensure a single entry point.

{% hint style="info" %}
Verify the internal DNS correctly resolves these addresses. DNS resolution failure for these FQDNs can cause communication issues.
{% endhint %}

* **`xsoar.<hostname>.<domain>`**: The Cortex XSOAR DNS name for accessing the UI. For example, **`xsoar.mycompany.com`**.
* **`api-<hostname>.<domain>`**: The Cortex XSOAR DNS name that is mapped for API access. For example, **`api-xsoar.mycompany.com`**. This should be a CNAME entry pointing to the same cluster IP address.
* **`ext-<hostname>.<domain>`**: The Cortex XSOAR DNS name that is mapped to access long-running integrations. For example, **`ext-xsoar.mycompany.com`**. This should be a CNAME entry pointing to the same cluster IP address.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-faqs/cortex-xsoar-8-faqs/cortex-xsoar-8-on-prem-faqs/url-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.