Monitoring IP Addresses

If your site sits behind a firewall, IP allowlist, or bot-protection rule, add Enori's check IP addresses so our monitors can reach you.

Browser (synthetic) checks

Browser monitors run real Chromium sessions from a dedicated, static set of IP addresses. These are stable — they do not change between deploys.

Add both addresses to your allowlist — checks are load-balanced across them, so any check can originate from either.

HTTP, Ping, Port, DNS, SSL & Domain checks

These lightweight checks currently run from our Azure infrastructure in West Europe and North Europe. They do not use a fixed allowlist today. If your firewall requires static source IPs for these check types, contact support — dedicated static egress is on our roadmap.

How to allowlist

The exact steps depend on your firewall or WAF, but in general:

1. Find your provider's IP allowlist (Cloudflare → WAF → Tools → IP Access Rules; AWS → Security Groups; Nginx → allow directives; etc.).
2. Add the IP addresses above with an Allow rule.
3. If you use a bot-protection product (Cloudflare Bot Fight Mode, reCAPTCHA, etc.), also allow these IPs there — browser checks run a real browser and can otherwise be challenged.

Will these IPs change?

The browser-check IP addresses above are static floating IPs and are kept stable across server replacements. If we ever add capacity (a third checker), we will publish the new address on this page before it goes live, so your allowlist stays accurate. There is no automatic rotation.

Tip: allowlisting by IP is the most reliable option, but if your firewall supports it you can also allow our requests by User-Agent — browser checks identify themselves in the navigator user-agent string.