DNS & network ops
End-to-end DNS health check: records, multi-resolver propagation, WHOIS, ASN, robots.txt, and reachability.
6 tools run server-side in one request. You pay once, settle once, and get a single response - no orchestration, no per-step payments, and a partial-success envelope if any step fails. USDC over x402 on any supported chain.
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
All 6 run inside the single $0.011 call above. Each is also callable on its own if you only need one part.
- DNS lookup 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 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 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) POST /api/whois Domain registration data via RDAP (the structured WHOIS successor): registrar, creation/expiry dates, status, nameservers.
- HTTP check 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 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.
Bought one at a time, these 6 tools cost $0.012 together; the pack is that sum less a 10% bundle discount, rounded up to the $0.001 settlement floor, which is $0.011.
Workflow
- Resolve A/AAAA/MX/TXT/NS/CAA records on the apex with dns-lookup to baseline what the authoritative answer should be.
- Run dns-propagation across Cloudflare/Google/Quad9/OpenDNS in parallel - divergent answers mean a stale cache somewhere or a botched TTL during a migration.
- 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.
- Pull whois for ownership, expiry, and registrar - catches the 'we forgot to renew' class of outage.
- Run http-check for status code, response time, and final URL after redirects - the fastest 'is it actually up' read.
- Spot-check robots.txt with robots-check to make sure a redeploy didn't accidentally Disallow: / the whole site.
Arguments
| Name | Required | Description | Example |
|---|---|---|---|
domain | yes | Domain to check (e.g. stripe.com) | agent402.tools |
What one call returns
A JSON object with pack, args, steps, summary; steps holds one entry per tool (dns-lookup, dns-propagation, asn-info, whois, http-check, robots-check), each with its own result or error. Full example on the API page.
Call it directly
Any x402 client pays the 402 and gets the whole workflow back in one response. With the agent402-client SDK (npm i agent402-client, an ES module):
import { Agent402 } from "agent402-client";
// payFetch: an x402-wrapped fetch your wallet signs (@x402/fetch).
// Tools on the free tier need no options: new Agent402() pays them by proof-of-work.
// an existing prepaid credits key also works: new Agent402({ creditsKey })
const client = new Agent402({ fetch: payFetch });
const result = await client.call("skill-dns-network-ops", {"domain":"agent402.tools"});
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 agent402.tools. 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.