Troubleshooting

    Bypassing bot protection for Lemwatch checks

    Configure bot-management platforms (Cloudflare, DataDome, PerimeterX, Akamai) so Lemwatch checks succeed without weakening security.

    Updated 2026-07-09
    2 min read
    bot
    protection
    datadome

    Quick answer#

    Add Lemwatch's IP ranges and Lemwatch/1.0 User-Agent to your bot-management platform's allow-list. Every major vendor supports IP + UA rules; you do not need to disable protection globally.

    What this fixes#

  1. Bot challenges returning 200 HTML instead of your real page
  2. "Access denied" 403s only from Lemwatch
  3. Fake "content changed" alerts caused by challenge pages
  4. Login walls appearing on public pages

    5. Where to find it in Lemwatch#

    Copy IPs and UA from Settings → Monitoring → Probe IPs. All rule creation happens in the vendor dashboard.

    How to configure each vendor#

  5. Cloudflare: WAF → Custom Rules → Skip rule matching Lemwatch UA + IPs.
  6. DataDome: Management → Allowlist → add Lemwatch CIDRs and UA.
  7. PerimeterX / HUMAN: Console → Allowlist → IP + User-Agent entries.
  8. Akamai Bot Manager: Add Lemwatch IPs to the "Known Bots" allow category.
  9. Run Check now in Lemwatch to verify the real page loads.

    10. FAQ#

    Won't attackers spoof the Lemwatch User-Agent?#

    Only if they also come from our published IPs — which are locked to our infrastructure.

    Do I still need to whitelist the IPs at the firewall?#

    Yes — bot management and firewalls are separate layers. See IP whitelisting.

    Related#

  10. Whitelist Lemwatch monitoring IPs
  11. Cloudflare blocking Lemwatch
  12. Fixing 5xx errors from firewalls
    13. Was this article helpful?

    Previous

    Why did my SSL grade drop?

    Next

    What is the "Is [site] down?" tool?

    Related Articles

    Whitelist Lemwatch monitoring IPs

    Allow Lemwatch checks through your firewall, WAF, or rate limiter using our published IP ranges and User-Agent.

    Cloudflare is blocking Lemwatch checks

    Fix Cloudflare "Challenge", "Managed Challenge", or 1020 errors that make Lemwatch see your site as down.

    Fixing 5xx errors caused by your firewall

    Diagnose 502, 503, and 520 responses that only appear in Lemwatch — usually WAF rate limits or origin timeouts.

    Why does is-down say a site is up when I cannot reach it?

    When the is-down tool shows a site as up but your browser cannot load it, the problem is almost always local: DNS cache, ISP route, or firewall.

    Back to Help Center