Nameservers API GET

Nameservers is a tool for looking up the authoritative nameservers for any domain. Returns nameserver hostnames, IP addresses, reverse DNS, and owner information.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/nameservers

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Nameservers response payload
  }
}

About the Nameservers API

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.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Nameservers

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Nameservers API.

Read the docs →

What does the Nameservers API do?

Nameservers is a tool for looking up the authoritative nameservers for any domain. Returns nameserver hostnames, IP addresses, reverse DNS, and owner information.

How do I authenticate Nameservers API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Nameservers API cost?

Each call spends 10 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Nameservers API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Nameservers API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Nameservers API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/nameservers

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`domain`Required	string	`google.com`	The domain name to lookup nameservers for domain

Example request

1
2

curl "https://api.apiverve.com/v1/nameservers?domain=google.com" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/nameservers

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "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
`nameserver`	string	`"ns1.google.com"`	Hostname of the nameserver
`ipAddresses`	array	`[216.239.32.10]`	Addresses the nameserver hostname resolves to
`reverseDns`	string	`"ns1.google.com"`	Hostname the nameserver's address resolves back to
`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

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Nameservers calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/nameservers

No SDK to install — this is a plain HTTPS call to /v1/nameservers with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/nameservers" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/nameservers-apiSource, issues and the examples this page is built from.ReferenceNameservers API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/nameserversnpm APIVerve.API.NameserversNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/nameservers

Install the Node.js SDK, then call the Nameservers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/nameservers

Node.js

const res = await fetch("https://api.apiverve.com/v1/nameservers", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/nameserversThe published Node.js client, versioned and signed.GitHubapiverve/nameservers-apiSource, issues and the examples this page is built from.ReferenceNameservers API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.NameserversNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/nameservers

No SDK to install — this is a plain HTTPS call to /v1/nameservers with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/nameservers",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/nameserversnpm APIVerve.API.NameserversNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/nameservers

Install the C# / .NET SDK, then call the Nameservers API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.Nameservers

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/nameservers");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.NameserversThe published C# / .NET client, versioned and signed.GitHubapiverve/nameservers-apiSource, issues and the examples this page is built from.ReferenceNameservers API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/nameserversnpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/nameservers

No SDK to install — this is a plain HTTPS call to /v1/nameservers with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/nameservers", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/nameserversnpm APIVerve.API.NameserversNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/nameservers

No SDK to install — this is a plain HTTPS call to /v1/nameservers with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/nameservers");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/nameserversnpm APIVerve.API.NameserversNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/nameservers

No SDK to install — this is a plain HTTPS call to /v1/nameservers with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/nameservers")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/nameserversnpm APIVerve.API.NameserversNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read

Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read

Nameservers API GET

Try it — live request, no key required

About the Nameservers API

Ways to call it

Other ways to use Nameservers

Questions.

Request parameters — GET /v1/nameservers

Required

Authentication

Response — GET /v1/nameservers

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — GET /v1/nameservers

Resources

Also published for

Call it from Node.js — GET /v1/nameservers

Resources

Also published for

Call it from Python — GET /v1/nameservers

Resources

Also published for

Call it from C# / .NET — GET /v1/nameservers

Resources

Also published for

Call it from Go — GET /v1/nameservers

Resources

Also published for

Call it from PHP — GET /v1/nameservers

Resources

Also published for

Call it from Ruby — GET /v1/nameservers

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Nameservers API

Networking

Related articles

Ready to build with Nameservers? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog