Nameserver Lookup Skill

Overview

Nameservers works by querying DNS NS records for a domain to retrieve its authoritative nameservers. For each nameserver, it resolves IP addresses and performs reverse DNS lookups to identify the hosting provider.

Live Test Nameserver Lookup Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as NameserverLookupSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "NameserverLookupSkill",
  "arguments": {
    "domain": "google.com"
  }
}

You do not name the tool yourself; the model picks it. Asking about google.com in the terms this skill covers is enough for it to reach for NameserverLookupSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`domain`Required	string	The domain name to lookup nameservers for domain

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "google.com",
    "nameserverCount": 4,
    "hasMultipleProviders": false,
    "nameservers": [
      {
        "nameserver": "ns1.google.com",
        "ipAddresses": [
          "216.239.32.10"
        ],
        "reverseDns": "ns1.google.com",
        "owner": "google.com"
      },
      {
        "nameserver": "ns2.google.com",
        "ipAddresses": [
          "216.239.34.10"
        ],
        "reverseDns": "ns2.google.com",
        "owner": "google.com"
      }
    ],
    "uniqueOwners": [
      "google.com"
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`domain`	string	`google.com`	The domain the nameservers were looked up for
`nameserverCount`	number	`4`	Number of nameservers found
`hasMultipleProviders`	boolean	`false`	Whether nameservers are distributed across multiple providers
`nameservers`	array[2]		The authoritative nameservers for the domain
`nameservers.0.nameserver`	string	`ns1.google.com`	Hostname of the nameserver
`nameservers.0.ipAddresses`	array	`["216.239.32.10"]`	Addresses the nameserver hostname resolves to
`nameservers.0.reverseDns`	string	`ns1.google.com`	Hostname the nameserver's address resolves back to
`nameservers.0.owner`	string	`google.com`	Domain the nameserver itself belongs to, showing who runs it
`uniqueOwners`Premium	array	`["google.com"]`	List of unique nameserver owners/providers

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

DNS Redundancy Verification: Site reliability engineers check whether production domains use multiple DNS providers to prevent total outages during single-provider DNS incidents.
Domain Transfer Tracking: When migrating web properties between registrars, DevOps teams verify nameserver IP propagation before cutting over live production traffic.
Phishing Infrastructure Profiling: Flag newly registered copycat domains pointing to suspicious nameserver infrastructure by analyzing reverse DNS and server ownership domains.
Hosting Provider Audits: Compliance platforms monitor external enterprise domains to confirm their DNS points only to approved corporate nameservers and infrastructure.

Other ways to use Nameserver Lookup Skill

Set up Nameserver Lookup Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →