Zone Files Explained: Acquiring and Filtering Domain Data

Zone files are the bedrock of domain intelligence: a snapshot of every active domain under a given Top-Level Domain, together with its DNS records. Understanding how to acquire, parse and filter them is what separates a domain dataset you can act on from a large text file you cannot. This guide covers where zone data comes from, why country-code zones are so much harder to obtain than generic ones, and how to reduce a raw feed to something usable.

TL;DR

• Raw newly registered domain (NRD) feeds are noisy — a large share are parked or PPC spam, so filtering is mandatory before use.
• Acquiring ccTLD zone files is significantly harder than gTLDs; registries such as .de and .fr publish no public zone, which forces reliance on aggregated data.
• A domain list's value for cold email decays quickly without MX validation — re-check deliverability the same week you send.
• WebTrackly covers 716 TLD zone files and 716 enriched zone sets, 279,944,703 domains across zones, delivered as CSV inside a ZIP.
• For time-sensitive lead generation, a recent export beats a much larger but aged marketplace dump.

Understanding the Zone File

A zone file is a plain-text file listing the active domain names under a specific TLD along with their DNS records. The .com zone file, for instance, lists every registered .com domain and its nameserver (NS) records — 163,422,083 domains in the current WebTrackly export of that zone. Access to gTLD zone files is governed by ICANN agreements and typically requires an application, approval, and commitments about how the data will be used; ICANN's registry programme documentation outlines the framework.

The value of a zone file is not the volume so much as the structure. Each entry gives the domain name, its nameservers, and sometimes glue records — the IP addresses of nameservers that live inside the TLD itself. That is enough to track hosting relationships, identify DNS providers, and group domains by shared infrastructure, which is the foundation of nearly every filtering technique worth using.

Acquiring Zone Files: gTLDs vs. ccTLDs

Acquisition is where the difficulty concentrates, and the gap between generic and country-code TLDs is wide.

gTLD Zone Files

For generic TLDs such as .com, .org or .info, the process is standardised but bureaucratic. Registries — Verisign for .com and .net — operate zone file access programmes with an application process, usage agreements, and in some cases fees. Details are published on Verisign's zone file access page. Approval is only the start: the files update daily, arrive compressed, and have to be decompressed, parsed and indexed on a schedule. That is a standing infrastructure commitment, not a one-off download.

ccTLD Zone Files: The Harder Problem

ccTLD zone files are far harder to obtain than gTLD zone files. Many country-code registries never publish a public zone file at all. Germany's .de and France's .fr are the prominent examples, both citing registrant privacy and national policy. Because ccTLD registries are not bound by ICANN policy the way gTLD registries are, there is no centralised access programme to appeal to — each registry sets its own terms, and for a meaningful share of them the answer is simply no.

That leaves aggregated data as the only practical route to coverage for those zones. It also means per-TLD availability is uneven at every provider in this market, ours included. Before building a workflow around a specific country-code zone, check that the zone is actually in the catalogue: WebTrackly currently publishes 716 TLD zone files, with matching enriched sets under domain data. For newly registered domain work specifically, see our guide to working with newly registered domains.

Filtering the Noise: From Raw Zone File to Actionable List

A raw zone file, or a daily feed of newly registered domains derived from one, is a firehose. The challenge is not obtaining data but obtaining useful data: a large proportion of any NRD feed is parked pages and PPC spam, and without aggressive filtering, outreach built on it fails by construction.

A Filtering Methodology

• Nameserver pattern recognition. The highest-yield filter. NS records pointing at parking providers indicate a domain with no active site, and they cluster — one pattern removes many domains at once. This runs offline against a CSV that already contains NS fields, at no cost beyond processing.
• Registrar filtering. Bulk, low-cost registrations concentrate at a handful of registrars and correlate strongly with the parking clusters above, so the two filters compound rather than duplicate.
• WHOIS analysis. Anonymous registrations, generic contact addresses and privacy services are weak individual signals but useful in combination with the structural filters.
• Technology and content analysis. For a shortlist, checking which platform a site runs on adds a strong qualifying dimension. WebTrackly publishes 79 technology-based site lists covering CMS and platform detection — WordPress at 21,639,326 domains, Joomla at 607,765, among others.

The order matters. Run the free structural filters across the whole zone first, then spend network requests only on what survives. Inverting that order is the most common way to turn a cheap analysis into an expensive one.

What Makes Zone Data Harder Than It Looks

Two things reliably surprise people coming to this from a general data background.

The first is that freshness is not a nice-to-have for newly registered domain work — it is the entire premise. The reason NRDs are interesting is that they represent businesses in their setup phase, still choosing vendors and making decisions. Once that window has passed, the list is just a list of domains, and its size does not compensate. This is why WebTrackly generates each file at the point of purchase rather than distributing a pre-built archive.

The second is that the interesting volume is not confined to the legacy TLDs. Newer gTLDs such as .xyz, .online and .site carry a higher junk ratio than .com, but the absolute registration volume is high enough that a well-filtered extract still yields a meaningful list. Restricting your coverage to .com and .net is a decision to ignore a large part of the current registration landscape, not a neutral default.

Practical Takeaways

1. Prioritise freshness for NRD campaigns. If you are targeting newly launched businesses, the age of your data is the variable that governs the result. Work from a recent export.
2. Validate MX records before cold email. A domain list is only as good as its MX validation, and validation ages. Do the offline pass on the MX field in enriched zone data, then run live checks with a service such as Hunter.io or ZeroBounce immediately before sending. WebTrackly sells domain-level data only — no contact records, email addresses or phone numbers.
3. Do not write off ccTLDs, but check coverage first. The targeting opportunity in country-code space is real and the data access problem is also real. Confirm the zone you need is available before designing around it.
4. Filter structurally, then selectively. Nameserver and registrar filters across the whole file, network requests only on the survivors.
5. Segment by technology. Knowing that a domain runs WordPress, Shopify or Magento makes outreach dramatically more specific. The technology site lists exist precisely so you do not have to build detection yourself.

FAQ

What is the difference between a zone file and enriched zone data?

A zone file lists the domains under a TLD along with their nameserver records — a technical map of what exists. Enriched zone data adds per-domain attributes on top: NS, MX, IP and CMS fields, which is what makes filtering possible without running your own crawling and resolution infrastructure. WebTrackly publishes 716 packages of each, under zones and domain data.

Why are ccTLD zone files harder to get than gTLD zone files?

National regulation and registry autonomy. Many country-code registries, particularly in Europe, prioritise registrant privacy and publish no full zone file, often citing data protection law. Major gTLD registries operate under ICANN agreements that provide for zone file access under defined terms. There is no equivalent central mechanism for country-code space, so aggregated data is the practical alternative where direct access is unavailable.

How current is the data when I download it?

Each file is exported at the time of purchase rather than served from a pre-built archive, so it reflects the state of the zone at that moment. You receive a CSV inside a ZIP, available immediately after payment.

What does it cost?

Individual packages start at $3.50 as one-time purchases with no subscription. For regular use there are two plans: Pro at $29/month covering 50 packages and 10 datasets with 30K API calls, and Enterprise at $99/month covering 200 packages and 50 datasets with 300K API calls. Cross-zone collections — including the full all-domains dataset at 272,614,863 rows — are listed under datasets. See also our companion guide on DNS records in zone data.