If you’re not seeing the site on the new server, it could be because your browser is serving a cached version of the page.
In that case, you can: If you’re uncertain whether you are seeing the new site or the old, you can confirm the IP address of the site you’re viewing using a browser add-on.
Now that you can see the site on its new server, you must thoroughly test it to determine whether everything works as expected.
It is common to see some issues and error messages when testing a migrated site.
You may have more or fewer such local entries in your hosts file; you don’t need to worry about them other than to note their presence.
Any custom entries will go at the bottom of the file, and in this case you can see that I have added one custom entry to the end of the file already: My custom entry specifies that any request made from my computer (via web browser or SSH, email, or FTP client) for or be directed to the IP address I’ve specified: 18.104.22.168.
The hosts file is used to map domain names to IP addresses, and can be used as an alternative to DNS.
That makes it an essential tool when migrating your website.