A site will not load. Before you restart your router, clear your browser or write to the site's owner, it is worth spending one minute finding out whether the site is down for everyone or only for you. The answer decides what to do next: wait, or fix something on your side.
Step 1: check from somewhere else
The quickest test is to ask a computer on a different network to load the site. The Is It Down Checker does exactly this from the Kitlantis server. If the site answers there, it is up, and the problem lies somewhere between you and it. If our server cannot reach it either, it really is down.
A good second test is your phone with Wi-Fi switched off. Mobile data uses a different network and usually different DNS servers, so a site that opens there but not on your Wi-Fi points to your connection rather than the site.
If it is down for everyone
There is little you can do except wait, but the error tells you something about why:
- 500 means the site's own software failed while building the page.
- 502, 503 and 504 mean a server in front of the site could not get a proper answer from the one behind it. They are common during heavy traffic and while a site is being updated.
- 520 to 530 are Cloudflare's codes: Cloudflare is working, but the site's own server is not answering it.
- No answer at all, ending in a timeout, means the server is off, overloaded or cut off from the internet.
- DNS_PROBE_FINISHED_NXDOMAIN in the browser means the name has no address in DNS. The domain may have expired, or there may be a typing mistake in the address.
If it is only you
Work from the quickest checks to the slowest:
- Reload, then try a private window. This rules out old cached files, cookies and most extensions in one go.
- Switch off a VPN, ad blocker or security extension for a moment. Any of them can stop a site from loading.
- Try another network. If mobile data works, the problem is your Wi-Fi, your router or your internet provider.
- Change your DNS. Your provider's DNS servers may still hold an old address for the site, especially just after it moved to a new server. Setting your device or router to a public resolver, such as 1.1.1.1 or 8.8.8.8, often fixes this straight away. The DNS Propagation Checker shows whether the big public resolvers agree on the site's address.
- Restart your router. It clears its own DNS cache and gets a fresh connection.
- Consider a block. Office and school networks filter many sites, some sites refuse visitors from certain countries or networks, and internet providers are sometimes ordered to block a site. In these cases the site can be up everywhere else and still unreachable from where you are.
When the browser shows a security warning
A warning such as NET::ERR_CERT_DATE_INVALID means the site's security certificate has expired, and NET::ERR_CERT_COMMON_NAME_INVALID means it was issued for a different name. The site is running, but your browser is right to stop you: never click past such a warning on a site where you sign in or pay. The SSL Certificate Checker shows exactly what is wrong with the certificate.
ERR_TOO_MANY_REDIRECTS means the site's addresses send visitors round in a loop. Clearing the site's cookies sometimes helps; if not, the Redirect Checker shows every step of the loop, which is what the site's owner needs to fix it.
If it is your own site
Check from outside first, so you know what visitors see. If it is down, go through the usual causes in order: is the server switched on, is the web server program running, is the disk full, and has the domain or the certificate expired? An expired domain is easy to miss and takes every page, email and subdomain down at once; the Domain Age Checker shows its expiry date.
Next time a site will not open, start with the Is It Down Checker. One check from our server tells you whether to wait or to fix something on your side.



