Overview
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.
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/dnslookup?domain=myspace.com" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/dnslookup?domain=myspace.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/dnslookup?domain=myspace.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/dnslookup?domain=myspace.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 for which you want to lookup the DNS records. Do not include the protocol, and not subdomains (e.g., myspace.com) 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": "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"
]
},
"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 |
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 |
NSPremium | array | [ns-cloud-a4.googledomains.com, ...] | Nameserver records for the domain |
SOAPremium | object | {...} | Start of Authority record with DNS zone info |
nsnamePremium | string | "ns-cloud-a1.googledomains.com" | Primary nameserver hostname |
hostmasterPremium | string | "cloud-dns-hostmaster.google.com" | Email address of domain administrator |
serialPremium | number | 2 | Serial number for zone version tracking |
refreshPremium | number | 21600 | Secondary server refresh interval in seconds |
retryPremium | number | 3600 | Retry interval for failed transfers |
expirePremium | number | 259200 | Zone expiration time in seconds |
minttlPremium | number | 300 | Minimum time to live for records |
TXTPremium | array | [cr40m536tje9on1slld9bi81bg, ...] | Text records including SPF, DKIM, verification data |
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 |
hasSPFPremium | 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) |
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
- Domain Management
- Manage domain records by using the DNS Lookup API. Retrieve the DNS records of a domain to verify configurations and troubleshoot issues
- Network Monitoring
- Monitor network performance by using the DNS Lookup API to check the DNS records of domains. Identify issues with DNS resolution and connectivity
- Security Analysis
- Analyze domain security by using the DNS Lookup API to inspect DNS records. Check for misconfigurations and vulnerabilities in domain settings
- Web Development
- Develop websites by using the DNS Lookup API to retrieve DNS records. Use the data to configure domain settings and optimize website performance
Other ways to use DNS Lookup
Set up DNS Lookup 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 Domain Data: