Why Is My Website Down? A Step-by-Step Diagnosis Guide
A website that will not load is stressful, but panic rarely helps. The trick is to work from the outside in — rule out your own connection first, then DNS, then the domain, then the server — so you find the real cause instead of chasing the wrong one. Here is a calm checklist.
Step 1: Is it just you?
Before assuming the worst, check whether the site is down for everyone or only you. Try it on mobile data instead of Wi-Fi, or use an online "is it down" checker. If it loads elsewhere, the problem is your network or a local cache, not the site.
Step 2: Check the error you see
The message matters. Each points somewhere different:
- A specific error code (500, 502, 503) — a server or site issue; see the matching guide.
- "This site can't be reached" / DNS error — a DNS or domain problem.
- An SSL warning — a certificate issue; see fixing SSL errors.
Step 3: Has the domain expired?
An expired domain takes a site offline instantly. Check your renewal status — see what happens when a domain expires. Renewing usually brings it straight back.
Step 4: Check DNS and nameservers
If DNS was recently changed, the site may be unreachable while it settles. Confirm your nameservers are correct and allow time for propagation.
Step 5: Check the server and your account
Look at your resource usage for an overload, and read the error log. If everything on your side looks fine and the site is still down for everyone, open a support ticket so we can check the server.
Frequently asked questions
The site loads for me but not for my client.
That is usually local — their network, DNS cache, or a stale propagation state after a recent change. Ask them to try mobile data and to clear their cache.
How do I know if it's the domain or the hosting?
A DNS or "can't be reached" error points to the domain/DNS side; a server error code or blank page points to hosting. Match the message to the cause using the steps above.
Everything looks fine but it's still down.
When your own checks come up clean and the site is down for everyone, it is time for us to look at the server. Send a ticket with the exact error and when it started.
Was this article helpful?