Docs
HTTP monitors

Firewalls and IP addresses

Table of contents
  1. Introduction
  2. When to whitelist IP addresses
  3. Finding WebGazer's IP addresses
    1. Staying updated

Introduction

Ensuring the security and accessibility of your online assets is crucial. WebGazer helps maintain your website's uptime and performance through continuous monitoring. To ensure effective monitoring, you need to whitelist WebGazer's IP addresses within your firewall or IP filtering mechanisms.

This guide will help you whitelist WebGazer's IP addresses, allowing uninterrupted monitoring and real-time alerts. Learn when and why to whitelist these IPs and how to obtain them from WebGazer.

When to whitelist IP addresses

Whitelisting WebGazer's IP addresses is necessary in various scenarios:

  1. Firewalls: If your network firewall restricts traffic based on IP addresses, you must explicitly allow WebGazer's IPs for monitoring.

  2. IP filtering mechanisms: Servers and applications with IP filtering need WebGazer's IPs whitelisted to permit monitoring.

  3. Cloud-based security services: Configure cloud security services (e.g., AWS Security Groups, Azure Network Security Groups) to accept traffic from WebGazer's IPs.

  4. Compliance requirements: Industries with stringent compliance requirements need controlled access to systems, making whitelisting essential for approved entities like WebGazer.

Finding WebGazer's IP addresses

To whitelist WebGazer's IPs, use the provided API endpoint:

https://api.webgazer.io/ip-addresses

This endpoint returns a JSON array with the IP addresses to whitelist.

Staying updated

WebGazer's IP addresses may change as infrastructure scales and updates. Regularly check the API endpoint to keep your whitelist current and avoid interruptions. Consider setting up a schedule or automating the update process.