DNS Lookup API
Overview
To use DNS Lookup, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/dnslookupExample
How to call the DNS Lookup API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/dnslookup?domain=myspace.com" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/dnslookup?domain=myspace.com', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/dnslookup?domain=myspace.com', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/dnslookup?domain=myspace.com", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"domain": "myspace.com",
"records": {
"A": [
"34.111.176.156"
],
"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"
],
"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"
]
}
}
}Authentication
The DNS Lookup API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the DNS Lookup API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the DNS Lookup API:
Lookup DNS
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
domain | string | required | The domain name for which you want to lookup the DNS records. Do not include the protocol, and not subdomains (e.g., myspace.com) Format: domain (e.g., myspace.com) | - |
Response
The DNS Lookup API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<domain>myspace.com</domain>
<records>
<A>
<item>34.111.176.156</item>
</A>
<MX>
<item>
<exchange>us-smtp-inbound-1.mimecast.com</exchange>
<priority>10</priority>
</item>
<item>
<exchange>us-smtp-inbound-2.mimecast.com</exchange>
<priority>10</priority>
</item>
</MX>
<NS>
<item>ns-cloud-a4.googledomains.com</item>
<item>ns-cloud-a1.googledomains.com</item>
<item>ns-cloud-a2.googledomains.com</item>
<item>ns-cloud-a3.googledomains.com</item>
</NS>
<SOA>
<nsname>ns-cloud-a1.googledomains.com</nsname>
<hostmaster>cloud-dns-hostmaster.google.com</hostmaster>
<serial>2</serial>
<refresh>21600</refresh>
<retry>3600</retry>
<expire>259200</expire>
<minttl>300</minttl>
</SOA>
<TXT>
<item>cr40m536tje9on1slld9bi81bg</item>
<item>qpdYoeakhlmAxsnmxgAVFmJgUSibqb/y+Eu6GGn8pdmLf+mFGIB3jhRAxIC5KObsPMES9MW2c+oOrpOo/lCQVw==</item>
<item>oZ19a+EOIwWVDPJ7POj14UAGBfzk9xcJMmsTUAMUy7H82sDuVCxvw9rZqdg3znFrdTH04+49zd1djhEAt0ooiA==</item>
<item>MS=ms89904786</item>
<item>google-site-verification=eu-3gW1JePvsGRRCaEvH17YUOTFJNofm4lnz2Pk0LTc</item>
<item>google-site-verification=q0iWqpcfOBclAJaCeWh83v62QQ4uCgbWObQ08p37qgU</item>
<item>al4upe6q5cl13sg4srvfivflvg</item>
<item>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</item>
<item>cj65vjpq0s1v9u7vfo020c6rel</item>
</TXT>
</records>
</data>
</response>
status: ok
error: null
data:
domain: myspace.com
records:
A:
- 34.111.176.156
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
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
| key | value |
|---|---|
| domain | myspace.com |
| records | {A:[34.111.176.156],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],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]} |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
domain | string | The domain name that was queried | |
records | object | Object containing all DNS records for the domain | |
â”” A | array | IPv4 address records for the domain | |
| [ ] Array items: | array[2] | Mail exchange server records with priority | |
â”” exchange | string | - | |
â”” priority | number | - | |
â”” NSPremium | array | Nameserver records for the domain | |
â”” SOAPremium | object | Start of Authority record with DNS zone info | |
â”” nsname | string | Primary nameserver hostname | |
â”” hostmaster | string | Email address of domain administrator | |
â”” serial | number | Serial number for zone version tracking | |
â”” refresh | number | Secondary server refresh interval in seconds | |
â”” retry | number | Retry interval for failed transfers | |
â”” expire | number | Zone expiration time in seconds | |
â”” minttl | number | Minimum time to live for records | |
â”” TXTPremium | array | Text records including SPF, DKIM, verification data |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access DNS Lookup through GraphQL to combine it with other API calls in a single request. Query only the dns lookup data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
dnslookup(
input: {
domain: "myspace.com"
}
) {
domain
records {
A
MX
NS
SOA {
nsname
hostmaster
serial
refresh
retry
expire
minttl
}
TXT
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The DNS Lookup API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
DNS Lookup requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The DNS Lookup API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for DNS Lookup
Official DNS Lookup packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
DNS Lookup works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for DNS Lookup?
How many credits does DNS Lookup cost?
Each successful DNS Lookup API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful dns lookup lookups.
Can I use DNS Lookup in production?
The free plan is for testing and development only. For production use of DNS Lookup, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use DNS Lookup from a browser?
What happens if I exceed my DNS Lookup credit limit?
When you reach your monthly credit limit, DNS Lookup API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








