> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-uk/v200c/how-tos/how-to-whitelist-ips-and-ports.md).

# How to Whitelist IPs and Ports

The ports and IPs that must be whitelisted on your network for a V200C terminal to reach Verifone's servers.

{% hint style="info" %}
**Use this when** a V200C terminal is behind a network firewall and you need to know which IPs and ports to whitelist so it can reach Verifone's servers.
{% endhint %}

The following ports and IPs must be whitelisted for inbound and outbound access on your network.

| Server                      | Host IP        | Ports                     |
| --------------------------- | -------------- | ------------------------- |
| Transaction / Update Server | `91.207.36.31` | `29006`, `29005`, `29002` |
| Download Server             | `91.207.36.37` | `29006`, `29005`, `29002` |

Also make sure the VHQ Messaging URL is whitelisted for inbound and outbound traffic to and from the terminal:

* **LIVE VHQ Messaging URL:** <https://vhq2.vfims.com/MessagingServer/MessageHandler.asmx>

<details>

<summary>Keywords</summary>

Also called: whitelist IPs, firewall ports, allowlist, open ports, network whitelist, VHQ URL. Search terms: whitelist, firewall, ports, IP, 29006, 29005, 29002, VHQ, messaging URL.

</details>


---

# 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://docs.verifone.com/support-uk/v200c/how-tos/how-to-whitelist-ips-and-ports.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.
