DNS migration checker

Moving a domain to Cloudflare, a new host or a new registrar? Most migrations that go wrong lose something small: a DKIM key, a Microsoft 365 record, a verification TXT or a forgotten subdomain. Read every record before you switch, export it as a zone file for the new provider, then run it again afterwards to see exactly what changed.

How to move DNS without breaking email

  1. A day or two before: lower the TTL on the records you'll change (the A record for the website, and MX if email is moving) to 300 seconds, so the switch takes effect quickly and can be rolled back quickly.
  2. Read and export: run the domain through this checker, download the zone file and import it at the new DNS provider. Cloudflare, Route 53 and most others accept a BIND zone file. Compare their import against this list.
  3. Check the new provider has everything before you touch the name servers: MX, SPF, every DKIM key, DMARC, Microsoft 365's autodiscover and SRV records, and the verification TXT records.
  4. Switch the name servers at the registrar. Most changes are visible within an hour, but allow up to 48 hours.
  5. Compare: run the domain through this checker again. Anything marked missing needs adding at the new provider. Then send a test email to and from the domain.

The records that usually go missing

DKIM keys. Each email service (Google Workspace, Microsoft 365, Mailchimp, SendGrid, Klaviyo) has its own selector, and they sit on names you would never guess, like s1._domainkey. Lose one and that service's email starts failing DMARC.

Verification TXT records. Google, Microsoft, Meta, Apple and dozens of SaaS tools prove domain ownership with a TXT record. Remove one and nothing breaks today, but the next time the service re-checks, the domain becomes unverified.

Microsoft 365 extras. Autodiscover, the SRV records for Teams and the enterprise enrolment CNAMEs are easy to miss and annoying to track down later.

Subdomains. The shop on shop., the help centre on help., a tracking domain on links.. They're often set up by someone else and nobody remembers them until they stop working.

Questions agencies ask

You can't list a zone from outside (DNS doesn't allow it, for good reasons), so the next best thing is asking for every name that's likely to exist. This checker asks for the apex records, around 80 common subdomains, the DKIM selectors used by the main email services, DMARC, MTA-STS and the SRV records Microsoft 365 needs. If the current provider offers a zone export, use both.

FOR AGENCIES

Moving hosts, DNS or a whole platform?

I handle the technical side of migrations for agencies: DNS and email moves, hosting changes, WordPress and WooCommerce transfers and Laravel deployments, with a plan to roll back if anything goes wrong.

  • White-label, under your brand, or alongside your team
  • Laravel, WordPress, WooCommerce, integrations and tracking
  • Inherited and half-finished sites taken over and stabilised
  • UK based, straight to the developer, no account managers

Related free tools