You have set everything up, you type your domain, and… nothing. A blank page, an error, or the old site instead of the new one. It is frustrating, but the reassuring news is that a domain not connecting to a website almost always comes down to one of a short list of common, fixable causes — and most of the time it is not even a real problem, just DNS changes still spreading.

This guide gives you a clear troubleshooting checklist, ordered from the most likely cause to the least, so you can diagnose why your domain is not connecting and fix it methodically. You will learn what to check first, how to test each possibility, and when the issue is simply a matter of waiting versus a setting that needs correcting.

Start here: is it propagation?

The single most common reason a domain is not connecting is DNS propagation — the delay while your recent DNS changes spread across the internet. DNS changes can take anywhere from a few hours up to 48 hours to update globally, so if you just pointed your domain or edited records, the most likely explanation is simply that the change has not finished spreading.

During propagation it is completely normal for the site to load on one device or network but not another, because different networks refresh their cached DNS at different times. So if your domain works on your phone’s mobile data but not your home wi-fi, that is propagation, not a broken setup.

Before changing anything else, ask yourself when you last made a DNS change. If it was within the last day or two, give it more time and check again later, ideally after flushing your own device’s DNS cache. Re-editing settings during this window only restarts the clock — patience is genuinely the fix in a large share of cases.

Check your nameservers and DNS records

If propagation is not the answer, the next most common causes are configuration errors. Two stand out. First, wrong nameservers: your domain registrar might still be using default nameservers instead of your hosting provider’s, so your domain is not looking at your host at all. Confirm your domain’s nameservers point where they should.

Second, incorrect DNS records: your A record or CNAME record might point to the wrong IP address or server. If you connected with an A record, verify it holds your host’s exact current server IP with no typos. A stale or mistyped record sends visitors to the wrong place or nowhere.

Critically, remember that records only take effect on the nameservers your domain actually uses. A frequent mistake is editing DNS in one place while your nameservers point somewhere else, so the edits never apply. Confirm where your DNS is actually managed, and make sure your website records live there and are correct.

Check for expired subscriptions

A cause that catches people off guard is expiration. If your domain registration has lapsed, the domain stops resolving and your site goes offline regardless of how your DNS is set — a parked or expiry notice may appear instead. Check that your domain is still active and not expired or in a grace/redemption state.

The same applies to your hosting plan: if your hosting subscription has expired or been suspended (for non-payment or another reason), there is no server to serve your site even if the domain points correctly. And an expired SSL certificate can cause secure-connection errors that make the site appear broken.

So verify the basics of your account: domain active, hosting active, SSL valid, and no outstanding billing issues. These lapses are easy to overlook because they are not “settings” you changed, but an expired domain or hosting plan is a common and completely explaining reason a site suddenly stops connecting.

The troubleshooting checklist

Work through these in order — the most common causes are first, so you fix the likeliest issues fastest:

• Propagation: did you change DNS recently? Wait up to 48 hours and re-check.
• Nameservers: do they point to your host, not the registrar’s defaults?
• DNS records: does your A/CNAME point to the correct, current server IP, with no typos?
• Right place: are you editing DNS on the nameservers your domain actually uses?
• Expiry: are your domain, hosting plan, and SSL all active and paid?
• Published: is your website actually published, not in draft or private mode?
• Cache: have you flushed your DNS cache and tried a different network or incognito window?

Going top to bottom resolves the vast majority of connection issues. If you reach the end and the site still will not connect, you have at least ruled out every common cause, which makes it far easier for your host’s support to pinpoint anything unusual.

Is your website actually published?

A surprisingly common and easily missed cause is that the website itself is not live. If you built your site in a website builder or CMS, the project or page might still be set to draft, private, or unpublished mode — so even with the domain connecting perfectly, there is no public page to show.

Check inside your website builder or content management system that the site is published and public. In some builders there is a distinct “publish” or “go live” step separate from connecting the domain, and skipping it leaves visitors with nothing to see even though the domain is pointed correctly.

This is worth checking early if your domain resolves but shows a blank page, a builder placeholder, or a “coming soon” screen rather than an error. In those cases the DNS side may be fine and the missing piece is simply publishing the site itself.

Clear your cache and test properly

Sometimes the site is actually working and your own device is showing you a stale version. Your browser and operating system cache DNS and page data, so after a change you might keep seeing the old result even though everyone else sees the new one. Flushing your local DNS cache and clearing your browser cache often reveals that the change has, in fact, taken effect.

To test properly, try loading your domain on a different network (like mobile data instead of wi-fi), in an incognito/private window, or on another device. If it works in one of those but not your main browser, the issue was local caching, not your domain — and it will clear on its own.

A DNS propagation checker is also useful here: it shows how your domain resolves from multiple locations worldwide, so you can see whether the change has reached most of the internet even if your own connection is lagging. These checks separate “actually broken” from “just cached on my machine,” which prevents a lot of unnecessary worry.

When to contact support

If you have worked through the checklist — confirmed propagation has finished, nameservers and records are correct and in the right place, nothing has expired, the site is published, and it is not a local cache issue — and the domain still will not connect, it is time to contact your host or registrar’s support.

When you do, describe what you have already checked. Telling support that you have verified nameservers, records, account status, and publishing, and tested across networks, lets them skip the basics and focus on anything unusual, which gets you a faster resolution.

Most connection problems, though, never reach this stage, because they are resolved by the checklist — usually by simply waiting for propagation or correcting a nameserver or record. Working through the common causes methodically is what turns a frustrating “my site is down” moment into a quick, understandable fix.

FAQs

Why is my domain not connecting to my website?

Most often DNS propagation still finishing (up to 48 hours after a change). Other common causes: nameservers still on the registrar’s defaults instead of your host’s, an A/CNAME pointing to the wrong IP, editing DNS in the wrong place, an expired domain or hosting plan, the site not published, or local DNS/browser caching.

How long should I wait before assuming it’s broken?

Up to 48 hours after any DNS change, since propagation spreads gradually and can load on some networks before others. If you changed DNS recently, wait and re-check after flushing your device’s cache before troubleshooting further. Re-editing during this window only restarts propagation.

How do I know if it’s a DNS problem or something else?

Check in order: propagation (recent change?), nameservers (pointing to your host?), DNS records (correct IP, right place?), account status (domain/hosting/SSL active?), publishing (site live?), and local cache (works in incognito or on another network?). A propagation checker shows whether the change reached the wider internet.

Can an expired domain or hosting stop my site connecting?

Yes. An expired domain stops resolving and takes the site offline; expired or suspended hosting means no server to serve the site even if the domain points correctly; and an expired SSL certificate causes secure-connection errors. Always verify your domain, hosting plan, and SSL are active with no billing issues.

My domain loads but shows a blank or ‘coming soon’ page — why?

The DNS side may be fine, but the website itself may not be published — builders and CMSs often have a separate publish/go-live step. Check that your site is set to public, not draft or private. A blank page or builder placeholder (rather than an error) points to a publishing issue rather than a DNS one.

It works on my phone but not my computer — what’s happening?

That’s almost always local caching or partial propagation. Your computer’s browser or OS is showing a cached old result while your phone’s network has already updated. Flush your computer’s DNS cache, clear the browser cache, or try an incognito window — the change has likely taken effect and will appear once the local cache clears.

The bottom line

When your domain is not connecting to your website, resist the urge to panic or start changing things at random — the cause is almost always on a short, fixable list, and often it is not a real problem at all. Start with propagation: if you changed DNS in the last day or two, the likeliest answer is simply that the change is still spreading, and waiting (plus flushing your local cache) is the fix. From there, work down the checklist: confirm your nameservers point to your host, your A/CNAME records hold the correct IP and live on the active nameservers, nothing has expired, your site is actually published, and you are not just seeing a cached version on your own device.

Working through these in order — most likely first — resolves the vast majority of connection issues quickly and turns a stressful outage into an understandable fix. A propagation checker and testing across networks separate “genuinely broken” from “just cached locally,” saving needless worry. And if you reach the end of the checklist with the problem still unsolved, you can hand your host’s support a clear list of what you have ruled out, so they can zero in on anything unusual. Diagnose methodically, and a domain that will not connect becomes a problem you can almost always solve yourself.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. A domain not connecting is usually propagation (wait up to 48h), wrong nameservers, an A/CNAME with the wrong IP or edited in the wrong place, an expired domain/hosting/SSL, an unpublished site, or local cache. Work the checklist top to bottom.