Domain Won't Load? Here's How to Diagnose and Fix It

You bought a domain, set up hosting, and now you type it in the browser and get... nothing. Or an error. Or someone else's site. Here's how to fix it, step by step.

Step 1: What exactly are you seeing?

Different errors mean different things:

• "This site can't be reached" → DNS or server problem
• "Your connection is not private" → SSL certificate problem
• "404 Not Found" → Site loaded but no content on that URL
• A parking page from GoDaddy/Namecheap → Nameservers not updated
• Connection times out → Server unreachable or firewall blocking

Step 2: Check DNS

Open a terminal:

`` dig yourdomain.com ``

Or use whatsmydns.net for a global check.

No IP returned (NXDOMAIN) Your domain's DNS is broken. Possible causes: - Domain expired — check registrar - Nameservers wrong — check registrar's nameserver settings - DNS records never added — log in to your DNS provider

IP returned but it's wrong DNS is working but pointing to the wrong server. Update the A record at your DNS provider.

DNS changes not taking effect DNS has TTL (time-to-live) — changes can take minutes or up to 48 hours to propagate globally. You can't rush this.

Step 3: Check nameservers

If you just bought a domain or changed hosts, you probably need to update nameservers.

• At your registrar (GoDaddy, Namecheap, etc.):
• Look for “Nameservers” setting
• Update to your host's nameservers (your host will provide these)

This is the #1 cause of “I set up hosting but the domain doesn't work”.

Step 4: Check the A record

Once nameservers point at the right DNS provider, create the records:

• For the bare domain (yourdomain.com):
• Type: A
• Name: @ (or blank)
• Value: your server's IP address

• For www:
• Type: CNAME
• Name: www
• Value: yourdomain.com

Most hosts provide exact records to copy.

Step 5: Check SSL

If you see a certificate warning:

Browser says “Not Secure” You have no SSL cert, or an expired one. Install Let's Encrypt (most hosts do this in one click).

“Your connection is not private” / “Common name mismatch” Your cert is for a different domain. Install a cert that matches.

Mixed content warnings Page loads over HTTPS but includes HTTP resources (images, scripts). Update all internal URLs to https://.

Step 6: Check the server

If DNS is right but the server won't respond:

`` ping yourserver.ip curl -I yourdomain.com ``

If ping works but HTTP doesn't, your web server isn't running or isn't listening on port 80/443. Check with your host.

Step 7: Check hosts file (if it's only broken for you)

If the site works for everyone except you, check /etc/hosts (Mac/Linux) or C:\Windows\System32\drivers\etc\hosts (Windows). You may have an old entry overriding DNS.

Common scenarios

"I just bought the domain" → Update nameservers at registrar. Wait up to 48h for propagation.

"I changed hosts" → Update A record at DNS provider. Wait for TTL.

"Site works on www but not bare domain" → Add A record for @ (bare domain), not just CNAME for www.

"Works on HTTP but HTTPS fails" → Install SSL certificate.

"Emails work but website doesn't" → MX records are right, A record is wrong. Fix A record.

"Site works logged in, errors for everyone else" → Cache or cookie issue. Not DNS.

The fastest path to “it just works”

1. Point domain nameservers at your host's DNS
2. Create A record for @ and CNAME for www
3. Wait 10-30 minutes
4. Install SSL certificate
5. Set up HTTP → HTTPS redirect

That's it.

Need help?

DNS and domain issues can be frustrating but are almost always fixable in under an hour once you know what to check. Send me a message if your domain is misbehaving.