You can reach example.com perfectly, but blog.example.com or shop.example.com won't load. It feels contradictory — surely if the main site is up, everything on the domain should be up too? Not quite. This is one of the most common sources of confusion in website troubleshooting, and the answer is genuinely useful to understand. So: can a subdomain go down while the main site stays up? Absolutely yes — and here's why, plus how to figure out what's actually broken.

The short answer: yes, easily

A subdomain can go down completely while the main domain runs without a hitch — and the reverse is equally true. That's because a subdomain isn't just a "folder" of the main site. It's a separate address with its own DNS record, and it very often points to an entirely different server or service. When you understand that, the mystery disappears.

Why a subdomain is independent

Every subdomain (blog., shop., app., mail. and so on) has its own DNS record — usually an A record pointing to an IP, or a CNAME pointing to another service. Because of that, each subdomain can be routed to a completely different place from the main domain.

In practice, a single domain's subdomains are often spread across multiple servers and providers:

  • example.com → your main web host
  • blog.example.com → a hosted blogging platform
  • shop.example.com → an e-commerce service like Shopify (via a CNAME)
  • app.example.com → a separate application server
  • mail.example.com → your email provider

Each of those is a distinct system that can succeed or fail on its own. Subdomains that point to third-party services usually do so with a CNAME — our guide on A records vs CNAMEs explains exactly how that routing works. If the service a CNAME points to goes down, that one subdomain goes down with it, while your main site (on a different server) carries on unaffected.

Common reasons a subdomain goes down while the main site works

When a subdomain fails but the main domain is fine, it's usually one of these:

  • A different server or service is down. The subdomain lives on separate infrastructure that's having its own outage.
  • The subdomain's DNS record is broken or missing. If its A or CNAME record is wrong, deleted, or points to a dead target, only that subdomain fails to resolve.
  • A third-party service is down. Subdomains pointing to hosted platforms (stores, help desks, status pages) go dark whenever that provider has an outage.
  • An expired SSL certificate. Certificates can be issued per-subdomain. If the subdomain's certificate expires (and it isn't covered by a wildcard), browsers block just that subdomain with a security warning while the main site stays secure.
  • A misconfiguration after a change. A recent DNS or hosting change to the subdomain that didn't affect the root domain.

How to check whether it's the subdomain or the whole domain

The trick is to test them separately, because they're separate systems:

  1. Check each address on its own. Run both the main domain and the full subdomain (e.g. shop.example.com) through our live website down checker individually. If the main domain comes back up and the subdomain comes back down, you've confirmed the problem is isolated to the subdomain.
  2. Look up the subdomain's DNS record. Use our DNS Records tool on the full subdomain to see its A or CNAME record. If it's missing or points somewhere unexpected, that's your culprit. Our guide on how to look up DNS records covers reading the results.
  3. Confirm it's not just you. If only you can't reach the subdomain, the issue may be local rather than a real outage — our guide on whether a site is down for everyone or just you helps you tell the difference.

What to do if a subdomain is down

Once you've confirmed the subdomain specifically is failing:

  • Check its DNS record points to the correct server or service, and hasn't been deleted or misdirected.
  • Check the status of the service it points to. If shop. points to a hosted platform, see whether that platform is having an outage.
  • Check its SSL certificate hasn't expired, especially if you're seeing a security warning on that subdomain only.
  • Review recent changes to that subdomain's configuration.

Because the main site is fine, you can safely focus entirely on the subdomain's own setup — the two don't share a single point of failure.

The flip side: main site down, subdomain up

The same independence works in reverse. Your main site can go down while a subdomain — say, a status page hosted elsewhere — stays online. This is actually why many companies host their status pages on a separate subdomain or provider: so that when the main site fails, the page telling customers about it is still reachable. It's a deliberate use of the fact that subdomains fail independently.

The bottom line

Yes — a subdomain can absolutely go down while the main site stays up, because each subdomain has its own DNS record and often lives on its own server or third-party service. When one fails and the other doesn't, test them separately, check the subdomain's DNS record and SSL certificate, and look at whatever service it points to. Understanding that subdomains are independent systems turns a baffling "how is this even possible?" moment into a quick, targeted fix.