> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/integrations/whitelisting-ip-addresses.md). # Whitelisting IP Addresses If your network restricts access by IP address (for example, corporate firewalls, VPNs, or private APIs), you may need to **whitelist Adalo’s IP ranges** to ensure all services function correctly including app builds, API calls, and external integrations. #### 📡 Adalo IP Address Ranges Our data centers use the following IP ranges. Your organization may need to whitelist them to ensure uninterrupted communication between your systems and Adalo: ``` 66.151.48.0/22 66.45.80.0/22 66.71.204.0/22 ``` These ranges may be used dynamically across Adalo infrastructure, so it is important to include the full block when whitelisting rather than individual IPs. #### 🧠 Why Whitelisting Is Important Whitelisting these ranges helps ensure * API calls are not blocked by your firewall * Adalo’s servers can communicate with your backend or authentication systems * Your app remains stable when network restrictions are applied If you use a managed hosting or corporate IT setup, share this list with your **IT or security administrator** so they can update their configuration. --- # 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://help.adalo.com/integrations/whitelisting-ip-addresses.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.