GeoPeeker

The GeoPeeker bot

Saw GeoPeeker in your access logs? Here's what it is and how to control it.

What the GeoPeeker bot does

GeoPeeker is a website tool that captures screenshots of a page from different geographic locations and runs uptime, DNS, SSL, and keyword monitors against it. When you see GeoPeeker in your logs, it's because someone, typically the site's own owner, asked us to peek or monitor that specific URL.

A few things worth knowing:

  • It is not a spider. GeoPeeker only requests the exact URLs a customer entered. It does not crawl your site, follow links, or discover new pages on its own.
  • It is user-initiated and low-volume. Requests happen when a customer runs a Peek or on the schedule they configured, not as continuous background crawling.
  • It renders like a real browser. Peeks load the page in headless Chromium (including CSS, fonts, and images) so the screenshot reflects what a visitor would actually see.

How to identify it

Every HTTP request GeoPeeker makes carries a recognizable User-Agent and an X-Geopeeker-Agent header naming the service behind it. Peeks also send a From header with our contact address.

A Peek request looks like:

User-Agent: GeoPeeker Peek Service/1.0.0 (+https://geopeeker.com/bot; [email protected])
X-Geopeeker-Agent: Peek Service
From: [email protected]

Monitors send their own descriptive agents (for example GeoPeeker HTTP Monitor and GeoPeeker Keyword Monitor), each with an X-Geopeeker-Agent and X-Geopeeker-Version header. The documentation lists them in full.

Because any client can copy a User-Agent or an X-Geopeeker-* header, treat these as identification only, not proof. To reliably recognize genuine GeoPeeker traffic, match on the worker node IP addresses below.

Worker node IP addresses

All GeoPeeker Peeks and monitor checks that reach your site come from the worker nodes below. This list updates as our network changes, so check back here for the current addresses.

  • Australia: 15.134.93.110
  • Brazil: 52.67.211.138
  • California: 18.144.108.46
  • Canada: 16.54.180.58
  • Germany: 63.188.68.211
  • India: 13.204.27.16
  • Ireland: 52.210.20.54
  • Japan: 52.193.158.189
  • Singapore: 56.10.149.205
  • Sweden: 16.192.47.13
  • United Kingdom: 16.61.183.3
  • Virginia: 44.194.250.5

IPs can't be spoofed the way request headers can, so this is the authoritative signal for both allowing and identifying GeoPeeker.

Allowing GeoPeeker

If your site sits behind a firewall, WAF, or bot challenge that's blocking Peeks, allow GeoPeeker through by whitelisting the worker node IP addresses above. You can additionally exempt requests carrying the X-Geopeeker-Agent header from rate limiting or bot challenges, but pair that with the IP allowlist rather than relying on the header alone.

Blocking or limiting GeoPeeker

GeoPeeker only visits a page when a customer asks it to, so the most common fix is simply not scheduling Peeks or monitors against a site you don't want captured.

If you're seeing GeoPeeker traffic you didn't expect and want it stopped, you have a few options:

  • Block at your edge. Deny the worker node IP addresses above, or reject requests whose User-Agent contains GeoPeeker, in your firewall, WAF, or server config.
  • Ask us. Email [email protected] from an address associated with the domain and we'll stop peeking and monitoring it. Including a sample log line with the timestamp and IP helps us act quickly.

Contact us

Questions about GeoPeeker traffic to your site, or a request to exclude a domain? Reach us at [email protected] or through our contact page.