DNS & network ops

End-to-end DNS health check: records, multi-resolver propagation, WHOIS, ASN, robots.txt, and reachability.

When to use this pack

Investigating a DNS-related outage, debugging propagation after a record change, or onboarding a new domain and checking the operator chain.

Tools in this pack

• DNS lookup $0.002 POST /api/dns-lookup Resolve any DNS record type for a host: A, AAAA, MX, TXT, CNAME, NS, SOA, CAA, SRV, PTR. Returns the records plus a count. Built on Node's native resolver — no external API.
• DNS propagation check $0.003 POST /api/dns-propagation Resolve the same DNS record against 4 public resolvers (Google, Cloudflare, Quad9, OpenDNS) in parallel; surface divergences. The first call you make after a DNS change — confirms the world sees what you intended.
• ASN + IP geolocation $0.003 POST /api/asn-info Look up the Autonomous System (ASN), prefix, country, registry, and allocation date for an IPv4 address — or for a hostname (which is resolved first). Uses Team Cymru's free DNS-based IP→ASN mapping; no HTTPS upstream, no auth, no rate-limit headaches.
• Domain WHOIS (RDAP) $0.003 POST /api/whois Domain registration data via RDAP (the structured WHOIS successor): registrar, creation/expiry dates, status, nameservers.
• HTTP check $0.003 POST /api/http-check Check any public URL: status code, latency, final URL after redirects, and response headers. The uptime primitive for agent monitors.
• Robots.txt check $0.002 POST /api/robots-check Fetch a site's robots.txt and answer: may this user-agent crawl this path? Returns the matched rule and all declared sitemaps.

Workflow

1. Resolve A/AAAA/MX/TXT/NS/CAA records on the apex with dns-lookup to baseline what the authoritative answer should be.
2. Run dns-propagation across Cloudflare/Google/Quad9/OpenDNS in parallel — divergent answers mean a stale cache somewhere or a botched TTL during a migration.
3. Look up the ASN and prefix that the apex resolves into with asn-info (Team Cymru DNS-based whois — no auth needed). Useful for spotting an unexpected hosting move.
4. Pull whois for ownership, expiry, and registrar — catches the 'we forgot to renew' class of outage.
5. Run http-check for status code, response time, and final URL after redirects — the fastest 'is it actually up' read.
6. Spot-check robots.txt with robots-check to make sure a redeploy didn't accidentally Disallow: / the whole site.

Run it in Claude

claude mcp add agent402 -s user -- npx -y agent402-mcp@latest

Then paste this prompt into Claude:

Run a DNS health check on example.com. Use Agent402 to: pull the apex DNS records, check propagation across major public resolvers, look up the ASN/prefix, pull whois for ownership and expiry, run an HTTP reachability check, and confirm robots.txt isn't broken. Report any inconsistency or near-expiry.

← All skill packs