Why does my domain point to the wrong website or work only with www?

Business Tech & Tools

Why does my domain point to the wrong website or work only with www?

The short answer

The bare domain (example.com) and the www hostname (www.example.com) are two separate DNS names. Each needs a correct destination or redirect, and the web host needs to recognize both. A domain can therefore work with www, fail without it, or reach an old website even when one record looks correct.

Check the problem as a four-part chain: authoritative DNS, host assignment, HTTPS certificate, and redirect.

Test all four versions first

Open a private browser window and record what happens with:

Address Result to record
http://example.com Error, old site, new site, or redirect
https://example.com Certificate result and destination
http://www.example.com Error, old site, new site, or redirect
https://www.example.com Certificate result and destination

Do not write “the domain is broken.” Write the exact hostname, protocol, result, and final URL. That distinction points toward the responsible layer.

Check DNS for the bare domain and www separately

The root may use an A or AAAA record while www uses a CNAME. Some platforms use different arrangements. Compare both records with the host’s current instructions.

Common problems include:

  • the root still points to an old server.
  • www points correctly but the root has no record.
  • a duplicate record sends some requests elsewhere.
  • the record was edited in a non-authoritative DNS account.
  • a proxy setting changes how the destination is reached.
  • the hostname was entered in the wrong format.

Use authoritative DNS results, not only what your laptop remembers. Cloudflare’s DNS documentation includes troubleshooting for unexpected records, stale responses, proxy status, and records with the same name. See Cloudflare DNS documentation.

Confirm the domain inside the web host

Correct DNS only delivers the request to a server. The server still needs to know which site belongs to that hostname.

In the hosting or website-platform account, check that:

  • the exact bare domain is attached to the intended site.
  • www is attached or redirected as the platform requires.
  • the intended site is published.
  • an old temporary or staging site is not set as primary.
  • the account is not displaying a default parking or setup page.

If several sites share one hosting account, a missing domain assignment can cause the server’s default site to appear. That can look like DNS pointing to the wrong place even though the IP address is technically correct.

Choose one preferred version

Decide whether visitors should end at https://example.com or https://www.example.com. Either can work. What matters is consistency.

Set permanent redirects from the other versions to the preferred one, preserve the rest of the path, and use the preferred version in internal links, navigation, canonical tags, analytics settings, and Search Console.

For example, a request for http://www.example.com/services should reach the preferred secure version of /services, not dump the visitor on the homepage. Google explains that permanent server-side redirects signal that the destination should be treated as canonical. See Google’s redirect guidance.

Check the certificate after DNS works

The HTTPS certificate must cover every hostname a visitor reaches before the redirect. If https://www.example.com has no valid certificate, the browser may warn the visitor before it can follow a redirect to the bare domain.

Wait until both hostnames resolve to the intended platform, then use the platform’s certificate process. Test again from a private window and a phone on mobile data.

Use this diagnosis map

What you observe Most likely place to investigate
Only one hostname has the correct DNS answer Missing or old DNS record
Both hostnames reach the correct IP but one shows a default site Host domain assignment
HTTP works but HTTPS warns Certificate or HTTPS configuration
Both open but stay as separate versions Redirect and preferred-domain setup
Some networks see the old site DNS caching or proxy cache
Every version redirects to an unrelated page Host redirect rule, plugin, or compromised configuration

If the destination is unfamiliar or suspicious, stop entering passwords and contact the registrar and host through addresses you already trust. Do not log in through a link shown on the unexpected page.

Sources and further reading

A free next step

You don't have to build this alone

Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.

Join Our Community Free

Related Questions

Related WAHMN resource

If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.

← All questions