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. Works as a nameserver lookup (NS lookup) and names the provider behind each server: a provider family from the hostname plus a readable host name such as Amazon Route 53, GoDaddy or Cloudflare for the common DNS hosts.
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/nameservers?domain=google.com" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/nameservers?domain=google.com', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/nameservers?domain=google.com",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/nameservers?domain=google.com", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
domainRequired | string | The domain name to lookup nameservers for domain |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"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 the nameservers span more than one DNS provider: more than one provider family in the hostnames, or more than one network behind them (self-branded nameservers run by two operators count) |
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" | Registrable domain of the reverse DNS name for the nameserver's first address. It shows who set the reverse record, which is not always who runs the server; network has the operator |
uniqueOwnersPremium | array | [google.com] | Distinct owner domains (from each nameserver address's reverse DNS). uniqueNetworks names who actually runs the servers |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
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 Nameservers
Set up Nameservers on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Networking: