Case study · Threat intelligence

How whatoblock.com uses IPAPI.GR.

whatoblock.com is a threat-intelligence platform that publishes firewall blocklists. Every record it publishes carries geographic and network context, and that context comes from IPAPI.GR lookups. This page explains where the lookup sits in that pipeline and which fields matter.

What it is
Threat-intelligence platform
Data from IPAPI.GR
Country and location fields, ASN, ISP and organisation

01 · The site

What whatoblock.com does.

whatoblock.com describes itself as "Threat intelligence without enterprise pricing". Its headline is "Live threat intelligence your firewall can use."

It runs its own sensor network, called HoneyBot, which records unsolicited connections. From that data it publishes firewall blocklists of botnet C2 servers, scanners, malicious proxies and DDoS infrastructure. The lists are available as text, CSV, JSON and firewall formats through feed URLs.

A dashboard lets people explore the records. Every record includes geographic and network context, so users can filter by country.

The site is written for SOC analysts, sysadmins and firewall admins, ISPs and hosts, CERTs, MSPs and researchers. It also states that a listing "does not identify a person or establish intent."

02 · The pipeline

Where the lookup fits.

The geographic and network context on each record comes from IPAPI.GR. In general terms, enrichment sits between the sensor and everything people see.

  1. A sensor records a connection

    A HoneyBot sensor sees an unsolicited connection. The source IP address is what the rest of the pipeline works with.

  2. The source IP is looked up

    The address is sent to the IPAPI.GR lookup API, which returns location and network data for it.

  3. The record gets its context

    Country and location fields, ASN, ISP and organisation are stored with the record.

  4. Filters and blocklists

    The enriched records are what people explore and filter by country in the dashboard, next to the published blocklist feeds.

03 · The fields

Which fields matter, and why.

Field names as the API returns them. All are on the free plan; see Response fields for the full list.

country and country_code
Country filters. The two-letter country_code is a stable value to filter and group on; country is the plain English name to show people.
asn
The autonomous system the address belongs to, returned as a string such as "15169". Grouping by ASN shows when many addresses sit on the same network, and helps spot hosting and datacenter networks as opposed to home connections.
organization and isp
organization is the organisation that holds the address and isp is the provider. Together they put a readable name next to the ASN, so an analyst sees a company instead of a number.
region, city, latitude, longitude
Location below country level. Useful for context, but approximate: treat them as an estimate, not a place.

04 · Good practice

Enrich once per IP, not once per hit.

A sensor network sees the same source address again and again. The lookup answer for that address does not change between hits, so the pipeline should not ask twice.

  • Look up each address once. Store the answer with the IP, and attach it to every later record from that address.
  • Cache with a sensible expiry. Network data changes slowly, but it does change. Refresh cached answers from time to time rather than keeping them forever.
  • Use batch lookups for backlogs. POST /api/lookup/batch takes up to 100 addresses per request, and identical addresses in one batch are counted once. Items that time out come back as 504 errors; send those again.
  • Treat "No Data" as missing. Any location or network field can be "No Data". Store it as empty, so a filter never offers "No Data" as a country.
  • Enrich off the hot path. Record the connection first and add context afterwards, so a slow or failed lookup never loses a record.
  • Skip private addresses. 10.0.0.0/8, 127.0.0.1, ::1 and similar have no location, so don't spend a request on them.
JavaScript (Node.js)
// Enrich each source IP once, in batches of up to 100, and reuse the answer for every later hit.
const BATCH = 'https://ipapi.gr/api/lookup/batch?key=' + process.env.IPAPI_KEY;
const context = new Map(); // ip -> network context. In production, use a cache with a TTL.
const known = (v) => (v == null || v === 'No Data' ? null : v); // "No Data" means missing

async function enrich(ips) {
  const fresh = [...new Set(ips)].filter((ip) => !context.has(ip));
  for (let i = 0; i < fresh.length; i += 100) {
    const r = await fetch(BATCH, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({ ips: fresh.slice(i, i + 100) }),
      signal: AbortSignal.timeout(10000)
    });
    if (!r.ok) continue; // keep the records, enrich these addresses on the next run
    const { results } = await r.json();
    for (const item of results) {
      if (item.status === 'error') continue; // e.g. 504: send it again later
      context.set(item.query, {
        country: known(item.country),
        country_code: known(item.country_code), // e.g. "NL", for country filters
        city: known(item.city),                 // approximate
        asn: known(item.asn),                   // a string, e.g. "15169"
        isp: known(item.isp),
        organization: known(item.organization)
      });
    }
  }
  return ips.map((ip) => context.get(ip) || null);
}

05 · Honest limits

What the context can't tell you.

  • Country is usually reliable. City and coordinates are estimates.
  • VPNs, proxies and mobile networks can place an address far from the device behind it.
  • The location of an IP address is not the location of a person, and, as whatoblock.com says of its own listings, it does not identify a person or establish intent.

Add network context to your own records.

Country, location, ASN, ISP and organisation are on the free plan: 1.000 requests a day, single and batch lookups.