Why Does My Domain Show the Wrong Website?
Your domain loads, but it is not your site. A parking page, a default server page, an old version, or in the worst case somebody else’s content entirely. Each cause looks the same in a browser and each has a different fix.
September 22, 20266 min readDNS · Troubleshooting · Hosting
The short answer. If your domain loads something that is not your site, DNS is almost certainly working. The name resolved and something answered. The question is what, and the answer is usually a server that does not know this hostname belongs to you, a cached old address, or a parking page. In one case it is somebody else's content on purpose, and that one is urgent.
First, work out what you are looking at
The page itself tells you a great deal.
| What you see | Almost certainly |
|---|---|
| "This domain is parked" or registrar branding | Domain not pointed at hosting yet |
| A hosting company's welcome or default page | Server does not recognise this hostname |
| An old version of your own site | Cached DNS or a stale CDN |
| A different customer's website | Shared hosting misconfiguration |
| An unrelated site you have no connection to | Possible takeover, see below |
| A "claim this domain" page from a cloud service | Dangling DNS record, act now |
Case 1: A parking page
The most common and least alarming. The domain is registered but its DNS still points at the registrar's default parking service, because nobody ever changed it, or it reverted.
Fix: point the nameservers at your DNS provider, or replace the A record with your server's address.
If you recently transferred the domain, note that transfers sometimes reset DNS to the new registrar's defaults. Check the records after every transfer.
Case 2: The server does not know this hostname
Most web servers host many sites on one IP address and choose which to serve by the hostname in the request. If your domain is not in that configuration, you get whatever the server treats as its default.
So the DNS is correct, the server is reached, and the server answers with something else because it does not recognise the name.
Fix: add the domain to the site's configuration at your host. On managed hosting this is usually an "add domain" or "domain aliases" screen. On a server you control it is a virtual host or server block.
A useful test: if the site loads correctly at your host's temporary URL but not at your domain, this is almost always the cause.
Case 3: You are seeing a cached old address
You moved hosts. The new server is correct. You are still being sent to the old one.
Fix: wait, or verify. Record changes clear within your TTL, usually minutes. Nameserver changes are governed by a 48 hour TTL at the registry that you do not control, so some visitors can reach the old host for up to two days. We covered why in How Long DNS Propagation Actually Takes.
Important: keep the old site running during a nameserver migration. If the old host still serves the correct site, nobody notices the overlap. If you cancel it immediately, some users get the wrong thing or nothing for two days.
Case 4: A CDN or proxy in front
If your domain runs through a CDN or reverse proxy, the origin it points at may be wrong or stale. The CDN answers instantly with whatever it believes, so the browser shows a confidently wrong result.
Fix: check the origin configuration, then purge the cache. Purging without fixing the origin re-caches the same wrong content.
Case 5: You bought a domain that used to be something else
If you registered a previously used domain and see traces of the old site, you are probably seeing caches, either yours, an intermediary's, or search engines still holding old pages.
This is not a fault and it clears. What does not clear by itself is the old domain's reputation and backlink history, which is a separate consideration we covered in Buying Expired Domains for SEO.
Case 6: Somebody else's content, on purpose
Take this one seriously.
If a subdomain of your domain is serving content you did not put there, especially from a cloud service you once used, you may have a subdomain takeover. A DNS record still points at a service you decommissioned, someone claimed that service name, and they now control a hostname under your domain, complete with a valid certificate.
Signs: the affected name is a subdomain rather than the main domain, it points at a third-party platform, and the content is unrelated or a generic "claim this project" page.
Fix immediately: delete the DNS record. That ends it at once. Then check what trusted that hostname, because OAuth redirect URIs, CORS allowlists and cookie scopes often trust entire domains. Full detail in What Is a Subdomain Takeover.
If the main domain itself is serving a stranger's site and the nameservers or registrar have changed, stop troubleshooting and treat it as a hijack. See Transfer Lock Removed.
The diagnostic order
1. Check what the registry says. Our checker shows the live nameservers and registrar. If those are not yours, nothing downstream matters and you may have a security problem rather than a configuration one.
2. Check where the name resolves. Does the A record point at your server's current IP? Hosts change IPs.
3. Test the IP directly. If the IP serves the right site when you bypass DNS, the problem is hostname configuration. If it serves the wrong site directly too, the problem is at the host.
4. Test with and without www. They are separate records and are frequently configured differently.
5. Try a browser you have never used for this domain, or a private window. It removes your own cache from the picture, which is the single most common source of confusion.
Common questions
Why does my domain show a parking page?
Its DNS still points at the registrar's default parking service. Update the nameservers or the A record to point at your hosting. Transfers sometimes reset this, so re-check after moving registrars.
Why does my domain show someone else's website?
Usually shared hosting where the server does not recognise your hostname and falls back to a default site. If it is a subdomain pointing at a third-party service, suspect a subdomain takeover and delete the record immediately.
Why do I see the old site after moving hosts?
Cached DNS. Record changes clear within your TTL, but nameserver changes can take up to 48 hours because of the registry's delegation TTL. Keep the old host running until the overlap has passed.
My site works at the hosting URL but not my domain, why?
The domain is not attached to the site in your host's configuration. The DNS is reaching the server correctly; the server just does not associate that hostname with your site.
How do I know if my domain was hijacked?
Check the registry record for the current registrar and nameservers. If either changed and nobody on your team did it, treat it as a security incident rather than a configuration problem.
Does clearing my browser cache fix this?
Only if the problem was your own cache. It does nothing for DNS caching elsewhere or for server configuration. Testing in a private window is a faster way to rule your own browser out.
Put the research to work.
Check your shortlist across the extensions that matter, then save the strongest names to a project.
Check a domain