Help center / Troubleshooting

IP addresses and allowlisting

Where checks come from, and how to let them through a firewall.

Where checks come from

Pingerer's checks run from probes in these regions:

  • Falkenstein fsn (home region: single-region plans check from here, as do SSL, domain, DNS and email checks)
  • New York iad
  • Singapore sgp
  • Toronto yyz

Each monitor is checked from as many of these regions as your plan includes.

User-Agent

HTTP checks identify themselves with this User-Agent:

Pingerer/1.0 (+https://pingerer.com/bot)

IP addresses

Checks come from these addresses. If we add or move a probe, we'll update this list first.

RegionIPv4IPv6
Falkenstein fsn46.224.96.2152a01:4f8:c016:908a::1
New York iad165.227.209.2052604:a880:800:14:0:3:b978:d000
Singapore sgp167.71.213.962400:6180:0:d2:0:3:442f:b000
Toronto yyz134.122.34.632604:a880:cad:d0:0:1:c251:7001

Allowlisting tips

  • Cloudflare: add a WAF custom rule or IP Access rule that skips challenges for our User-Agent or IPs.
  • WordPress security plugins: add our IPs to the plugin's allowlist.
  • Server firewalls: allow the IPs on ports 80 and 443 (and any port you monitor).
  • Don't allowlist by User-Agent alone on anything sensitive; anyone can send any User-Agent.

Who hosts your site

Each check notes the address your site answered from. Pingerer looks that address up to show, on your site's page, who runs the network it's on (your host) and which country it's in, along with the CDN and platform your pages point to. The lookup uses a copy of the database kept on our own servers, so your addresses aren't sent anywhere.

IP geolocation by DB-IP, used under the Creative Commons Attribution 4.0 licence.

Seeing checks you didn't set up?

Someone may have added your site to their account. Our acceptable use policy requires permission. Report it with your site's address and we'll look into it.

Still stuck? Contact us and a person will reply.