How to Check a Website Has Moved to Its New Host After a Migration

To confirm a migration, check that each domain's records and response now name the new host. Paste the domains into the website host checker. It reads each one's CNAME and A records, the NS and MX records, and the headers of one request to the home page, then names the platform with the evidence. Compare that against the host you moved to.

Step 1: write down what you expect

For each site, note the new platform and the record you changed. If you moved to Vercel, expect the A record 76.76.21.21 or a CNAME to cname.vercel-dns.com, per Vercel's docs, and server: Vercel in the response. Every platform publishes its own values, so use the new host's documentation.

Step 2: run the check

Paste the domains, one per line. Up to 100 a run without an account and 500 after a free Google sign-in. Results come with the record or header behind each call.

Step 3: compare each row to your list

Row shows	What it means	What to do
The new platform	Records and response match	Done for that site
The old platform	DNS or the cache has not caught up, or the change was not saved	Check the record at the DNS host, then wait for the TTL
A CDN such as Cloudflare	The origin is hidden behind a proxy	Look for a platform header, or test the origin another way
No platform recognised	Nothing matched	Check by hand at the host's dashboard

If you are unsure where the record lives, find where to edit a domain's DNS shows the DNS host from the NS records. Records edited anywhere else do nothing.

Why the old host can still show

DNS answers are cached. A resolver can serve the old record for up to the record's TTL after you change it, so a check straight after a change can show the old host even though the change is correct. Lower the TTL before a planned move and wait out the old one afterwards. For email moves, planning a DNS TTL change before an MX move applies the same idea.

Do not forget the email provider

Moving a site does not move its mail. The same row shows the email provider from the MX records. If you changed MX on purpose, confirm it. If you did not, it should not have changed. A common slip is deleting records at the old host that email still needed.

After the DNS check: redirects and status

Records can be right while pages are broken. Run the list through the bulk website status checker, and see auditing redirects after a site migration.

What this check cannot do

• It reads one request to the home page; other pages and paths are not checked.
• Cached DNS can show old records after a change.
• A CDN can hide which host is behind it.
• It does not test redirects, SSL or page content.

If contact addresses came with the move

Correct DNS and a good domain get mail to the door; the address still has to exist. Upload your list on the verify page: the first 100 email checks are free with a Google sign-in, no card. Each address comes back valid, risky or invalid with a reason, and nothing is sent to anyone on the list. For larger or recurring lists, see bulk email verification, list cleaning and pricing.

Check the move now

Paste your domains into the website host checker.