> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/workflow-check-resolution/ip-whitelisting.md).
# IP Whitelisting
### **Overview**
Some organisations prefer not to expose their systems to the public internet. Sprinto supports IP whitelisting, allowing you to restrict inbound requests to a defined set of fixed IP addresses. By whitelisting Sprinto’s IP addresses in your firewall or access control settings, you can ensure that only requests from Sprinto’s infrastructure are allowed.
### **Fixed IP Addresses**
The table below lists Sprinto’s fixed IP addresses for each domain. You can use the AWS Console links to view these IP addresses directly in the relevant region.
### **When to Use IP Whitelisting**
You should use IP whitelisting if:
* Your organisation’s security policy restricts inbound traffic to known sources.
* You need to integrate with Sprinto but do not want to open your systems to the entire public internet.
* You want to add an extra security layer for API access.
### **How to Whitelist Sprinto IPs**
1. Identify the IP addresses relevant to your Sprinto deployment from the table above.
2. Access your firewall, security group, or network access control settings.
3. Add the IP addresses to your allowlist.
4. Save and apply your changes.
5. Test the integration to ensure requests from Sprinto are accepted.
---
# 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.sprinto.com/monitors/workflow-check-resolution/ip-whitelisting.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.