10-Point Checklist After Moving Your Website to a New Host

When you are moving your website to a new host, completing the migration is just half the job. There are plenty of things you need to check afterthe move is done. These can range from checking DNS propagation to reissuing SSL certificates.

Checking for these issues is important because any problems can lead to a broken website, poor search rankings, and bad email delivery.

So, before you cancel your old hosting plan, take some time to check your new setup. This 10-point checklist will help you find common problems and make sure your website is ready to run on its new host.


1.  Confirm the Site Is Served From the New Host

First, check that your new server is actually loading the site. You have to check this because sometimes your browser may load an old cached version of your site without even checking the new server. This site will still be using the old hosting.

To check that the new server is loading the site, do the following:

  • Clear your browser’s cache
  • Do a domain IP lookup with your website domain
  • Compare the returned IP address with the one provided by your hosting
  • Do an IP WHOIS lookup on the returned IP as well.

If everything is working, then the returned IP should be the same as the one provided by your hosting, and the WHOIS results should show your hosting’s name as the organization controlling the IP address.

2.  Verify Your A and AAAA Records

Verify your A and AAAA records. A records deal with IPv4, while AAAA records deal with IPv6.  When you have moved hosts, your domain’s A and AAAA records should only list the IP address of the new hosting.

Use an A record Lookup and AAAA record lookup tool to check these records for your domain and ensure no old IPs are still listed. If an old address remains, visitors may still reach the wrong server, and you don’t want that to happen.


3.  Check DNS Propagation

When you change hosts, obviously, you change a lot of DNS records for the domain, most notably the A and AAAA records, which map your domain to the new IP.

These DNS changes, however, do not update all over the worldwide DNS instantly. It typically takes 24 to 72 hours for the entirety of the public DNS to be updated with your domain’s new records.

This delay is called DNS propagation delay. It occurs because many DNS providers don’t update their records until their TTL (time to live) expires. If the records have a short TTL, they will expire faster, and DNS propagation will be quicker, and vice versa.

You can monitor the propagation status of your updated records with a DNS propagation checker.

Just know that until propagation is complete, some regions will still see your old website because of outdated records. You can’t do anything about it except wait and monitor it.


4.  Review CNAME and Subdomain Records

CNAME records are one of the most important records you must update after switching to a new host.

These records are used to manage subdomains by pointing them toward the main domain. Normally, you don’t need to update them after changing hosts; however, you do in the following situations.

  • When Your New Host Uses a Different Target

If your new host gives you a new hostname for your website, you must update the CNAME to point to it.

  • When You Switch Hosting Providers

Some hosts use their own hostnames to route website traffic. If your new host uses a different one, update the CNAME record.

  • When You Change Your CDN Provider

A CDN may use a CNAME record to route traffic. When you switch CDN providers, you may need to point it to the new provider's hostname.

  • When You Move a Subdomain

If you move a subdomain, such as blog.example.com, to a new host, update its CNAME if the new host gives you a different target.

  • When Your New Host Needs Domain Verification

Some hosting providers ask you to add a CNAME record to verify your domain. You must add or update this record to complete the process.

  • When You Change Website Platforms

Moving to a new website builder or platform may require a new CNAME target. Follow the DNS values given by your new provider.

Check whether these apply to you and act accordingly.


5.  Test Email Delivery and MX Records

Host migrations can definitely affect your email setup as well. One of the most important records you must check is the MX record. It is responsible for designating the server that receives email for your domain.

If your hosting provider provided that server, then the MX record must be updated to point toward the new server. You need to verify that it's correct and not missing any values. You can do that with an MX record lookup.

Once verified, send a test email to a different device on a different network and then reply to it. If the email and the reply reach their destinations easily, then you are good.

Do not skip this step. Email problems can go unnoticed until a customer or team member reports them.


6.  Check SPF, DKIM, and DMARC Records

SPF, DKIM, and DMARC help protect your domain from email spoofing. They also help email providers decide whether messages from your domain are safe.

These settings are stored in DNS, so you should check them after a move.

Use a TXT record lookup to confirm that the records are still in place. You can also use SPF and DKIM checkers to find errors.

If your new host handles outgoing email, make sure its sending servers are included in your SPF record. Check that your DKIM keys and DMARC policy are also correct.


7.  Verify the SSL Certificate and HTTPS

Your website needs a valid SSL certificate to use HTTPS. A migration may leave you with an expired certificate, a missing certificate, or one that does not cover all your domains.

Use an SSL checker to review the certificate. Make sure it covers your main domain and any required subdomains. Also, check that the full certificate chain is installed.

Open your website over HTTPS and look for security warnings. Check for mixed content, such as images or scripts still loading over HTTP.

Finally, make sure visitors who open an HTTP link are sent to the HTTPS version.


8.  Test Site Functionality and Redirects

A website may look fine on the home page but still have problems on other pages.

Click through your main pages and test important features. Check contact forms, user logins, search boxes, and checkout pages if your site has them.

Look for broken links, missing images, and 404 errors. Also, test old URLs to make sure they redirect to the correct pages on the new site.

If you changed your URL structure during the move, review your redirect rules carefully. Broken redirects can hurt both visitors and search engines.


9.   Check the New IP's Blacklist Status

Your new hosting provider may assign you a shared or recycled IP address. This address may already have a poor reputation because of past activity.

A flagged IP can cause email delivery problems. Some security systems may also block traffic from addresses with a poor reputation.

Use an IP and domain blacklist checker to see whether your new server's IP or domain appears on known blacklists.

If you find a listing, check which blacklist reported it and why. Contact your hosting provider if the issue is linked to the server's IP address.


10. Monitor Performance and Uptime Before Retiring the Old Host

Do not cancel your old hosting plan as soon as the new website goes live. Give the new server a few days of testing first.

Watch your website's loading speed and uptime. Check important pages during busy hours and see how they perform.

You can also use ping and traceroute tools to spot connection delays or routing problems between your device and the server.

Once everything looks stable, take a fresh backup of your website and database. Keep a copy somewhere outside your hosting account.


Common Mistakes to Avoid

One common mistake is cancelling the old host too early. This can cause problems if DNS changes have not reached all visitors or if you need to recover an old file. Another mistake is checking only the main domain and forgetting subdomains, email records, or redirects. Take time to review every part of your setup before closing the old account.

Conclusion

Moving to a new host involves more than copying your website files. You also need to check DNS records, email settings, SSL, IP reputation, and site performance. Most of these checks take only a few minutes with the right tools. Work through each item on this list and fix any issues you find. Once everything works as expected, you can safely retire your old hosting account.

Post comment