Capture both states.
Paste BIND-style zone text or import common CSV/spreadsheet DNS exports. Parsing and comparison stay local to the browser.
Free DNS migration tool · browser-only
CHANGE DNS.
KEEP THE BUSINESS WORKING.
Compare the DNS you have with the DNS you plan to publish. Catch web, email, certificate and DNSSEC risks before the switch, then leave with a reviewed cutover order and rollback evidence.
Compare the zonesAdds · removals · routing changes · TTL changes
Catch outage risksMail · HTTPS · CAA · SPF · critical hostnames
Control the switchCutover order · rollback evidence · audit receipt
DNS Migration Cutover Planner + Zone Diff
COMPARE THE ZONES.
CONTROL THE CUTOVER.
Paste or upload the current DNS zone and the proposed target. The tool compares record sets, finds changes that can break web traffic or email, and forces risky differences into explicit review before launch exports unlock.
01 · Current production DNSWhat the world relies on now
02 · Proposed target DNSWhat you plan to publish
How it works
COMPARE BEFORE YOU
SWITCH NAMESERVERS.
A propagation checker tells you what DNS is live after a change. This tool solves the earlier problem: whether the target zone preserves the records the business still needs, and whether the switch has a controlled rollback.
Separate change from noise.
See record-set additions, removals, target changes and TTL-only changes across A, AAAA, CNAME, MX, TXT, NS, CAA, HTTPS, SVCB and other common types.
Protect web, mail and certificates.
Missing web hosts, changed mail routing, dropped SPF/DKIM/DMARC records, unsupported record types, ambiguous zone context, nameserver/DNSSEC obligations and risky old TTLs are surfaced before cutover.
Leave with rollback.
Explicitly confirm intentional risks, export the reviewed target, keep the current zone as rollback evidence, and follow the generated pre-cutover, switch and post-cutover order.
!
This does not replace live DNS, HTTPS and application testing.
Provider-specific records, ALIAS/ANAME behaviour, split-horizon DNS, registrar delegation, DNSSEC parent state, certificate automation and hidden application dependencies can sit outside a simple zone diff. Use this as migration evidence, then validate public DNS and real customer journeys after the switch.
FAQ
BEFORE YOU CHANGE
THE NAMESERVERS.
DNS changes can affect much more than the website. The tool is deliberately conservative around mail, certificates and records that disappear between zones.
Do my zone files leave the browser?
No. Parsing, record comparison, risk checks and exports happen locally. The tool does not send the imported DNS zone to ZappFlow or an AI model.
Is this the same as checking DNS propagation?
No. Propagation checkers query public resolvers after a DNS change. This tool compares the current and proposed configuration so you can catch risky differences and prepare rollback before the change goes live.
Why does an MX or mail TXT change require confirmation?
Because a website migration often should not move email. A changed MX, SPF, DKIM or DMARC record can be completely intentional, but it should never disappear as an unnoticed side effect of copying a DNS zone to a new provider.
Can I use the exported target zone as a guaranteed provider import?
No. The export is normalized BIND-style evidence. DNS providers differ in how they represent apex aliases, proxy/CDN flags, routing policies and proprietary record types. Review provider-specific settings before applying production changes.