Troubleshooting · Practical guide

Website not loading? A DNS troubleshooting checklist

Find out whether the issue is DNS, hosting, SSL or local caching before making changes.

Quick answer

Find out whether the issue is DNS, hosting, SSL or local caching before making changes.

Start with the checks below. Each step explains what to look for and what to try next.

Identify the exact symptom

“Server not found” often points toward DNS resolution. A timeout can indicate connectivity or firewall issues. An HTTPS warning may indicate a certificate problem. A 500 error generally indicates a server-side application problem.

Find where the connection breaks

Find where the connection breaks

Domain expired or on hold

Check your registrar status before editing hosting settings.

DNS points somewhere unexpected

Compare authoritative records with the IP or nameservers in your hosting welcome details.

DNS looks correct, site still fails

Test HTTPS and check the hosting account or error logs.

Only one network shows an old site

It may be a cached DNS answer; compare another network before changing records.

Before you continue: Do not change nameservers and A records together while diagnosing. Record existing values first.

Check in the right order

  1. Confirm that your domain is registered and active.
  2. Check which nameservers are authoritative.
  3. Verify that the A/AAAA or CNAME records lead to the intended hosting endpoint.
  4. Check if the hosting service is active and its web server is responding.
  5. Test HTTPS and certificate coverage.
  6. Try another network or DNS resolver to rule out local cache.

Avoid changing everything at once

Make one verified DNS change at a time and record the original value. Unnecessary changes can interrupt email or other connected services.

When to contact support

Share the domain, exact error, time it began, and steps you’ve already checked. Never include passwords or one-time codes in a support request.

How to confirm the issue is resolved

  1. Repeat the original action that produced the issue.
  2. Check the result in a second browser or network when relevant.
  3. Review logs or status messages for remaining errors.
  4. Keep a short record of what changed so it can be reversed if necessary.

If the issue persists, contact support with the exact error, time, affected domain and actions already tried—never include passwords or secret keys.

Guidance may vary by plan, control panel version and enabled features. Review the settings available to your account before changing live services.