Bot signals — Search & SEO crawler

InfluenceKit fetcher IP addresses

Customer-triggered link-preview fetcher origins. Exact published IPv4 hosts only.

risk.is_crawler Ranges Reviewed

Check an IP

Is this IP really InfluenceKit fetcher?

Checks the address against what InfluenceKit fetcher publishes, the same evidence behind risk.is_crawler.

01 — Verification

How IPAPI.GR verifies InfluenceKit fetcher.

Only from what InfluenceKit fetcher publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official files for the current list.

02 — In the response

What a match looks like.

A lookup of a InfluenceKit fetcher 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 InfluenceKit fetcher 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 InfluenceKit fetcher.

Where does InfluenceKit fetcher publish its IP addresses?

InfluenceKit fetcher publishes its addresses in 2 places at https://www.influencekit.com/bot-ips-v4 and https://www.influencekit.com/bot-ips-v6. IPAPI.GR reads those publications directly, not a third-party copy.

How often is the InfluenceKit fetcher 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 InfluenceKit fetcher set?

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

Verify InfluenceKit fetcher on every request.

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