# The "Allowlist" Guide

All <code class="expression">space.vars.company\_name</code> traffic uses **HTTPS or WSS on TCP port 443**. No other ports are required. These apply identically to Windows and macOS.

**Wildcard rules (strongly recommended):**

| Domain pattern  | Notes                                                                        |
| --------------- | ---------------------------------------------------------------------------- |
| `*.we360.ai`    | Covers all <code class="expression">space.vars.company\_name</code> services |
| `*.in.we360.ai` | India-region endpoints                                                       |

**Individual URL fallback list** (use if your firewall does not support wildcards):

| URL                              | Purpose                                                                             |
| -------------------------------- | ----------------------------------------------------------------------------------- |
| `https://portal.we360.ai`        | Admin portal; delivers installers and agent updates                                 |
| `https://assets.we360.ai`        | Configuration bundles                                                               |
| `https://assets.v2.we360.ai`     | Configuration bundles (v2)                                                          |
| `https://origin.in.we360.ai`     | License validation                                                                  |
| `https://origin.global.we360.ai` | License validation                                                                  |
| `https://api.in.we360.ai`        | Primary API endpoint: REST (HTTPS) and real-time livestream (WSS), both on port 443 |
| `https://auth.in.we360.ai`       | Issues and refreshes authentication tokens for agent-to-backend communication       |
| `https://<base_domain>.we360.ai` | Customer admin console (e.g., `acme.we360.ai`)                                      |

#### 2.7 Cloudflare IP allowlist

<code class="expression">space.vars.company\_name</code> sits behind Cloudflare. Domain-based rules are preferred; the IPs below are provided as a supplementary reference for environments where only IP-based rules are possible.

| IP              | Notes      |
| --------------- | ---------- |
| `104.26.15.125` | Cloudflare |
| `104.26.14.125` | Cloudflare |
| `172.67.72.141` | Cloudflare |

These addresses may change through Cloudflare anycast re-routing. To future-proof your rules, allow all Cloudflare proxy ranges. The authoritative and machine-readable lists are maintained at:

* **Human-readable:** <https://www.cloudflare.com/ips/>
* **IPv4 list:** <https://www.cloudflare.com/ips-v4>
* **IPv6 list:** <https://www.cloudflare.com/ips-v6>


---

# Agent Instructions: 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:

```
GET https://docs.we360.ai/deployment-and-it-ops/network-and-security-hardening/allowlist-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.