gtrace-ip-enrichment

Enrich IP addresses with ASN ownership, geolocation, and reverse DNS.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/dgethings/netclaw --skill gtrace-ip-enrichment-dgethings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gtrace-ip-enrichment
Source: https://github.com/dgethings/netclaw/tree/main/workspace/skills/gtrace-ip-enrichment
Command: npx skills add https://github.com/dgethings/netclaw --skill gtrace-ip-enrichment-dgethings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly enrich IP observations with contextual ownership, location, and hostname data to support network investigations and incident response.

Core Features & Use Cases

  • ASN ownership lookup for an IP to reveal the owning organization and network range
  • GeoLookup to determine city, region, country, and coordinates
  • Reverse DNS resolution to identify PTR hostname for onboarding and troubleshooting
  • Workflow integration with traceroute hops to annotate each hop with ASN and geo context

Quick Start

Invoke the gtrace IP enrichment to enrich a target IP with ASN, geo data, and reverse DNS.

Frequently Asked Questions about gtrace-ip-enrichment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enrich IP addresses with ASN ownership and geolocation data for log analysis?

To enrich IP addresses with ASN ownership and geolocation data, this Skill performs lookups using the gtrace MCP tools to append owning organization, network range, city, region, country, and coordinates to your IP logs. It also resolves reverse DNS for hostname context.

Can I annotate traceroute hops with ASN and geo context automatically?

Yes, you can annotate traceroute hops with ASN and geo context automatically. The Skill integrates with traceroute workflows by applying ASN ownership, geolocation, and reverse DNS lookups to each observed IP hop to support network investigations.

What is reverse DNS resolution and when do I need it for incident response?

Reverse DNS resolution identifies the PTR hostname associated with an IP address. You need it for incident response and troubleshooting to quickly contextualize IP observations with ownership, location, and hostname data during network investigations.

Do I need internet access to perform ASN lookup and geo lookup on target IPs?

Yes, you need internet access to perform ASN lookup and geo lookup on target IPs. The Skill relies on external IP intelligence lookups via the gtrace MCP tools to retrieve ownership, geolocation, and reverse DNS data.

How do I get BGP context for an IP address during incident response?

To get BGP context for an IP address during incident response, the Skill performs ASN ownership lookups to reveal the owning organization and network range. This provides the necessary BGP context alongside geolocation and reverse DNS data.

What's the best way to add hostname and location context to raw network logs?

The best way to add hostname and location context to raw network logs is to use an IP enrichment workflow that applies reverse DNS resolution and geo lookups. This Skill annotates your IP observations with PTR hostnames, city, region, country, and coordinates.