DNS Lookup API

GET

Read any domain's DNS records from your code in one call.

DNS Lookup retrieves published DNS records for any domain, including IPv4 (A), IPv6 (AAAA), and mail exchange (MX) servers. It provides hostnames, priorities, and dual-stack status flags, while paid plans add TXT, CNAME, and nameserver records.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/dnslookup?domain=myspace.com

Query parameters

domainstring

Verification

Format

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

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "myspace.com",
    "records": {
      "A": [
        "34.111.176.156"
      ],
      "AAAA": null,
      "CNAME": null,
      "MX": [
        {
          "exchange": "us-smtp-inbound-1.mimecast.com",
          "priority": 10
        },
        {
          "exchange": "us-smtp-inbound-2.mimecast.com",
          "priority": 10
        }
      ],
      "NS": [
        "ns-cloud-a4.googledomains.com",
        "ns-cloud-a1.googledomains.com",
        "ns-cloud-a2.googledomains.com",
        "ns-cloud-a3.googledomains.com"
      ],
      "PTR": null,
      "SRV": null,
      "SOA": {
        "nsname": "ns-cloud-a1.googledomains.com",
        "hostmaster": "cloud-dns-hostmaster.google.com",
        "serial": 2,
        "refresh": 21600,
        "retry": 3600,
        "expire": 259200,
        "minttl": 300
      },
      "TXT": [
        "cr40m536tje9on1slld9bi81bg",
        "qpdYoeakhlmAxsnmxgAVFmJgUSibqb/y+Eu6GGn8pdmLf+mFGIB3jhRAxIC5KObsPMES9MW2c+oOrpOo/lCQVw==",
        "oZ19a+EOIwWVDPJ7POj14UAGBfzk9xcJMmsTUAMUy7H82sDuVCxvw9rZqdg3znFrdTH04+49zd1djhEAt0ooiA==",
        "MS=ms89904786",
        "google-site-verification=eu-3gW1JePvsGRRCaEvH17YUOTFJNofm4lnz2Pk0LTc",
        "google-site-verification=q0iWqpcfOBclAJaCeWh83v62QQ4uCgbWObQ08p37qgU",
        "al4upe6q5cl13sg4srvfivflvg",
        "v=spf1 mx ip4:63.208.226.34 ip4:204.16.32.0/22 ip4:67.134.143.0/24 ip4:216.205.243.0/24 ip4:34.85.156.5/32 ip4:35.245.108.108/32 ip4:34.86.129.193/32 ip4:34.86.134.94/32 ip4:34.85.222.234/32 ip4:34.86.176.234/32 ip4:34.86.125.212/32 ip4:34.85.224.60/32 ip4:34.86.160.49/32 ip4:35.245.64.166/32 ip4:35.188.226.11/32 ip4:34.86.208.228/32 ip4:34.85.216.144/32 ip4:35.221.22.153/32 ip4:34.86.137.108/32 ip4:34.86.51.35/32 ip4:34.150.221.40/32 ip4:34.85.216.70/32 ip4:34.86.37.191/32 ip4:34.85.214.215/32 ip4:35.236.234.82/32 ip4:34.86.161.241/32 ip4:216.32.181.16 ip4:216.178.32.0/20 ip4:168.235.224.0/24 include:_netblocks.mimecast.com -all",
        "cj65vjpq0s1v9u7vfo020c6rel"
      ],
      "CAA": null
    },
    "summary": {
      "hasIPv6": false,
      "hasMailServers": true,
      "hasSPF": true
    }
  }
}

Start from a template — a working app you can deploy in a minute

DNS Lookup

A domain’s DNS records: where it points, who handles its mail, and more.

Deploy to Vercel See the template →

About the DNS Lookup API

DNS Lookup works by performing a DNS query to retrieve the DNS records of a domain. It returns the A, MX, and other records of the domain.

What people use it for

Mail Delivery Verification: To verify email destination readiness, onboarding systems query incoming domain MX records and priority values before routing outbound messages.
Dual-Stack Infrastructure Auditing: DevOps engineers inspect IPv4 and IPv6 addresses across client domains to confirm dual-stack network reachability and detect missing AAAA entries.
Domain Migration Monitoring: When moving web infrastructure to new hosts, deployment pipelines check resolving A and MX records in real time to verify DNS propagation.
Custom Domain Onboarding: Hosting platforms query target domains during customer onboarding to verify that resolved IP addresses point to designated web servers.

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 DNS Lookup

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 DNS Lookup API.

Read the docs →

Which DNS record types does the lookup return?

The query returns standard records including A, AAAA, and MX records with priority values, along with summary flags for IPv6 and mail server readiness. Upgrading to a paid plan adds CNAME, NS, TXT, and full SOA zone configuration details.

Can I query a full URL or a subdomain?

No, the domain parameter accepts root domain names only, such as example.com. You should not include web protocols like https:// or subdomain prefixes, as the lookup is designed to query root zone records.

Are TXT and nameserver records included on the Free plan?

No, CNAME, NS, SOA, and TXT records require a paid plan, as does the summary flag for SPF verification. The Free plan provides A, AAAA, and MX records, while any paid subscription unlocks the full set of records.

Which plan fits checking 10,000 domains a month?

The Starter plan is sufficient. Each query costs 6 credits, giving you up to 33,333 lookups each month, which works out to about $0.90 per 1,000 calls. The Free plan includes 33 lookups per month for testing.

How fresh is the returned DNS information?

DNS records are queried in real time whenever a request is made. The service performs an active DNS query to fetch live records rather than serving outdated or pre-indexed domain data.

Can I use this DNS data in a commercial product?

Yes, you can integrate and display the returned DNS records inside your own commercial tools or dashboards on any paid plan. The Free plan is restricted to non-commercial evaluation, and direct resale of the raw data is not permitted.

Request parameters — GET /v1/dnslookup

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	`myspace.com`	The domain name for which you want to lookup the DNS records. Do not include the protocol, and not subdomains (e.g., myspace.com) domain

Example request

1
2

curl "https://api.apiverve.com/v1/dnslookup?domain=myspace.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/dnslookup

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": "myspace.com",
    "records": {
      "A": [
        "34.111.176.156"
      ],
      "AAAA": null,
      "CNAME": null,
      "MX": [
        {
          "exchange": "us-smtp-inbound-1.mimecast.com",
          "priority": 10
        },
        {
          "exchange": "us-smtp-inbound-2.mimecast.com",
          "priority": 10
        }
      ],
      "NS": [
        "ns-cloud-a4.googledomains.com",
        "ns-cloud-a1.googledomains.com",
        "ns-cloud-a2.googledomains.com",
        "ns-cloud-a3.googledomains.com"
      ],
      "PTR": null,
      "SRV": null,
      "SOA": {
        "nsname": "ns-cloud-a1.googledomains.com",
        "hostmaster": "cloud-dns-hostmaster.google.com",
        "serial": 2,
        "refresh": 21600,
        "retry": 3600,
        "expire": 259200,
        "minttl": 300
      },
      "TXT": [
        "cr40m536tje9on1slld9bi81bg",
        "qpdYoeakhlmAxsnmxgAVFmJgUSibqb/y+Eu6GGn8pdmLf+mFGIB3jhRAxIC5KObsPMES9MW2c+oOrpOo/lCQVw==",
        "oZ19a+EOIwWVDPJ7POj14UAGBfzk9xcJMmsTUAMUy7H82sDuVCxvw9rZqdg3znFrdTH04+49zd1djhEAt0ooiA==",
        "MS=ms89904786",
        "google-site-verification=eu-3gW1JePvsGRRCaEvH17YUOTFJNofm4lnz2Pk0LTc",
        "google-site-verification=q0iWqpcfOBclAJaCeWh83v62QQ4uCgbWObQ08p37qgU",
        "al4upe6q5cl13sg4srvfivflvg",
        "v=spf1 mx ip4:63.208.226.34 ip4:204.16.32.0/22 ip4:67.134.143.0/24 ip4:216.205.243.0/24 ip4:34.85.156.5/32 ip4:35.245.108.108/32 ip4:34.86.129.193/32 ip4:34.86.134.94/32 ip4:34.85.222.234/32 ip4:34.86.176.234/32 ip4:34.86.125.212/32 ip4:34.85.224.60/32 ip4:34.86.160.49/32 ip4:35.245.64.166/32 ip4:35.188.226.11/32 ip4:34.86.208.228/32 ip4:34.85.216.144/32 ip4:35.221.22.153/32 ip4:34.86.137.108/32 ip4:34.86.51.35/32 ip4:34.150.221.40/32 ip4:34.85.216.70/32 ip4:34.86.37.191/32 ip4:34.85.214.215/32 ip4:35.236.234.82/32 ip4:34.86.161.241/32 ip4:216.32.181.16 ip4:216.178.32.0/20 ip4:168.235.224.0/24 include:_netblocks.mimecast.com -all",
        "cj65vjpq0s1v9u7vfo020c6rel"
      ],
      "CAA": null
    },
    "summary": {
      "hasIPv6": false,
      "hasMailServers": true,
      "hasSPF": 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.

Field	Type	Example	Description
`domain`	string	`"myspace.com"`	The domain name that was queried
`records`	object	`{...}`	Object containing all DNS records for the domain
`A`	array	`[34.111.176.156]`	IPv4 address records for the domain
`AAAA`	object	`null`	IPv6 address records for the domain
`CNAME`Premium	object	`null`	Canonical name alias records
`MX`	array[2]		Mail exchange server records with priority
`exchange`	string	`"us-smtp-inbound-1.mimecast.com"`	Mail server hostname
`priority`	number	`10`	Priority level for the mail server
`NS`Premium	array	`[ns-cloud-a4.googledomains.com, ...]`	Nameserver records for the domain
`PTR`	object	`null`
`SRV`	object	`null`
`SOA`Premium	object	`{...}`	Start of Authority record with DNS zone info
`nsname`Premium	string	`"ns-cloud-a1.googledomains.com"`	Primary nameserver hostname
`hostmaster`Premium	string	`"cloud-dns-hostmaster.google.com"`	Email address of domain administrator
`serial`Premium	number	`2`	Serial number for zone version tracking
`refresh`Premium	number	`21600`	Secondary server refresh interval in seconds
`retry`Premium	number	`3600`	Retry interval for failed transfers
`expire`Premium	number	`259200`	Zone expiration time in seconds
`minttl`Premium	number	`300`	Minimum time to live for records
`TXT`Premium	array	`[cr40m536tje9on1slld9bi81bg, ...]`	Text records including SPF, DKIM, verification data
`CAA`	object	`null`
`summary`	object	`{...}`	At-a-glance flags derived from the records above
`hasIPv6`	boolean	`false`	Whether the domain publishes any AAAA (IPv6) records — indicates dual-stack readiness
`hasMailServers`	boolean	`true`	Whether the domain publishes any MX records — indicates it is configured to receive email
`hasSPF`Premium	boolean	`true`	Whether a TXT record starting with v=spf1 is present — a coarse email-authentication posture flag (use the SPF Validator to parse it)

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 — 6 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	DNS Lookup calls	Per 1,000 calls
Free	Free	200	33	Free
Starter	$29.99	200,000	33,333	$0.90
Pro	$99.99	1,000,000	166,666	$0.60
Mega	$299.99	4,000,000	666,666	$0.45

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/dnslookup

No SDK to install — this is a plain HTTPS call to /v1/dnslookup 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/dnslookup" \
  -H "x-api-key: YOUR_API_KEY"

Resources

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

Also published for

@apiverve/dnslookupnpm apiverve-dnslookupPyPI APIVerve.API.DNSLookupNuGet

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/dnslookup

Install the Node.js SDK, then call the DNS Lookup 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/dnslookup

Node.js

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

Resources

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

Also published for

apiverve-dnslookupPyPI APIVerve.API.DNSLookupNuGet

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

Call it from Python — GET /v1/dnslookup

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

Install — PyPI

pip install apiverve-dnslookup

Python

import requests

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

Resources

PyPIapiverve-dnslookupThe published Python client, versioned and signed.GitHubapiverve/dnslookup-apiSource, issues and the examples this page is built from.ReferenceDNS Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/dnslookupnpm APIVerve.API.DNSLookupNuGet

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/dnslookup

Install the C# / .NET SDK, then call the DNS Lookup 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.DNSLookup

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/dnslookup");
Console.WriteLine(json);

Resources

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

Also published for

@apiverve/dnslookupnpm apiverve-dnslookupPyPI

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

Call it from Go — GET /v1/dnslookup

No SDK to install — this is a plain HTTPS call to /v1/dnslookup 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/dnslookup", 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/dnslookupnpm apiverve-dnslookupPyPI APIVerve.API.DNSLookupNuGet

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

Call it from PHP — GET /v1/dnslookup

No SDK to install — this is a plain HTTPS call to /v1/dnslookup 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/dnslookup");
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/dnslookupnpm apiverve-dnslookupPyPI APIVerve.API.DNSLookupNuGet

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

Call it from Ruby — GET /v1/dnslookup

No SDK to install — this is a plain HTTPS call to /v1/dnslookup 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/dnslookup")
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/dnslookupnpm apiverve-dnslookupPyPI APIVerve.API.DNSLookupNuGet

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

All articles →

DNS Lookups: A Developer's Debugging GuideDNS problems cause connection failures and email issues. Learn how to use DNS lookups to diagnose problems faster.Read

The DNS Migration Checklist Nobody Talks AboutDNS propagation takes 24-48 hours. Except when it doesn't. Here's the zero-downtime DNS migration checklist.Read

Why Your API Integration Keeps BreakingAPIs break in production. Here's why it happens and how to build integrations that survive the real world.Read

DNS Lookup API

Try it — live request, no key required

Start from a template — a working app you can deploy in a minute

DNS Lookup

About the DNS Lookup API

What people use it for

Ways to call it

Other ways to use DNS Lookup

Questions.

Request parameters — GET /v1/dnslookup

Required

Authentication

Response — GET /v1/dnslookup

Response fields

Response headers

Errors

What a call costs — 6 credits per call

Call it from cURL — GET /v1/dnslookup

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/dnslookup

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/dnslookup

Resources

Also published for

Call it from PHP — GET /v1/dnslookup

Resources

Also published for

Call it from Ruby — GET /v1/dnslookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — DNS Lookup API

Domain Data

Related articles

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

Explore the catalog