[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.
Bulk DNS Lookup retrieves all DNS record types - A, AAAA, MX, NS, SPF, SOA, TXT, and CNAME - for a list of domains in a single operation. Where individual DNS Lookup handles one domain at a time, Bulk DNS scales to hundreds or thousands of domains simultaneously, returning consistent structured data for each.
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 Historical DNS Lookup for change context.
Filter your bulk results to a specific record type via the API (e.g., only MX records) to reduce payload size and processing time when you only need one record type across a large list.
