Website Not Loading? Causes and a Step-by-Step Checklist
Website not loading? First find out who is affected, then check domain, DNS, hosting, SSL, error codes and caching in order, and learn who to contact.
rabbitclip teamPublished: 7 min read
Short answer
If your website will not load, the cause is usually one of five places: the domain has expired, the DNS record is broken, the hosting account has stopped, the SSL certificate has run out, or the server is returning an error. The right order is to find out first whether the problem is only yours or everyone's, then read the message the browser gives you, and then work from the domain towards the hosting. In most cases the first ten minutes show whose responsibility the fault is.
The biggest mistake under pressure is changing things before the cause is known: deleting DNS records, reinstalling the hosting, uploading the site again. Most of these cannot be undone, and if the fault lies elsewhere they make it worse. Look first, then touch.
Below you will find what to check in order, what the error codes mean, what a business owner can do alone, and who you should write to.
Is the site really down, or is it only down for me?
The first job is to understand the scope. Try opening the site on your phone over mobile data, on another network and in another browser. If it opens in one place and not in another, the fault lies in the connection, in your computer's cache or in a rule on your office network rather than in the site.
You can also confirm from the outside whether it is down for everyone. The site-up checker on our site queries the address from outside and shows whether it answers. It is the quickest answer to the question of whether the fault is yours or the site's.
Could the domain name have expired?
Yes, and more often than people expect. A domain renews yearly; the renewal emails may go to an old address, the payment method may be invalid, or auto-renewal may be switched off. An expired domain first falls back to a parking page and later stops resolving altogether, and your email stops along with your website.
A domain lookup shows the registration status and the expiry date. If it has expired, log in at once to the registrar where you bought it and renew. It also matters to know who will do this: the domain often sits in an agency's or a former employee's account. The owner of the domain should be your company.
What may have broken on the DNS and hosting side?
DNS is the phone book that connects a domain to the address of a server. If the record has been deleted, points to the wrong server, or the domain's name servers have been changed, the site will not load. The typical moment is just after a migration, a new hosting plan or an email service being added. While DNS changes propagate, some people may see the old address and others the new one for a while.
On the hosting side the most common causes are an account suspended for billing or contract reasons, a full disk or resource quota, a server under maintenance and a software version that no longer matches. All of these become clear when you look at the hosting company's panel or contact their support.
- Do the domain's name servers still point to the right hosting
- Does the main address record point to the server's current address
- Is the hosting account active, or has a quota been reached
- Was a migration or DNS change made recently
What do the browser message and the error code tell you?
The error message tells you where the problem is. A certificate warning points to SSL, a message that the site cannot be reached or the address cannot be found points to DNS, and a connection timeout means the server is not responding. If a page opens and shows a code, the code gives you a direct lead.
Code 403 means access is blocked, so a permission or security rule is at fault. Code 404 means the page was not found; if you see it on the home page, there is a redirect or file problem. Code 500 means the server or the site's software has failed, 502 and 504 mean a server behind the front one is not answering or is too slow, and 503 means the server cannot serve for the moment, for example because of maintenance or overload.
- 403: access denied; a firewall or file permission
- 404: page missing; a redirect or a deleted file
- 500: server or software error; a recent update or plugin
- 502 and 504: the back-end server is not answering or is slow
- 503: service temporarily unavailable; maintenance or overload
How do SSL, firewalls and caching take a site down?
An expired or wrongly installed SSL certificate shows a full-screen security warning, and most visitors turn back. Even if the site is technically up, in practice it is closed. Certificates failing to renew automatically is common; the reason is usually a DNS or hosting change that broke the renewal check. A security and SSL check shows the certificate's state from the outside.
A firewall or CDN layer with the wrong settings can also shut the site to its own visitors, by blocking a country, an IP range or a legitimate bot. Caching does the opposite: you have fixed the fault, yet it keeps showing the old broken page. Do not say it is still broken until you have cleared the cache and tried in a private window.
What are the common mistakes, and who should you write to?
The most common mistake is writing to one person and waiting. Telling the hosting company only that your site is not opening gets you half an answer. Include the error message, the time and the last change you made, and attach a screenshot. The second mistake is quietly changing records while trying to fix things; if nobody knows what changed, nothing can be rolled back.
Who to write to depends on the type of fault. For domain expiry and name servers, write to the domain registrar. If the server is not responding or the account has stopped, write to the hosting company. If the server is up but a software error such as 500 appears, write to the developer or agency that built the site. If you are unsure, send the result of the checklist above in one message to everyone concerned.
- Domain expiry and name servers: the domain registrar
- Account suspension, quota, server fault: the hosting company
- Software error, plugin, breakage after an update: the team that built the site
- Firewall or CDN block: whoever set up that layer
When a site will not open, check in order: scope, domain, DNS and hosting, error code, SSL and cache. Finding out what broke before deleting anything makes most problems solvable in minutes. The next step is to document domain ownership and hosting access in the company's name. If you would like us to look at your infrastructure together so that the same fault does not return, we would be glad to hear from you in a discovery call with rabbitclip.
FAQ
I see a blank white page when I open my site. What does it mean?
Most often the site's software has hit an error that is not being shown on screen. Roll back the latest update, plugin or theme change and look at the server error log.
Why does the site open in one place and not in another?
Usually a DNS change has not yet propagated, or there is a local cache or a network rule. Trying another network and a private window shows which it is.
Does the site vanish the moment a domain expires?
Not always at once. The registrar may first turn the page into a parking page, and resolution stops entirely later. What happens after expiry differs by registrar, so ask yours.
What should I write to the hosting company?
Give the domain, the exact error message or code, when it started and the last change you made. Add a screenshot if you can.
