> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/security/ip-blocklist.md). # IP Blocklist IP Blocklist allows you to block incoming traffic based on IP addresses or geographic regions. **IP Blocklist** allows you to block incoming traffic based on **IP addresses** or **geographic regions**. This helps prevent unwanted access and reduces automated attacks such as credential stuffing and bot traffic. When enabled, requests from blocked IPs or regions are denied before authentication is processed. ### What Is IP Blocklist? IP Blocklist is an access control mechanism that evaluates the client’s IP address at request time and blocks requests that match configured rules. You can block traffic by: * Specific IP addresses * IP ranges using CIDR notation * Geographic regions based on GeoIP ### Blocking IP Addresses You can block individual IP addresses or ranges. * Supports **IPv4**, **IPv6**, and **CIDR notation** * Enter one IP address or range per line * Useful for blocking known malicious sources or internal policy restrictions Example: ``` 192.0.2.10/32 203.0.113.0/24 2001:db8:85a3:0:0:8a2e:370:7334/128 ``` ### Blocking by Geographic Region You can block traffic based on the user’s geographic location. GeoIP blocking is based on IP geolocation and may not be perfectly accurate. ### Checking an IP Address The **Check IP address** tool lets you verify whether a specific IP address would be blocked by the current configuration. This is useful for testing new rules before deployment. ### Common Use Cases * Blocking known malicious IP ranges * Reducing bot traffic from high-risk regions * Enforcing geographic access restrictions * Responding quickly to active attacks --- # 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.authgear.com/security/ip-blocklist.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.