{"id":96840,"plugin_id":"plugin_asdk_app_6acf4061581c8191a113796b35d99bae","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T18:10:17.189Z","digest":"d0c8096ae22a13983688b8c4e31f7e3b5e3ffd60da3dd8bd17fc09348a98bbcc","against":null,"payload":{"description":"Look up IP addresses with InternetData: where each one is, whose network it's on and who uses it, its abuse contact and reverse DNS name, whether it's a VPN, a residential, datacenter, mobile or public proxy, a Tor node, a privacy relay, a hosting provider or a CDN, and which services answer on it. Use when someone gives you one or more IP addresses, or text that contains them, and asks where they are, who owns or operates them, whether they're anonymized or risky, or where to report abuse from them.","included_files":[],"name":"check-ips","skill_md_contents":"---\nname: check-ips\ndescription: \"Look up IP addresses with InternetData: where each one is, whose network it's on and who uses it, its abuse contact and reverse DNS name, whether it's a VPN, a residential, datacenter, mobile or public proxy, a Tor node, a privacy relay, a hosting provider or a CDN, and which services answer on it. Use when someone gives you one or more IP addresses, or text that contains them, and asks where they are, who owns or operates them, whether they're anonymized or risky, or where to report abuse from them.\"\n---\n\n# Look up IP addresses with InternetData\n\n1. Collect every IPv4 and IPv6 address in what you were given and drop duplicates. If there are none, ask for them.\n2. For one address call `lookup_ip`. For more than one, call `lookup_ips` once with the whole list: it batches long lists itself, so never split it or loop over `lookup_ip`. A batch needs a key on a paid plan. On any other key, a list of up to 10 is still answered, one address at a time, and a longer one comes back refused on every address: say a list that long needs a paid plan, and offer to look up the 10 the person cares about most.\n3. Read `coverage` before you conclude anything. A field listed in `coverage.not_included` was not returned because of the plan behind the API key, which is not the same as \"no\". Say \"not covered by this key's plan\" for it, never \"not a VPN\". If the person needs those fields, `my_entitlement` shows the plan and what it has used.\n4. A private or reserved address comes back with `is_bogon: true`. Report it as an internal address, not as a clean one.\n5. Report what came back:\n   - One address: where it is, the network and the company behind it, then each positive classification with its provider name when the result has one, then the abuse contact if the person asked who to report to.\n   - Several: a table of address, country, network or company, what it is (VPN, residential proxy, Tor, hosting and so on, or nothing found), provider, and notes, with flagged addresses first, then one line counting each category.\n   - Quote raw JSON only when asked.\n6. If `lookup_ips` returns an error in place of a result for an address, show it in that row and keep the rest. If a call is refused with `unauthorized`, the connection needs signing in again. If it is refused for going over the plan's allowance, check `my_entitlement` and say when it resets.\n\nA positive answer describes the network the address belongs to, not the intent of the person using it. Leave judgement about what to do with a flagged user to the person asking, unless they ask for it; the `review-traffic` skill covers that case.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}