HeimPulse Bot

What this is

HeimPulse's automated health-check bot, run on behalf of a customer who explicitly configured uptime monitoring against this specific URL. It is not a crawler and does not index content — it makes one request to one explicitly configured URL per check, on a schedule that customer chose.

User-Agent string

Every request from this bot sends exactly this, verbatim:

HeimPulse-Checker/1.0 (+https://heimpulse.com/bot)

If a customer configured their own User-Agent header for their check, that value is sent instead — this default only applies when they haven't set one.

Traffic shape

• Plain HTTP GET or POST only — no JavaScript execution, no form submission beyond what's configured.
• One request per configured endpoint per check interval, never faster than every 30 seconds.
• No follow-on requests, no asset fetching, no session/cookie persistence across checks.

Where it comes from

Checks currently run from six regions: fra, ewr, sgp, sao, tlv, and syd. More regions to come. We don't publish exact IP ranges yet — once our infrastructure footprint is stable, this page will list them so they can be allowlisted with confidence.

Didn't expect this traffic? Get it stopped

If you don't have a HeimPulse account and want a specific check against your domain disabled, email reports@heimpulse.com with the URL being checked and we'll turn it off.

Why it doesn't respect robots.txt

robots.txt governs crawl and indexing behavior. This bot does neither — every request targets one specific URL a customer explicitly configured, the same category of traffic as other uptime-monitoring bots (UptimeRobot, Pingdom, and similar all take the same position).