Bot signals — Search & SEO crawler

Lumar (Deepcrawl) IP addresses

The two crawl IPs Lumar asks site owners to allowlist. Lumar defaults to a Googlebot user agent, so the address is the only first-party identifier.

risk.is_crawler Page parser Reviewed

Check an IP

Is this IP really Lumar (Deepcrawl)?

Checks the address against what Lumar (Deepcrawl) publishes, the same evidence behind risk.is_crawler.

01 — Verification

How IPAPI.GR verifies Lumar (Deepcrawl).

Only from what Lumar (Deepcrawl) publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official file for the current list.

02 — In the response

What a match looks like.

A lookup of a Lumar (Deepcrawl) address sets risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.

The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be Lumar (Deepcrawl) but doesn't match is unverified.

GET /api/lookup/{ip}?key=PRO_KEY
{
  // … location and network fields …
  "risk": {
    "is_ai": false,
    "is_crawler": true,
    "is_scanner": false
  }
}

03 — Questions

About Lumar (Deepcrawl).

Where does Lumar (Deepcrawl) publish its IP addresses?

Lumar (Deepcrawl) publishes its addresses at https://www.lumar.io/product-guides/how-to-crawl/blocked-crawls-and-whitelisting-our-ips/. IPAPI.GR reads that publication directly, not a third-party copy.

How often is the Lumar (Deepcrawl) list refreshed?

IPAPI.GR re-fetches it every hour. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.

Which risk flag does Lumar (Deepcrawl) set?

A matching address sets risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.

Verify Lumar (Deepcrawl) on every request.

Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.