[Maximum of 100 domains and 100 IPv4 addresses are allowed]
Note: For domain name(s), all available records of these 8 DNS types will be fetched: A, AAAA, MX, NS, SPF, SOA, TXT, and CNAME. For IP address(es), only the PTR record will be fetched.
A bulk DNS lookup queries DNS records for multiple domains in a single batch request rather than one domain at a time. Where a standard DNS lookup returns A, AAAA, MX, NS, SPF, SOA, TXT, and CNAME records for one domain, bulk DNS scales that to a list - useful when you need DNS data for an entire portfolio, threat-feed indicator list, or post-migration verification set. WhoisFreaks supports up to 100 domains or 100 IPv4 addresses per batch in the web tool; the API supports far higher concurrency for enterprise-scale lists.
Feature: Up to 100 domains or 100 IPv4 addresses per query; all 8 DNS record types returned for each domain
Feature: For IPv4 inputs, PTR (reverse DNS) records are returned instead
Feature: Optional record-type filter via the API reduces response size when you only need MX, NS, or TXT
Feature: Free tool covers ad-hoc batches; programmatic access for portfolio-scale work available through the API
For continuous bulk DNS monitoring, scheduled portfolio audits, and integration into SIEM or SOAR platforms, the DNS Checker API for portfolio-scale lookups returns parsed JSON for thousands of domains per request with concurrent processing.
Bulk DNS shows up wherever DNS data needs to be reconciled across a list rather than a single domain: email-security audits across a portfolio, post-migration verification, threat-feed enrichment, and scheduled change detection. The four use cases below are where it matters most.
Security and IT teams responsible for large domain portfolios use Bulk DNS Lookup to audit email authentication configurations across every domain. By pulling TXT records (SPF, DKIM, DMARC) and MX records for all owned domains simultaneously, teams can instantly identify which domains are missing SPF policies, have misconfigured DMARC, or have unauthorized MX servers - risks that enable email spoofing and phishing under your brand.
After migrating dozens or hundreds of domains to a new DNS provider or nameserver infrastructure, Bulk DNS Lookup verifies the migration completed correctly across the entire portfolio - confirming A records, CNAME configurations, and NS records updated as expected for every domain in one pass.
When processing domain indicator lists from threat feeds - which can contain hundreds of IOCs - security teams use Bulk DNS Lookup to rapidly enrich each indicator with current DNS data: what IP is this domain currently pointing to? Is it using a bulletproof nameserver? Has it recently changed infrastructure? This enrichment happens in seconds rather than hours of manual lookups.
Organizations that need to detect unauthorized DNS changes across their domain portfolio run scheduled Bulk DNS Lookups and compare results against a known-good baseline. Unexpected A record, MX, or NS changes are strong indicators of domain hijacking or BGP-level attacks. Pair with the Historical DNS Lookup for change context.
WhoisFreaks queries authoritative nameservers for each domain in the batch (not cached resolvers), so results reflect the current zone state even for recently changed configurations. Each domain in the batch is processed independently, so a single failed lookup doesn't poison the rest of the batch.
Filter your bulk results to a specific record type via the DNS Checker API (e.g., only MX records) to reduce payload size and processing time when you only need one record type across a large list.
