Allow the checksite.pro probes (allowlist)

Some firewalls (WAF), CDNs or security plugins block monitoring tools as if they were bots. When that happens, the site detail page shows a Blocked badge instead of “Down”: your website may be working normally, but our probes cannot reach it, so we cannot assess it. Add the details below to your allowlist, then click Re-check now on the site detail page.

1. Probe User-Agent

Every check request sends exactly this User-Agent (fixed):

checksite.pro-monitor/1.0 (+https://checksite.pro)

The simplest way: allow by User-Agent containing checksite.pro-monitor. Note that a User-Agent can be spoofed, so for sensitive websites also combine it with the IP addresses below.

2. IP addresses by probe region

The probes in each region use their own egress IP addresses. You only need to allow the regions your site uses.

Region	IP address
local	IPs not published, use the User-Agent.
md	IPs not published, use the User-Agent.
vn	IPs not published, use the User-Agent.

3. Instructions per firewall

Cloudflare

Go to Security → WAF → Custom rules and create a new rule.
Condition: User Agent contains checksite.pro-monitor (or IP Source Address is in the IP list above).
Action: Skip → choose to skip the remaining WAF rules, Rate limiting and Bot Fight Mode / Super Bot Fight Mode.
Place this rule at the top of the list. Alternatively, add each IP under Security → WAF → Tools (IP Access Rules) with the Allow action.

Sucuri

Go to Firewall → Access Control → Whitelist IP Address and add each IP above. If you are blocked by bot protection, temporarily enable “Allow bots” or contact Sucuri support to have the User-Agent added to the allowlist.

Imperva (Incapsula)

Go to Security Settings → Access Control (or Bot Protection), add the IPs to the Whitelist and put checksite.pro-monitor in the allowed bots list (“Good bots”).

AWS WAF / CloudFront

Create an IP set containing the IPs above, then add an Allow rule referencing this IP set with the highest priority in the Web ACL (placed before the Bot Control and rate-based rules).

Akamai

In Security Configuration → Network Lists, create an IP list and add it to the Allow list (or a “Bypass” rule for Bot Manager). The “Reference #…” code on the block page helps Akamai support look it up quickly.

WordPress security plugins (Wordfence, iThemes, All In One Security…)

Add the IPs above to the plugin's allowlist (Allowlisted IPs). For Wordfence: Wordfence → All Options → Brute Force Protection / Rate Limiting, add the IPs to “Allowlisted IPs”. If your hosting uses ModSecurity, ask your provider to add an exception for these IPs/User-Agent.

4. Re-check

After updating, open the site detail page and click Re-check now. If the probes can get in, the “Blocked” badge disappears on the next check and you receive an “unblocked” notification. We only mark a site as “Blocked” when we detect firewall signatures or a 429 status; a plain 403 is still treated as an error.