Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WordPress Domain Not Working: Causes and How to Fix It

WordPress Domain Not Working: Causes and How to Fix It

Short answer

A WordPress domain usually fails because its DNS does not point to your host, recent changes have not spread yet, the domain expired, it was never added in your hosting account, or WordPress is set to another address. Check DNS first, then hosting, settings and SSL.

Key takeaways

  • Most domain problems come from DNS records or nameservers that do not point to your host.
  • DNS changes can take time to show everywhere.
  • Check expiry and status codes such as clientHold with an ICANN lookup.
  • WordPress Address and Site Address must match the domain you use.
  • Both www and non-www need DNS records and SSL coverage.

Why is my WordPress domain not working?

A WordPress domain usually stops working because its DNS does not point to your host, the change has not spread yet, the domain expired, the hosting account does not know about it, or WordPress is set to a different address.

The domain and the website are two separate things. The domain is an address, and DNS records tell browsers which server holds the site.

If any link in that chain breaks, the browser cannot reach WordPress. The error you see tells you where to look.

What you seeLikely causeFirst fix
This site can't be reached or DNS_PROBE_FINISHED_NXDOMAINDNS missing or not pointedCheck nameservers and A record
Registrar parking pageDomain not pointed to hostUpdate DNS at the registrar
Host's default or no website here pageDomain not added in hostingAdd the domain in your host panel
Redirects to an old or temporary URLWordPress address settingsFix Site Address and WordPress Address
Security warning or SSL errorNo certificate for the domainIssue SSL for the domain
Works on one network, not anotherDNS still propagatingWait, then flush DNS cache

Is the domain pointing to your hosting?

Check that the domain uses your host's nameservers or has an A record pointing to your server's IP address, because a domain that points elsewhere will never load your WordPress site.

There are two common ways to connect a domain:

  • Nameservers: you set the domain's nameservers to your host's, and the host manages all DNS records.
  • A record: you keep DNS at the registrar or a service like Cloudflare and point an A record to your server's IP.

Log in to your registrar and compare the settings with what your host gives you. A single wrong digit in an IP address is enough to break everything.

Online tools such as whatsmydns.net show what the domain resolves to around the world. If the IP shown is not your host's, DNS is the problem.

Our guide on pointing a domain to WordPress hosting walks through both methods.

Are DNS changes still spreading?

If you changed nameservers or records recently, the domain may work for some people and not others for a while, because DNS caches update on their own schedule.

This is called DNS propagation. Record changes often show within an hour, while nameserver changes can take longer.

You can speed up your own view, not the whole internet's:

Our explainer on how long DNS propagation takes explains what controls the delay.

If you see DNS_PROBE_FINISHED_NXDOMAIN, the browser could not find any record for the domain. The NXDOMAIN fix guide covers that error in depth.

Has the domain expired or been suspended?

An expired, unpaid or suspended domain stops resolving, often showing a registrar parking page, so check its status and expiry date before changing anything else.

Domains renew yearly or on a set term. If the payment card expired, the renewal may have failed quietly.

Look up the domain in the ICANN registration data lookup. It shows the expiry date and status codes.

Status codes like clientHold or serverHold mean the domain is suspended. That often happens after a failed renewal or an unverified contact email.

Renew the domain or verify the email through your registrar. Service usually returns soon after, once DNS updates.

Has the domain been added in your hosting account?

Even with correct DNS, the server must know which folder to serve for your domain, so the domain needs to be added to your hosting account as the main, addon or parked domain.

If you skip this step, the server receives the request but has no site to match. You may see the host's default page or a generic error.

In cPanel, check the Domains section. On managed WordPress hosts, look for a domains tab in the site's settings.

Make sure the domain points to the folder where WordPress is installed. Our guide on what the WordPress root directory is explains how to find that folder.

Are the WordPress address settings correct?

If the site loads but jumps to another address, check Settings > General, where WordPress Address and Site Address must both match the domain you want to use.

WordPress stores its address in the database. After a domain change, it keeps sending visitors to the old one until you update it.

The General Settings documentation explains both fields.

If you cannot reach the dashboard, set the address in wp-config.php instead:

define( 'WP_HOME', 'https://example.com' );
define( 'WP_SITEURL', 'https://example.com' );

Replace example.com with your domain. Our guide on changing the domain of a WordPress site covers the full process, including updating old links in the database.

If your site sends visitors somewhere unexpected, see our guide on a site redirecting to another site.

Is SSL set up for the domain?

When the domain loads with a security warning or an SSL error, the certificate is missing, expired or issued for a different name, so issue a certificate that covers the exact domain.

Many hosts issue free certificates from Let's Encrypt automatically. That only works once DNS points to the host.

If you connected the domain before DNS finished, the automatic certificate may have failed. Ask your host to reissue it, or run the SSL tool in your control panel again.

Make sure the certificate covers both www and non-www versions. A certificate for only one will warn visitors on the other.

Our guide on installing an SSL certificate covers the setup steps for most hosts.

If the browser shows a protocol error rather than a warning, the guide to fixing ERR_SSL_PROTOCOL_ERROR explains the usual causes.

Does only www or only non-www work?

If one version works and the other fails, a DNS record is missing for one of them, usually the www CNAME or the root A record.

Both versions need records:

  • The root domain, such as example.com, needs an A record
  • The www version usually needs a CNAME pointing to the root domain or host

Then pick one as the main address in WordPress settings. The other should redirect to it.

If the two versions bounce visitors back and forth, you will see a redirect loop. Our too many redirects guide shows how to break it.

Is Cloudflare or another proxy causing the problem?

If your DNS runs through Cloudflare, wrong proxy settings, SSL modes or a paused zone can stop the domain from loading even when records look correct.

Check that your records point to the right server IP and that the zone is active. Cloudflare's DNS documentation explains proxied and DNS-only records.

A common mistake is the Flexible SSL mode with WordPress forcing HTTPS. That combination creates a loop.

Our guide to Cloudflare SSL settings for WordPress explains which mode to use.

What if I use a domain with WordPress.com?

On WordPress.com, a domain bought elsewhere must be connected through WordPress.com's domain settings, either by changing nameservers or adding the records it lists.

The steps differ from self-hosted WordPress. WordPress.com shows the exact records to add on its domain screen.

If the domain still does not connect after a day, check that the nameservers or records match exactly. Our guide on adding your domain to WordPress covers both WordPress.com and self-hosted setups.

When should I contact my host or registrar?

Contact support when DNS points correctly, the domain is active and added in hosting, yet the site still fails, because the problem may be a server setting you cannot see.

Before you contact them, collect:

  • The domain name and what you see when you visit it
  • A screenshot of your DNS records or nameservers
  • When you last changed anything
  • Results from a DNS lookup tool

Your registrar handles domain status and nameservers. Your host handles the server, the domain's folder and SSL. Contact the one that matches the problem you found.

Frequently asked questions

How long does it take for a new domain to work with WordPress?

Record changes often work within an hour, while nameserver changes can take longer before everyone sees them. If the domain still fails after a full day, check that the records match what your host gave you.

Why does my domain show a parking page instead of my site?

The domain still points to the registrar's default servers. Update the nameservers to your host's, or add an A record with your server's IP address, then wait for the change to spread.

Why does my WordPress site redirect to the old domain?

WordPress still has the old address saved in its settings or database. Update the WordPress Address and Site Address fields, or set WP_HOME and WP_SITEURL in wp-config.php, then replace old links in the database.

Can an expired SSL certificate make my domain stop working?

The domain still resolves, but browsers show a security warning and many visitors leave. Renew or reissue the certificate through your host, and make sure it covers both the www and non-www versions of your domain.

My domain works on mobile data but not on Wi-Fi. Why?

Your Wi-Fi network or computer is still using a cached DNS answer. Restart the router, flush your computer's DNS cache or switch to a public DNS resolver, and the domain should load once the old record expires.

Sources

  1. General Settings Screen WordPress.org
  2. Registration Data Lookup ICANN
  3. Flush Cache Google Public DNS
  4. DNS documentation Cloudflare
  5. Let's Encrypt Internet Security Research Group

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.