My Site Isn't Loading

"My site is down" can mean a dozen different things. Work through this decision tree from the top. Each step rules out one cause, so by the end you will know exactly where the problem is — and usually how to fix it.

Tools You'll Use

ping — run ping yourdomain.com in a terminal to see whether the domain resolves to an IP at all.
whatsmydns.net — check what nameservers and records the world sees for your domain.
cPanel — confirm your files, quota, and account status.

Step 1: Is the Domain Pointed at Us?

Your domain must use our nameservers for it to load from our servers. At your domain registrar, confirm the nameservers are set to:

ns1.ultranameservers.com
ns2.ultranameservers.com
ns3.ultranameservers.com

Check the live values on whatsmydns.net using the NS record type. If they are wrong or you just changed them, the update may still be spreading — see DNS Propagation. For full setup steps, see Nameservers.

Step 2: Are the DNS Records Correct?

Even with the right nameservers, a wrong A record sends visitors to the wrong place. In cPanel, open Zone Editor and confirm:

The A record for your domain (and www) points to your server's IP address.
There are no stale records left over from a previous host.

Run ping yourdomain.com — if the IP that comes back is not your server's IP, your records or nameservers need fixing.

Step 3: Is There an SSL or Redirect Loop?

If the browser reports "too many redirects" or the page never finishes loading, you likely have a redirect loop. Common causes:

An HTTPS redirect in .htaccess fighting with a WordPress or CDN redirect.
A forced www-to-non-www rule that also loops.

Temporarily rename .htaccess in File Manager to test. If the loop stops, the rule in that file is the cause. See our SSL guide if the loop appeared right after enabling HTTPS.

Step 4: Are Your Files in the Right Place?

If you see a blank page, a "Index of /" listing, or a default cPanel page, your files may be in the wrong document root.

Your primary domain's files must live in public_html.
Add-on and subdomains have their own document roots — check the folder shown when you created them.
Confirm your home page is named index.html or index.php.

Step 5: Is the Account Over Quota or Suspended?

If your account has hit its disk quota, new writes fail and pages can break. If the account is suspended (for example over a billing issue), it will not serve at all.

Log into cPanel and check the disk usage figure in the sidebar.
If you cannot log in, check your billing status in the Client Area.
Free up space by removing old backups and logs, or resolve any outstanding billing.

Note If your site returns a 508 error rather than failing to load, that is a resource limit, not a quota. See 508 Resource Limit Reached.

Step 6: Is It Just Your Browser or Local DNS?

Sometimes the site is fine and only you cannot reach it, because of cached data on your machine.

Try the site in a private/incognito window or a different browser.
Try it on mobile data instead of your home network.
Flush your local DNS cache — see DNS Propagation for the commands.

If the site loads elsewhere, the problem is local to your device or network.

Step 7: Rule Out a Server Outage

If you have ruled out everything above and the site is down for everyone, there may be a server-side issue. Open a support ticket with your domain, what you have already tested, and the exact error you see. We will check the server and get you back online.