Product guide
Zone Analyzer Guide
Zone Analyzer parses DNS zone exports locally and presents them in a structured grid for inspection, filtering, and lightweight validation. It is built for fast review of large record sets without requiring you to upload the zone elsewhere first.
The short answer
Use Zone Analyzer when you already have a zone export and want to sort, filter, inspect, and verify records locally in the browser.
Start here for internal DNS hygiene reviews, large zone audits, duplicate hunting, and quick web-facing record verification before or after a change window.
Upload and parsing workflow
The tool accepts drag-and-drop uploads or toolbar-based file selection. Supported inputs include DNS exports from BlueCat, Infoblox, BIND, NSD, Knot, PowerDNS, and other BIND-style formats.
- Loads a local export file with no separate cloud upload flow described in the product help.
- Parses the zone into a grid so records can be inspected row by row.
- Keeps the landing state focused on the file import action before analysis begins.
Core features
| Feature | What it does | Why it matters |
|---|---|---|
| Filters | Builds custom rules by zone, type, hostname, or data | Lets you narrow large exports into focused review slices. |
| Quick pills | Toggles SOA and NS noise, PTR records, or web-facing records | Speeds up common triage patterns with one click. |
| Export CSV | Downloads the currently filtered records | Makes it easier to share only the rows that matter. |
| Visual verification | Opens screenshots only for explicitly checked A, AAAA, and CNAME rows | Prevents accidentally sending huge batches for web preview. |
How filtering is meant to be used
The filtering model is designed for iterative narrowing rather than a single static query. You can stack custom rules, use quick pills for common record classes, then export only the current view once you have isolated the rows that need follow-up.
This is especially useful when a single zone contains many operationally unrelated records and you only want the subset tied to web, mail, reverse DNS, or one hostname family.
Visual verification guard rails
Visual verification is intentionally limited. It opens screenshots of web pages only for specifically checked A, AAAA, and CNAME rows. That constraint exists to prevent the tool from accidentally submitting very large batches and to keep the action tied to clearly chosen web-facing records.
If you need preview or redirect checks, first narrow the grid and select only the rows you actually want to verify. Broad selection defeats the safety intent of the workflow.
When to use Zone Analyzer instead of Domain Explorer
Choose Zone Analyzer when you have local zone data and want direct control over filtering and export. Choose Domain Explorer when you want a live public-DNS scan with scoring and findings rather than a view of a supplied export file.
FAQ
Does Zone Analyzer require a live DNS lookup?
No. It is designed around parsing a provided zone export rather than fetching public DNS data for a domain.
Why are preview actions limited to selected A, AAAA, and CNAME rows?
Because those rows are the most likely to map to web-facing destinations, and requiring explicit selection prevents oversized accidental submissions.
Can I export just the filtered subset?
Yes. The CSV export uses the records currently visible after filtering, not the full original dataset by default.
Where can I review parser and pipeline internals?
See the Zone Analyzer technical details reference for the ingest, normalization, and analysis pipeline.