IP Intelligence playbook
Stop bots burning your paid-ads budget
Paid search and paid social burn budget on traffic that never converts. A meaningful slice of that traffic is automated, originating from datacenter ASNs, commercial proxy networks, or affiliate-fraud farms. Catching it at the IP layer is the cheapest place to drop it. Application-layer scoring still matters, but most of the obvious waste lives in the ASN.
This playbook uses three fields from the IP Intelligence response: asn.type, is_residential_proxy, and recommendation.severity. One lookup, one boolean, one decision. Add it to the landing-page handler before you log a paid-click event and the ad platform stops getting a positive conversion signal from bot traffic.
Try it now
Free tier returns the same shape. Sign in for a key, replace the placeholder, watch the response.
curl -H "Authorization: Bearer dk_live_..." \ "https://dnschkr.com/api/v1/ip?address=185.220.101.1" # Reject the click if either is true: # data.asn.type === "hosting" // datacenter origin # data.is_residential_proxy === true // commercial proxy # data.recommendation.severity >= 2 // any high-severity flag
What this catches
Datacenter clicks are the cleanest signal: a hosting ASN ( asn.type === "hosting") reaching a paid landing page is almost never a real consumer. Commercial residential-proxy services (Bright Data datacenter, Smartproxy, Oxylabs ISP) ship through ASNs DNS Checker tracks; the is_residential_proxy flag carries a detection_sources[] array so the logic is replayable in an audit.
What this does not catch by itself: SDK-residential pools running on real consumer devices (Bright Data EarnApp, Honeygain, Massive, IPRoyal Pawns). Those clicks egress through real residential ISP IPs and look identical to a real consumer at the network layer. Behavioural signals at the application layer (mouse paths, form-fill timing, conversion completion) remain the right tool for that segment.