Why compare before you switch
Moving a domain to a new DNS provider comes down to one change at your registrar: replacing the list of nameservers. The moment you save it, resolvers start asking the new servers instead of the old ones. Anything the new provider doesn't have yet stops working for the people whose resolvers switched first: a website, mail delivery, a verification record for a service you rely on.
Most providers offer to import your records, and most imports miss something. TXT records for mail and domain verification, service records for calendars and phones, records on subdomains and anything behind a wildcard are the usual gaps. This checker finds them before your visitors do.
How the check works
We read the current delegation from your registry's own servers, so we know which nameservers are live today. The current servers are those minus the new ones you entered; we ask each of them for the zone's serial and compare against the one with the newest copy.
Then we ask the current server and every new server the same questions. The list of names covers the root of your domain and the names most domains use (www, mail, autodiscover, the mail policy names such as _dmarc and _mta-sts, DKIM selectors for common mail providers, and service records for mail, calendars and chat). We also follow what your records point to: CNAME, MX and SRV targets inside your zone, and the domains named in your SPF record. Add any other names you use in the extra names box. The check covers up to 150 names.
For each name and record type we compare the values and the TTL. A server that doesn't answer with authority counts as unknown, never as missing, so a flaky server can't make records look absent.
If your registry has a DS record for the domain, we also fetch the new servers' DNSSEC keys and check that one of them matches the DS record and signs the zone. Keys belong to each provider, so this is the step that most often breaks a move.
Reading the result
The banner says whether you're ready. Ready means nothing we found would break when you switch: no record is missing, every new nameserver answers for your zone, and DNSSEC would keep working.
The comparison table lists problems first:
- Missing: the record exists now and the new servers don't have it. Add it before you switch.
- Different: both have it, with different values. Check which one is right.
- Couldn't compare: one side didn't give an authoritative answer. Run the check again.
- Only at the new provider: fine if you added it on purpose.
- Different TTL: same values, different cache time. Nothing breaks.
Each finding links to a step-by-step guide when there is something to fix.
A safe switch, step by step
- Set up every record at the new provider and run this check until it says ready.
- A day before the move, lower your records' TTLs to 300 seconds at the current provider, so changes spread quickly.
- If DNSSEC is on, deal with the DS record first, as the check explains.
- Change the nameservers at your registrar.
- Keep the old provider's zone running for at least the parent's NS TTL, often two days, then run the DNSSEC and nameserver check.
What we don't do
We don't try zone transfers. They would show us your whole zone, but they would show it to anyone who asks, so we leave them out. We only query nameserver addresses on the public internet, and queries to each registry server are rate limited.