The checker

Where our checks come from

Every check is one small request from one of the addresses below, with the User-Agent below. A bot wall such as Cloudflare's may answer it with a challenge instead of your page: then the site shows as blocked, nothing is paged, and the alert list gets one email with this page. Allow the checker and it clears on the next check.

Addresses

The list is not published on this server yet; ask support for the addresses of the check regions.

User-Agent

Mozilla/5.0 (compatible; Heedery/1.0; +https://heedery.com/checker)

A rule that matches a User-Agent containing Heedery catches every check and the look-up made when a site is added.

Cloudflare

  1. Allow the addresses. Security → WAF → Tools → IP Access Rules: add each address with the action Allow for this website. This is the one that also gets past Bot Fight Mode on the Free plan.
  2. Or skip the bot check by User-Agent. Security → WAF → Custom rules: when User Agent contains Heedery, action Skip with Super Bot Fight Mode and the managed challenges ticked. Custom rules cannot skip the Free plan's Bot Fight Mode; use the address rule there.
  3. Or check something the wall does not see. A TCP check of port 443 or a DNS check says whether the edge answers, without a page. Switch the monitor's type under its Settings.

Other firewalls

Allow the addresses above, or the User-Agent, in the firewall or the rate limiter in front of the site. Checks are one request per interval, from every minute to every hour, and read at most 1 MB of the page.