Knowledge Base

Why does my domain show a parked page or the wrong website?

A parked page or an unexpected website can mean the domain points to the wrong server, the domain uses the wrong website folder, or a placeholder file is being shown. Check the exact address, DNS destination and document root before deleting files or changing nameservers. A domain transfer alone does not move a website's files or email.

Identify the address and destination

  • Copy the full address from your browser, including www, a subdomain and https://. Check the bare domain and its www address separately. They can use different DNS records or redirects.
  • Try the same address in a private browsing window. If you see the correct site there, review our cache-clearing guide before changing the hosting setup.
  • If you recently moved the website or edited DNS, record the old and intended hosting destinations. Use the hosting details supplied for your service, or ask us to confirm the destination. Do not copy an IP address or server name from somebody else's example.
  • Follow our DNS-records guide to find the provider that currently manages the domain's records and check the affected A, AAAA or CNAME record. Changing records in a different DNS provider's panel will not change the live answer.
  • If you intend to keep the current DNS provider, update the necessary website records there. Do not change nameservers merely to fix a website record. A nameserver change can affect email and other records too. Our DNS timing guide explains why visitors can temporarily reach different destinations after a change.

Check the domain's website folder

  • Sign in to your account, find the correct hosting service in Services and choose Log in to cPanel. On a phone, choose cPanel.
  • Open Domains, find the exact domain and check its document root. That is the folder the server uses for its website files. Do not assume an additional domain uses the main site's public_html folder.
  • If two domains share the same document root, they serve the same files. Our additional-website guide explains the difference between another address for one site and a separate website. Do not move a shared folder while other domains still depend on it.
  • Open File Manager and navigate to the document root. Check whether it contains the intended website, an uploaded archive, an extra nested folder or only a placeholder page. Compare the names with your known-good website copy before changing anything.
  • If the intended site is missing, upload it to the confirmed folder or complete the website migration. Pointing a domain at this hosting does not copy its old website.

Correct the cause and check again

  • If DNS points elsewhere, change only the confirmed website records at the active DNS provider. Keep the existing email records intact. If a proxy or website-delivery service sits in front of the hosting, check its destination as well.
  • If a placeholder file is taking priority, back up the folder and have the website maintainer identify that exact file before removing or renaming it. Do not delete every file in the folder to get rid of a parked page.
  • If the correct site appears and then redirects to another domain, ask the maintainer to check the website's configured address and redirect rules. Avoid changing DNS repeatedly when the server is already receiving the request.
  • Test the bare domain, www, HTTPS and an inner page after the confirmed correction. Clear only the relevant cache after checking the underlying website, using our cache guide.
  • If the destination or shared-folder arrangement is unclear, open Support → New Ticket → Tech/Server. Include the full URL, screenshot, intended site, recent changes and the document root you found. We can help identify the mismatch before you replace content.