Docs/Skills/Reverse DNS Lookup Skill

Reverse DNS Lookup Skill

Get hostname from IP address

OperationalCredits 10 per callp50 747msDomain Data

Overview

Reverse DNS Lookup works by querying the PTR record for an IP address to find its associated hostname. This is useful for identifying servers, verifying email sender authenticity, and network troubleshooting.

Live Test Reverse DNS Lookup Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as ReverseDNSLookupSkill. 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": "ReverseDNSLookupSkill",
  "arguments": {
    "ip": "8.8.8.8"
  }
}

You do not name the tool yourself; the model picks it. Asking about 8.8.8.8 in the terms this skill covers is enough for it to reach for ReverseDNSLookupSkill 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.

ArgumentTypeDescription
ipRequiredstringThe IP address to lookup (IPv4 or IPv6)
ip

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": {
    "ip": "8.8.8.8",
    "hostname": "dns.google",
    "ptr": [
      "dns.google"
    ],
    "found": true
  }
}

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.

FieldTypeExampleDescription
ipstring8.8.8.8The IP address that was queried
hostnamestringdns.googleHostname associated with the IP address
ptrarray["dns.google"]All PTR hostnames resolved for the IP address
foundbooleantrueWhether a PTR record was found

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.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This skill is not part of VerveKit. Check the catalog.
429Out 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

Email Verification
Verify email sender authenticity by checking if the sending IP has a valid reverse DNS entry matching the sender domain
Server Identification
Identify what server or service is running on an IP address by looking up its hostname
Network Troubleshooting
Diagnose network issues by verifying that IP addresses resolve to expected hostnames
Security Analysis
Investigate suspicious IPs by discovering their associated hostnames and infrastructure

Other ways to use Reverse DNS Lookup Skill

Set up Reverse DNS 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 →

More in Domain Data:

Was this page helpful?