Before and after migration

Make your nextmove with clarity.

Save the current records before a change. Check the new targets after the switch.

Website migrationPublic records · Query and inspect

BEFORE & AFTER

Review current DNS

DNS / LIVE

Quick typesNo https:// or path

Read the current answers before comparing them with your migration targets.

Name	Type	Data	TTL / sec

Resolver: Google Public DNS

01ACheck the new address

02AAAARemember IPv6

03MXPreserve mail routing

MIGRATION NOTES

Two checklists for your next move

Migration guide ↗

What to save before a website migration

Keep the previous configuration traceable and leave useful evidence for a rollback.

Read the guide →02

After the switch, check more than one A record

IPv6, aliases and email can still point to the old environment.

Read the guide →

Migration questions

Which names should I save before moving?

The apex, www, API and email entry points can all use different names. Query each one from your own service inventory instead of saving only the apex. This tool does not discover all of your service subdomains.

Does “All types” include every subdomain?

No. It queries common types for the name you enter. Subdomains, service records and email authentication records require their own complete names.

Why can this differ from my DNS control panel?

These answers come from a recursive resolver and can reflect its cache, proxy settings or provider-specific features. Compare TTL and the actual configuration; a single lookup is not a global propagation test.