dns.tools

What It Is

DNS.Tools API is a domain and website intelligence service for developers. Its goal is to wrap the underlying complexity of DNS, WHOIS, RDAP, and related protocols into a simple HTTPS REST API. It uses GET requests and JSON responses, with endpoints such as https://api.dns.tools/v1/{tool}/{query}. It is suitable for embedding into monitoring, troubleshooting, security analysis, asset inventory, or internal operations tools.

Core Capabilities

The DNS Lookup API is its main feature, supporting more than 30 record types, including A, AAAA, MX, TXT, NS, SOA, CAA, TLSA, DS, DNSKEY, HTTPS, SVCB, and more. It also supports ALL queries. Users can specify DNS servers, query authoritative servers, toggle recursion, choose TCP/UDP transport, and enable DNSSEC validation with additional DNSSEC records returned. The Domain API automatically selects RDAP or WHOIS as the data source and returns normalized fields such as domain creation, expiration, and update dates, registrar, registrant, domain status, NS, and DNSSEC information. Privacy-protected fields are returned as null. IDN support covers both Unicode and Punycode, making it relatively friendly for internationalized domain names.

API, Documentation, and Ecosystem

The service uses a unified response structure that includes requestId, timestamp, duration, cache flag, error code, and result array, making it easier to trace logs and troubleshoot exceptions. Authentication is flexible, with support for X-API-Key, Bearer Token, and URL query parameters. The documentation covers authentication, requests, responses, rate limits, error handling, and provides curl and JavaScript Fetch examples, along with an OpenAPI Spec and Swagger UI. The main content does not mention official SDKs, a plugin marketplace, or third-party integrations, but the standard HTTP/JSON interface and OpenAPI support should be sufficient for most teams to build their own integrations.

Pricing and Limits

It offers a free tier with no registration and no API Key required, making it suitable for testing and lightweight use. Higher limits, production use, high-capacity needs, or enterprise plans require contacting the provider. The downside is that the documentation does not disclose the specific free quota, paid pricing, SLA, or plan differences. Rate limiting is only described at a high level: the free tier is limited by IP, authenticated requests are limited by API Key, and requests over the limit return 429.

Pros, Cons, and Who It Is For

Its strengths are low integration friction, broad DNS capability coverage, stable response formatting, and clear documentation examples. It is well suited to developers, SREs, operations teams, security teams, and SaaS products that need domain intelligence. The main drawbacks are the lack of transparent commercial information, and the absence of clear statements on self-hosting, open source availability, SDKs, or availability in China. Enterprises with strict compliance requirements, private deployment needs, or fixed cost planning should confirm details with the provider first.

Access from China

The main content does not provide information about network connectivity from mainland China, payment methods, or localized support, so its availability should be considered unknown. For production use in China, it is recommended to test latency, stability, and rate limits first. Alternatives to compare include Cloudflare/Google DNS query APIs, WhoisXML API, SecurityTrails, and DomainTools.