The Live DNS Checker API offers real-time access to DNS records, enabling swift and accurate resolution of domain names to IP addresses and vice versa. This powerful tool is essential for network administrators and developers, providing instant network diagnostics, verifying DNS configurations, and troubleshooting connectivity issues. By using the Live DNS API, users can ensure the correctness and availability of their DNS records, streamlining the process of maintaining a reliable and resilient online presence. Whether it's for confirming recent DNS changes, detecting misconfigurations, or ensuring uptime, this API is indispensable for anyone responsible for the integrity and performance of their network infrastructure.
With the Historical DNS Lookup API, you gain a valuable resource to delve into the past and track changes in domain configurations over time. Researchers, cyber-security experts, and businesses can utilise this API to explore domain history, ownership changes, and record modifications. By accessing historical DNS data, organizations can conduct in-depth analyses, identify security threats, and make informed decisions based on the evolution of their domain's infrastructure.
Our Reverse DNS Lookup API provides an extensive range of DNS records, including A, AAAA, SOA, MX, NS, CNAME, TXT, and SPF. With this comprehensive API, effortlessly retrieve associated domain names for various record types and enable yourself to gain valuable insights into domain configurations and ownership. Utilise our Reverse DNS API for email verification, spam prevention, and robust network security. Uncover the true potential of reverse DNS lookups to optimise user experiences, enhance cyber-security measures, and ensure the authenticity of incoming emails.
The Bulk DNS Lookup Tool allows you to efficiently query multiple domains in a single request, retrieving the latest DNS records such as A, AAAA, MX, NS, CNAME, and more. This tool streamlines the process by enabling you to query up to 100 domain names at a time, providing results in JSON or XML format for easy integration and analysis. Whether you're managing a large number of domains or need to verify email addresses, the Bulk DNS Lookup Tool saves time and offers valuable insights into domain configurations and ownership. This capability is highly beneficial for network administrators, domain registrars, and business operators. It enables them to manage multiple domains simultaneously.
Access real-time data for any domain name by using live DNS lookup, NS lookup or MX lookup, ensuring you receive the most current information about domain configurations and server addresses.
Retrieve historical DNS records for a domain, for anyone from A, AAAA, TXT, NS, MX, SOA, SPF, CNAME record or for all of them, providing a comprehensive view of past configurations and changes.
Perform reverse dns lookup to find specific DNS records, for anyone from A, AAAA, TXT, NS, MX, SOA, SPF, CNAME record, and conduct reverse DNS lookups for detailed information.
Conduct bulk DNS lookups for multiple domains simultaneously, saving time and effort by retrieving DNS records for numerous domains in one request.
Our service supports data retrieval in JSON and XML formats, offering flexibility and compatibility with various applications for seamless data integration and processing.
We ensure data consistency and compression, providing accurate information while optimizing storage and bandwidth usage for faster access and reduced costs.
Stay up to date with the latest DNS information, ensuring that you always have access to the most current and accurate domain data available.
{
"domainNames":[
"whoisfreaks.com",
"jfreaks.com"
]
}
The Domain Name System, or DNS, is a system that translates domain names to Internet Protocol (IP) addresses so browsers can load resources from the Internet.
A (IP address), AAAA (IPv6 address), MX (mail server), NS (name server), SOA (start of authority), SPF, TXT, and CNAME records are supported by DNS checker API.
No, DNS record types are not case sensitive.
Our Live Lookup API offers real-time access to various endpoints, including domain whois, SSL and DNS data. By directly connecting to authoritative sources, this API ensures that you receive the most current and up-to-date information, eliminating data latency.
Our Historical API offers a blend of up-to-date information and comprehensive unique historical data. We will provide all previous unique records related to that domain along with the latest data. Please note that we update our database on monthly basis, so the maximum data latency in our historical api data can be 1 month.
To perform Bulk DNS lookup, follow these steps:
By following these steps, you can efficiently retrieve DNS records for multiple domains simultaneously using the Bulk DNS lookup tool.
Bulk DNS API tool allows you to query up to 100 domains at once. You can input any number of domains, from 1 to 100, with each domain on a separate line, to retrieve their respective DNS lookup information.
All available TLDs and their sub-domains are supported by DNS lookup API.
Yes, we will inform you via an email. We send notification email on 80%,90%,100% usage. You can get credits/ subscription usage information from our billing portal or through API.
We provide surcharge requests on all active API credits subscriptions. You can fetch credits and surcharge requests information through our API. Each subscription plan has different surcharge requests limit.
No, We do not charge credits on 4xx status codes in response. All Whois APIs follow same rule for 4xx status codes in response.
We will provide 500 API credits to new users and yes, those credits have a rate-limiting of 10 requests per minute for Live APIs, 5 requests per minute for Bulk Domain Lookup, and 1 request per minute for Reverse/Historical Endpoints.
Yes, we have rate limiting on requests being made on all of our paid plans. The requests limit is shown in the following table.
The Table is divided into three types of plans:
| Credits | Live-rpm | Bulk-rpm | Historical/Reverse-rpm |
|---|---|---|---|
| 5000 | 20 | 8 | 3 |
| 15000 | 35 | 12 | 5 |
| 50000 | 80 | 20 | 10 |
| 150000 | 120 | 25 | 15 |
| 450000 | 150 | 35 | 20 |
| 1000000 | 200 | 50 | 25 |
| 3000000 | 300 | 70 | 35 |
| Credits | Live-rpm | Bulk-rpm | Historical/Reverse-rpm |
|---|---|---|---|
| 5000 | 20 | 8 | 3 |
| 15000 | 35 | 12 | 5 |
| 50000 | 80 | 20 | 10 |
| 150000 | 120 | 25 | 15 |
| 450000 | 150 | 35 | 20 |
| 1000000 | 200 | 50 | 25 |
| 3000000 | 300 | 70 | 35 |
In case, the request per minute exceeds; it'll throw an error with HTTP error code of 429.
Yes, there are following three header parameters in the response:
