Our Bulk DNS Lookup API is designed to streamline DNS management by allowing you to perform bulk DNS lookups with ease. This powerful tool enables you to fetch DNS records for hundreds of domains in one request, including A, AAAA, MX, NS, SOA, SPF, TXT, and CNAME records. Ideal for those needing DNS bulk lookup, it enhances efficiency and accuracy for network administrators, domain managers, and cybersecurity professionals handling large-scale DNS queries
Leverage our Bulk DNS Lookup API to conduct real-time DNS searches for multiple domains within a single request. This feature enables you to execute live DNS lookups, providing the most current and accurate DNS records across hundreds of domains simultaneously. Our API delivers up-to-date information on A, AAAA, MX, NS, SOA, SPF, TXT, and CNAME records, empowering you to swiftly identify and resolve domain-related issues.
When conducting bulk DNS lookups with our API, you can precisely select from A, AAAA, MX, NS, SOA, SPF, TXT, and CNAME records for each hostname included in your request. This targeted lookup capability enables you to filter out unnecessary data, streamlining your DNS checks and improving efficiency.
Maximize efficiency with our Bulk DNS Lookup API, which supports up to 100 hostnames per request. This advanced feature enables you to process extensive batches of hostname queries simultaneously, significantly streamlining your workflow and conserving valuable time. By handling large-scale DNS lookups in a single request, our API enhances your operational productivity and provides seamless management of multiple hostnames, ensuring rapid and accurate results for effective domain administration.
$ pip install requests
Parameter | Required | Type | Default | Description |
---|---|---|---|---|
type | Yes | Array | - | A comma-separated list of DNS record types for lookup is required. The values can be A, AAAA, MX, NS, SOA, SPF, TXT, CNAME, or all. |
The request body must be in JSON format and include a comma-separated list of hostnames for which to retrieve DNS records
{ "domainNames":[ "google.com", "paypal.us" ] }
For a comprehensive view of the API response structure and detailed field descriptions, explore the interactive Response Table by clicking here.
If the entire request encounters an error, specific error codes will be returned. However, if an individual hostname fails to retrieve DNS records or experiences another issue, the status for that hostname will be marked as false. The response will still include DNS records for the remaining hostnames, ensuring you receive the maximum amount of useful information available.
HTTP Status | Reasons |
---|---|
400 | Unable to process request. |
408 | Unable to fetch dns records. Please try after some time. |
500 | Internal Server error occurred. |
503 | Service is unavailable. Please try after some time. |
504 | Request is timed-out |
To look up specific DNS records, including A, AAAA, MX, NS, SOA, SPF, TXT, and CNAME, include the type parameter in your request. Specify a comma-separated list of record types for targeted lookups, or use all to obtain all supported DNS records for each hostname.
{ "bulk_dns_info": [ { "status": true, "queryTime": "2024-08-15 15:26:09", "domainName": "paypal.us", "domainRegistered": true, "dnsTypes": { "A": 1, "MX": 15 }, "dnsRecords": [ { "name": "paypal.us", "type": 1, "dnsType": "A", "ttl": 3600, "rawText": "paypal.us. 3600 IN A 3.33.139.32", "rRsetType": 1, "address": "3.33.139.32" }, { "name": "paypal.us", "type": 15, "dnsType": "MX", "ttl": 21600, "rawText": "paypal.us. 21600 IN MX 1 bh.markmonitor.com.", "rRsetType": 15, "target": "bh.markmonitor.com.", "priority": 1 } ] }, { "status": true, "queryTime": "2024-08-15 15:26:09", "domainName": "google.com", "domainRegistered": true, "dnsTypes": { "A": 1, "MX": 15 }, "dnsRecords": [ { "name": "google.com", "type": 1, "dnsType": "A", "ttl": 164, "rawText": "google.com. 164 IN A 142.250.179.142", "rRsetType": 1, "address": "142.250.179.142" }, { "name": "google.com", "type": 15, "dnsType": "MX", "ttl": 218, "rawText": "google.com. 218 IN MX 10 smtp.google.com.", "rRsetType": 15, "target": "smtp.google.com.", "priority": 10 } ] } ] }curl --location 'https://api.apifreaks.com/v1.0/domain/dns/live?type=a%2Cmx&apiKey=API-KEY' --header 'Content-Type: application/json' --data '{ "domainNames":[ "google.com", "paypal.us" ] }'
Submit hostnames or URLs in the request body. Our API will return the corresponding DNS records for each entry, providing precise and comprehensive data tailored to your requirements.
{ "bulk_dns_info": [ { "status": true, "queryTime": "2024-08-15 15:30:18", "domainName": "https://jfreaks.com", "domainRegistered": true, "dnsTypes": { "A": 1, "MX": 15 }, "dnsRecords": [ { "name": "jfreaks.com", "type": 1, "dnsType": "A", "ttl": 300, "rawText": "jfreaks.com. 300 IN A 104.21.20.167", "rRsetType": 1, "address": "104.21.20.167" }, { "name": "jfreaks.com", "type": 1, "dnsType": "A", "ttl": 300, "rawText": "jfreaks.com. 300 IN A 172.67.193.56", "rRsetType": 1, "address": "172.67.193.56" }, { "name": "jfreaks.com", "type": 15, "dnsType": "MX", "ttl": 3600, "rawText": "jfreaks.com. 3600 IN MX 0 jfreaks-com.mail.protection.outlook.com.", "rRsetType": 15, "target": "jfreaks-com.mail.protection.outlook.com.", "priority": 0 } ] }, { "status": true, "queryTime": "2024-08-15 15:30:18", "domainName": "google.com", "domainRegistered": true, "dnsTypes": { "A": 1, "MX": 15 }, "dnsRecords": [ { "name": "google.com", "type": 1, "dnsType": "A", "ttl": 300, "rawText": "google.com. 300 IN A 142.251.39.110", "rRsetType": 1, "address": "142.251.39.110" }, { "name": "google.com", "type": 15, "dnsType": "MX", "ttl": 5, "rawText": "google.com. 5 IN MX 10 smtp.google.com.", "rRsetType": 15, "target": "smtp.google.com.", "priority": 10 } ] } ] }curl --location 'https://api.apifreaks.com/v1.0/domain/dns/live?type=a%2Cmx&apiKey=API-KEY' --header 'Content-Type: application/json' --data '{ "domainNames":[ "google.com", "https://jfreaks.com" ] }'
To use the Bulk DNS Lookup API, API credits are required. Charges apply only for successful queries, which are defined by a 2xx status code. If a request results in a 4xx or 5xx status code, no credits will be deducted, and any credits already charged will be refunded. Credits are applied based on each domain name specified in your request. If an error occurs with a specific domain name, credits will be refunded for that domain, and you will be charged only for successful DNS lookups.
Service | Credits |
---|---|
DNS Data per Domain Name | 15 credits per successful domain name DNS lookup |
Utilize the Credits Usage API to efficiently monitor your recent consumption of both one-off and subscription credits. This API provides a streamlined way to track and manage your credit usage, ensuring you stay informed about your remaining balance and can optimize your resource allocation effectively.