> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/rewst-documentation/security/security-policy.md).

# Incoming and outgoing domains and IPs

{% hint style="info" %}
Some of the information on this page is still being finalized as we launch new Rewst. Check back for confirmation.
{% endhint %}

## **Outgoing IP addresses**

Traffic from Rewst to your systems— integrations, HTTP requests, database connections— comes from fixed NAT IPs, 3 per region. These IPs should be included in any necessary allow lists for outbound connections.

### North America

* US
  * 18.224.160.10
  * 3.140.22.105
  * 3.130.202.104

### Europe

* UK
  * TBD
* DE
  * TBD

### Australia

* TBD

## **Inbound IP addresses**

Allowlist by hostname, not IP:

* `app.rewst.ai` - the entry point for every region
* Region-specific hosts, used behind it:
  *  [`us.rewst.ai`](http://us.rewst.ai)
  *  [`eu.rewst.ai`](http://eu.rewst.ai) - Germany only
  *  [`uk.rewst.ai`](http://uk.rewst.ai)
  * [`au.rewst.ai`](http://au.rewst.ai)

We recommend allowlisting [`app.rewst.ai`](http://app.rewst.ai) and the host for your region, or all of them if you're unsure which region you're in. Rewst's inbound traffic runs through Cloudflare, so there are no Rewst-specific inbound IPs. If your firewall can only allowlist by IP, use [Cloudflare's published ranges](https://cloudflare.com/ips).

### **Best practice**

First review logs — including firewall logs, proxy logs, endpoint protection logs, and email filtering logs — to determine whether connections or emails containing Rewst webhook URLs are being blocked, inspected, or altered. Only after confirming should allowlisting or bypass rules be added.


---

# 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.rewst.help/rewst-documentation/security/security-policy.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.