Why Is My Website Down? Diagnose It in 5 Minutes (2026)

Your website was fine last night. This morning it's a blank screen, a scary error, or an endless loading spinner — and every minute offline is a customer clicking away. If you're typing "why is my website down" into a search bar right now, take a breath: in roughly 9 out of 10 cases the cause is one of four things, and you can identify which one in about 5 minutes with zero technical skill.

The four usual suspects, in the order you should check them: your own connection, your domain registration, your DNS records, and your hosting server (with its SSL certificate). That order isn't theory. Our team at Hostaccent resolves 20-30 client site issues every single day, and "my site is down" is the most common opening line in that queue — this checklist is the same one our engineers run first, rewritten in plain English so you can run it yourself.

Quick Answer: As of July 2026, the four most common reasons a website goes down are an expired domain registration, broken or still-propagating DNS records, a hosting server problem (crash, suspension, or resource limits), and an expired SSL certificate. Check them in order — down-for-everyone test first, then domain, DNS, hosting, SSL — and you'll usually have your answer within 5 minutes.

Why Is My Website Down? The 4-Layer Check

Every website you've ever visited depends on four layers working at once. Your domain is the address people type. DNS is the phone book that translates that address into a server location. The hosting server is the computer that stores and serves your site. And the SSL certificate is the security pass that lets browsers trust the connection. Break any single layer, and the whole site disappears — even though the other three are perfectly healthy.

That's why guessing is so expensive. When you find your site down, what to do first is not to change everything at once — it's to test the layers in order, cheapest check first. Panicked owners who skip this step often "fix" three things that were never broken and still stay offline.

Match what you're seeing to the most likely layer:

| What your browser shows | Most likely layer | Go to | |---|---|---| | "This site can't be reached" / DNS error | Domain or DNS | Steps 2-3 | | A registrar parking page or ads on your domain | Expired domain | Step 2 | | Spins forever, then times out | Hosting server | Step 4 | | 500, 502, or 503 error message | Hosting server | Step 4 | | "Your connection is not private" warning | SSL certificate | Step 5 |

Bookmark this table. It's the 5-second version of everything below.

Step 1: Is It Down for Everyone, or Just You?

Time: about 1 minute. Before you touch anything, confirm the outage is real. A surprising share of "downtime" turns out to be a stale browser cache, a hiccuping Wi-Fi router, or an office firewall — the site was up the whole time.

Run these three quick tests:

1. Hard-refresh the page. Ctrl+F5 on Windows, Cmd+Shift+R on Mac. This bypasses your browser's saved copy of the page.
2. Try incognito mode and a second device. A private window ignores most cached data. Then load the site on your phone with Wi-Fi turned off — mobile data uses a completely different network path.
3. Use a website down checker. Free tools built for the "is my website down or is it just me" question test your address from multiple locations worldwide and tell you instantly whether the outage is global or local to you.

If the checker reaches your site but you can't, the problem is on your end — restart your router, flush your device's DNS cache, and you're likely done. If the tool confirms your website is not loading for anyone, the outage is real. Move to Step 2.

Pro Tip: The phone-on-mobile-data test is the fastest tiebreaker we know. If the site loads over 4G but not on your Wi-Fi, stop debugging your website entirely — the issue is your local network, and no hosting change will fix it.

Step 2: Did Your Domain Expire?

Time: about 1 minute. This is the most embarrassing cause and one of the most common. Domains are rentals, not purchases — miss a renewal and your address simply stops pointing anywhere. The telltale signs: your site suddenly shows a parking page full of ads, or browsers report the address doesn't exist at all.

Check it definitively with ICANN's official domain lookup tool. Type your domain and read the expiry date field. If that date is in the past, you've found your answer.

Here's the honest timeline of what happens next, because it matters:

• Grace period (typically 0-45 days after expiry): you can usually renew at the normal price — a .com renews for around $13.99/yr — and the site comes back within hours.
• Redemption period (roughly 30 days after that): you can still recover the domain, but registrars charge a recovery fee that industry-wide typically runs $80-200 on top of the renewal.
• After redemption: the domain returns to the open market, and anyone — including competitors and squatters — can register it.

An expired domain also silently kills your email, which is why owners sometimes discover the problem through bouncing messages before they ever notice the website. If you're registering fresh or consolidating, you can check and register your domain in about two minutes — .com runs $13.99/yr with the same price at renewal, so there's no year-two surprise.

Pro Tip: Turn on auto-renew and check the card on file today. In the expired-domain cases we see, the owner almost always had auto-renew enabled — it failed because the saved card had expired, and the warning emails went to spam.

Step 3: Is It a DNS Problem?

Time: about 1 minute. DNS (Domain Name System) is the internet's phone book: it translates your human-readable domain into the numeric address of your server. When DNS is misconfigured, your domain is alive and your server is running — they just can't find each other.

DNS problems almost always follow a change: you switched hosts, edited records, changed nameservers, or moved to a new provider. Two things to know:

Propagation is normal, not broken. After any DNS change, the update spreads across the internet's resolvers gradually. Most changes complete within 1-4 hours, but the standard window is up to 24-48 hours worldwide. If you changed something today and the site is patchy — working on your phone, dead on your laptop — that's propagation, and the only fix is patience. Cloudflare's DNS learning guide explains the mechanics well if you want the deeper story.

Wrong records are broken. If nothing was changed recently and DNS still fails — typically a dns_probe_finished_nxdomain error in Chrome — check that your domain's nameservers point at your actual host and that an A record exists for your root domain. Our step-by-step guide to fixing dns_probe_finished_nxdomain walks through every check with screenshots.

Don't want to run any of these checks yourself? Hostaccent's engineers handle the whole thing — domain, hosting, SSL, and your live website — start to finish, and they diagnose downtime exactly like this every day. Tell us what's happening with your site and we'll take it from there. One message, zero technical work.

Step 4: Is Your Hosting Server Down?

Time: about 2 minutes. If your domain is current and DNS resolves, the trail leads to the server itself. The good news: servers usually tell you what's wrong through HTTP status codes — MDN's HTTP status code reference covers the full list, but three matter most here:

• 500 Internal Server Error — something in your site's code or configuration crashed. On WordPress, the culprit is usually a plugin update, a corrupted .htaccess file, or a PHP version mismatch.
• 502 Bad Gateway / 504 Gateway Timeout — the front-end server is fine, but the back-end application stopped answering. Often temporary; often load-related.
• 503 Service Unavailable — the server is deliberately refusing traffic: maintenance, overload, or — read carefully — an account suspension notice.

In our experience running the Cloudflare → Nginx → Apache stack at Hostaccent, we found the three most common server-side causes in real tickets are, in order: a billing lapse that suspended the account (check your inbox and spam for invoice emails before anything technical), a plugin or PHP update that broke the site, and resource limits on oversold budget plans — cheap hosts often cap CPU seconds and memory so tightly that one traffic spike takes you offline.

Two quick self-serve checks: log into your hosting control panel (if you can't even log in, the account or the whole server is the problem, and support is your next stop), and look for your host's status page, which reports server-wide incidents. If you're instead seeing a client-side code like a 400 Bad Request error, that's a different animal — usually cookies or a malformed URL rather than a dead server.

Pro Tip: Set up a free uptime monitor today — most free tiers ping your site every 5 minutes and email you the moment it stops answering. The gap between "a monitor told me at 6:04 am" and "a customer told me at lunch" is the real cost of downtime.

Step 5: Has Your SSL Certificate Expired?

Time: about 30 seconds. If visitors see "Your connection is not private" or NET::ERR_CERT_DATE_INVALID, your site isn't down at all — browsers are blocking it because its security certificate expired. As of 2026, every major browser treats an expired certificate as a hard stop, so to your customers the effect is identical to a full outage.

Certificates have short lifespans by design. Free certificates from Let's Encrypt last 90 days and are meant to renew automatically — when they don't, it's usually because the automation broke during a migration or a DNS change. Click the padlock (or the warning triangle) in your address bar to see the exact expiry date.

The fix is genuinely simple on a decent host: open your control panel, find the SSL section, and reissue or force-renew the certificate — typically a 15-minute job including the wait. If your host makes you pay extra for basic SSL or reissue it manually every quarter, that's a signal worth remembering when you read the next section.

Fix It Yourself, or Hand It Off?

Full honesty: most of the fixes above are DIY-able, and you now know more than enough to attempt them. Here's what each path really takes.

The DIY path. Renewing an expired domain is a 10-minute job at $13.99/yr. Fixing DNS records takes 30-60 minutes of careful reading plus the propagation wait. Reissuing SSL is 15 minutes in a control panel. The hard ones are code-level 500 errors (an hour or a weekend, depending on your comfort with plugins and PHP) and escaping a chronically overloaded host — moving a site takes a first-timer 2-4 hours and a working knowledge of backups, DNS, and email records. Budget-wise, solid shared hosting starts at $1.99/mo on the Economy shared plan with NVMe SSD storage and free SSL — our full website cost breakdown covers everything else.

The done-for-you path. If your time is worth more than the hours above — or the site earns money every hour it's up — hand it off. A complete A-to-Z setup covers domain registration, hosting, SSL, migration of your existing content, and a live, working website, plus ongoing care so updates, errors, and security never land on your desk again. Across the 4,000+ migrations our team has handled since 2012, the step owners most often get wrong solo is the DNS-and-email cutover — exactly the part a managed setup makes invisible. If you're comparing options, see what fully managed hosting actually includes and typical rates for hiring the work out.

The honest decision rule: if the outage was a one-off (expired card, plugin update) and you fixed it in an afternoon, DIY is fine — you don't need to pay anyone. If this is the second outage this quarter, or your stomach dropped reading Step 4, the managed path pays for itself the first time it prevents a repeat.

Your Next Step: A Site You Don't Have to Rescue

What to remember from the last five minutes:

• Always run the down-for-everyone test first — it's the 60-second check that prevents hours of wasted fixing.
• Expired domains and lapsed billing cause more "mystery" outages than hackers ever do.
• DNS changes need 24-48 hours; don't redo settings mid-propagation.
• An expired SSL certificate blocks your site as completely as a dead server.

Now that you know the outage is one of four layers — and which layer yours lives in — you have two options. You can work through the fix yourself with the steps above, or you can send one message and have it handled: diagnosis, fix, and a setup built not to break again. Hostaccent has launched 10,000+ websites and holds a 99.9% uptime guarantee, backed by a 30-day money-back guarantee, as a UK-registered company trading since 2012 (UK-incorporated 2018) — and the engineers who wrote this checklist are the ones who'll open your ticket, not a script-reading call centre. One honest caveat: if your fix turned out to be a one-line card update, you don't need us yet — bookmark this page instead. For everything else, tell us what you need — domain, hosting, SSL, and your live site, handled end to end — and if you only want solid ground to run things yourself, the Economy plan at $1.99/mo is where these fixes stop being your problem. So the next time you catch yourself searching "why is my website down," it'll be for someone else's site.

Frequently Asked Questions About Website Downtime

How do I check if my website is down for everyone or just me?

Use a free multi-location website down checker: it tests your address from servers around the world. If every location fails, the outage is real. If the tool loads your site but your browser can't, the problem is local — clear your cache, flush DNS, or switch to mobile data to confirm.

Why is my website down when my hosting bill is paid?

A paid hosting bill only rules out one cause. Your domain registration is billed separately and may have expired, DNS records may be broken or still propagating, your SSL certificate may have lapsed, or a plugin update may have crashed the site with a 500 error. Run the 4-layer check in order to isolate it.

How long does DNS propagation take?

Most DNS changes complete within 1-4 hours, but the standard worldwide window is 24-48 hours. During propagation your site can load for some visitors and fail for others — that's normal, not broken. Avoid making further DNS changes mid-propagation; you'll reset the clock and make diagnosis harder.

Can an expired SSL certificate make my site unreachable?

Effectively, yes. The server stays online, but modern browsers show a full-page "Your connection is not private" warning that most visitors won't click past. Free certificates last 90 days and should auto-renew; when automation breaks, reissuing through your hosting control panel usually restores access within 15 minutes.

What does a 503 Service Unavailable error mean?

A 503 means the server received your request but deliberately refused it — usually planned maintenance, a traffic overload, or a suspended hosting account. Check your host's status page and your billing emails first. If the account is suspended for non-payment, settling the invoice typically restores the site within an hour.

My site is down and I can't fix it — what should I do?

Note the exact error message and anything that changed recently (renewals, updates, DNS edits), then contact your provider with those details. If you'd rather not chase it at all, Hostaccent's engineers answer directly — they diagnose the cause, fix it, and can rebuild the full setup, from domain to live website, on request.