--- title: WatchForBot — our monitoring probe description: WatchForBot is the automated agent WatchFor uses to check websites, APIs and certificates on behalf of their owners. Learn how to identify, verify and allowlist it. canonical: https://watchfor.io/bot --- # WatchForBot WatchForBot is the automated agent WatchFor uses to check that websites, APIs, servers and certificates are healthy — from locations around the world — so their owners get alerted the moment something breaks. If you're seeing it in your logs, it's almost certainly because you (or someone on your team) set up a monitor for your own site. ## How to identify it Every request sends this exact User-Agent: Mozilla/5.0 (compatible; WatchForBot/1.0; +https://watchfor.io/bot) The requests come only from the fixed IP addresses listed below. Each IP has forward-confirmed reverse DNS under *.probe.watchfor.io (IPv4): a reverse lookup resolves to the hostname, and the hostname resolves back to the same IP — so you can verify a request genuinely came from us and isn't someone spoofing the User-Agent. A machine-readable list is at [/ips.json](/ips.json). ## Cryptographic verification (Web Bot Auth) Every HTTP(S) probe request is also signed with the fleet's Ed25519 key using RFC 9421 HTTP message signatures (the Web Bot Auth tag="web-bot-auth" profile). Each request carries: Signature-Agent: "https://watchfor.io" Signature-Input: sig1=("@authority" "signature-agent");created=…;expires=…; keyid="BOtvqWNOvlmOUZNVE2MMbkWVpAz9QVgZIOSsMJTivg0";alg="ed25519";tag="web-bot-auth" Signature: sig1=:…base64 Ed25519 signature…: Our public keys are published at [/.well-known/http-message-signatures-directory](/.well-known/http-message-signatures-directory) — verify the signature and you have cryptographic proof the request came from WatchFor, not from someone spoofing our User-Agent. The keyid is the key's JWK thumbprint (RFC 7638), and the directory response is itself signed with that key. WAFs and bot-management platforms that support Web Bot Auth can allowlist us on this basis alone. Browser checks (Playwright journeys a customer scripts) run in a real Chrome and identify as WatchFor-BrowserCheck/1.0 (+https://watchfor.io/bot) , not WatchForBot: their requests are not signed. They come from the same addresses listed on this page. ## A verified bot on Cloudflare WatchForBot is listed as a verified bot in [Cloudflare Radar's bots directory](https://radar.cloudflare.com/bots/directory?q=watchfor), in the Monitoring & Operations category. Cloudflare checks the signature above on every request, so a zone that lets verified bots through treats our probes as a known monitor, not as anonymous automated traffic — no rule needed on your side. A zone can still choose to block or challenge verified bots, or the monitoring category. If your own site does, add the one-line rule below so your monitors keep seeing the site the way visitors do. ## What it does — and doesn't - ✅ Performs the specific checks a customer configured (an HTTP request, an SSL handshake, a DNS lookup, a page-speed audit…), on a schedule they chose. - ✅ Respects normal request limits — a monitor runs at most as often as its interval, from one location per cycle. - 🚫 Does not crawl your site, follow links, or harvest content. It only touches the exact target of each monitor. ## Allowlisting & blocking If a firewall or CDN is blocking our checks, allowlist the User-Agent or the IPs below so monitoring keeps working. You can safely block WatchForBot if you don't want to be monitored from here — but if the site is one you're monitoring with WatchFor , blocking it will make your own monitor report the site as down. Behind Cloudflare? A WAF custom rule with the action Skip matching http.user_agent contains "WatchForBot" exempts our probes from managed challenges in two minutes — see the [step-by-step guide](/docs/reference/probe-locations). ## Where it checks from ### Europe Copy Europe Location IPv4 IPv6 Hostname 🇫🇷 Paris , France 15.236.177.94 2a05:d012:c19:3401:4dc9:840d:8f8d:85d0 paris-1.fr.probe.watchfor.io 🇩🇪 Frankfurt , Germany 35.157.172.211 2a05:d014:155e:5600:c3a5:473e:e9d7:4fcb frankfurt-1.de.probe.watchfor.io 🇱🇹 Vilnius , Lithuania 85.206.149.28 — vilnius-1.lt.probe.watchfor.io 🇱🇹 Vilnius , Lithuania 80.209.238.252 2a02:7b40:50d1:eefc::1 vilnius-2.lt.probe.watchfor.io 🇪🇸 Madrid , Spain 15.217.52.23 2a05:d011:f31:a700:6ab:26fc:e1b6:a2a madrid-1.es.probe.watchfor.io 🇸🇪 Stockholm , Sweden 13.63.231.185 2a05:d016:db4:1200:e052:7feb:a7dd:1cb8 stockholm-1.se.probe.watchfor.io 🇬🇧 London , United Kingdom 18.132.86.229 2a05:d01c:d1f:1b00:8c65:d5a7:3b55:f96b london-1.gb.probe.watchfor.io ### North America Copy North America Location IPv4 IPv6 Hostname 🇨🇦 Montreal , Canada 16.54.175.65 2600:1f11:26:9200:5230:88f5:ca1c:8dba montreal-1.ca.probe.watchfor.io 🇲🇽 Querétaro , Mexico 78.14.142.185 2600:1f17:428c:c500:8ebb:1f23:21f7:62b4 queretaro-1.mx.probe.watchfor.io 🇺🇸 Ashburn , United States 52.73.13.30 2600:1f18:7b53:2800:f95c:9c84:6f85:e3e7 ashburn-1.us.probe.watchfor.io 🇺🇸 Columbus , United States 18.226.195.23 2600:1f16:9d5:ec00:310f:fa1:98de:3f60 columbus-1.us.probe.watchfor.io 🇺🇸 Portland , United States 34.210.233.0 2600:1f14:3b0c:6400:914:8212:717f:84b8 portland-1.us.probe.watchfor.io ### South America Copy South America Location IPv4 IPv6 Hostname 🇧🇷 São Paulo , Brazil 18.230.13.42 2600:1f1e:a43:c500:76cf:93f:7a49:9f8e sao-paulo-1.br.probe.watchfor.io ### Asia Copy Asia Location IPv4 IPv6 Hostname 🇮🇳 Mumbai , India 3.111.4.15 2406:da1a:1082:bd00:3d80:8d20:9d2f:5b18 mumbai-1.in.probe.watchfor.io 🇮🇩 Jakarta , Indonesia 16.79.55.179 2406:da19:45b:cd00:909b:f6b4:f77e:51de jakarta-1.id.probe.watchfor.io 🇯🇵 Tokyo , Japan 13.114.238.105 2406:da14:13bb:ce00:f883:cbfe:84e7:e1a9 tokyo-1.jp.probe.watchfor.io 🇸🇬 Singapore , Singapore 13.250.143.183 2406:da18:1863:b400:fb92:3b38:6bdd:8386 singapore-1.sg.probe.watchfor.io ### Middle East Copy Middle East Location IPv4 IPv6 Hostname 🇮🇱 Tel Aviv , Israel 16.164.39.228 2a05:d025:f8:fa00:fe40:7f04:148e:1f95 tel-aviv-1.il.probe.watchfor.io ### Africa Copy Africa Location IPv4 IPv6 Hostname 🇿🇦 Cape Town , South Africa 13.244.54.44 2406:da11:f61:f300:c9c:e64a:61d6:e80e cape-town-1.za.probe.watchfor.io ### Oceania Copy Oceania Location IPv4 IPv6 Hostname 🇦🇺 Sydney , Australia 52.62.237.155 2406:da1c:1682:5900:df7:d42c:8b58:f39e sydney-1.au.probe.watchfor.io 🇳🇿 Auckland , New Zealand 3.103.20.111 2406:da12:8bb0:3f00:9f31:99ac:aed7:33fe auckland-1.nz.probe.watchfor.io This list can change as we add regions. Always prefer the live [/ips.json](/ips.json) for automated allowlisting. ## Questions? If WatchForBot is causing trouble, or you just need to reach a human about how we monitor your site, we're happy to help. [Email us](mailto:hello@watchfor.io) --- Canonical page: https://watchfor.io/bot · Site guide: https://watchfor.io/llms.txt