If your website will not load, enquiries cannot reach you either
For a business, an unavailable website is more than an annoying error message. Visitors cannot view services or find contact details, and someone arriving through an advert has no usable landing page. Reliable data is needed to know how many enquiries are actually lost, but the customer journey can certainly be interrupted.
However, an unresolved domain name, an unresponsive server and a failing website application are different problems. Your domain, DNS, hosting and website itself are connected but have different roles. That is why switching hosting providers blindly after the first error is rarely sensible.
What might the error on your screen mean?
These clues help you explain the issue to your provider or website specialist. An error code alone does not prove one specific cause.
NXDOMAIN or name-resolution error
There may be a problem with the domain's DNS records, delegation or the network used to resolve the name. Check the exact address.
ERR_CONNECTION_TIMED_OUT
The connection was not established in time. The obstacle may be on the network, route or server; test from another network too.
502 / 503 / 504
These may indicate server, application or intermediary-service problems. They do not automatically mean the domain has expired.
Cloudflare 521–524
When Cloudflare is in use, communication between the intermediary service and origin server may be affected. The exact code and Ray ID are useful.
Fails with or without www only
The two domain versions may have different DNS, redirect or certificate configurations.
Works on mobile data but not Wi-Fi
Local DNS, network settings or caches may contribute. That does not prove a nationwide outage.
Domain, DNS, hosting and website: what is the difference?
Domain: your website's name
The domain is the address customers enter. Registration expiry or changes to permissions can affect access. Domain renewal and hosting may be billed separately, even by different providers.
DNS: which server should the address lead to?
DNS links a domain to the correct network destination. An incorrect change or faulty delegation can mean the address no longer points to the working website. A DNS issue after migration does not prove the website itself has been deleted.
Hosting and server: is something available to respond?
Server operation, capacity, security protections or the backend application may cause outages. If an intermediary provider displays an error page, interpret its error code in that provider's context.
Website application: is the site's functionality running?
The domain and server can be reachable while the site's own application fails. Changing hosting alone may not resolve that; targeted developer investigation may be needed.
A 404 is not the same as a total outage. If only an old subpage is missing while the homepage and other service pages work, the guide to handling 404 errors is more relevant.
Three safe steps you can take
Do not start changing DNS settings or deleting files simply because the page will not load. Record what is happening first.
- 01 · Record the exact failing URL and messageDoes the whole site fail or just one page? Do the versions with and without wwwbehave the same? Make sure screenshots are readable.
- 02 · Test in another safe environmentIf it fails on the office Wi-Fi, try mobile data, for example. The difference can help, but one test is not definitive proof.
- 03 · Report what you see to the right partyThe domain registrar, hosting provider and website developer may each be responsible in different cases. Describe changes made immediately before the problem started too.
Is your website unavailable?
Do not leave customers guessing what went wrong
Send the address, exact error and when it started. I can help clarify the situation and the kind of professional investigation needed; I cannot promise automatic hosting or DNS recovery.
Why does it matter where and when the site fails?
If the site works intermittently, timestamps and differences between networks are important. Equally, a problem that started after a recent domain change or website migration calls for different next steps from a longstanding, unchanged system that suddenly went down.
Illustrative example, not a Kaluzsa client: a car repair shop in Szolnok is inaccessible over office Wi-Fi but works on the owner's phone over mobile data. That does not immediately prove the hosting provider's entire service is down. The different conditions need investigating first.
If it fails on only one network
Include the network, device and time in the support ticket. A site working on another network is not a reason to migrate the entire website.
If it appears to fail everywhere
Record the URL, error code and start time, then send that information promptly to the providers or web specialist involved.
If it started after a migration
A precise list of changes and old/new domain versions is essential. Do not begin another migration before checking the previous state.
If only the contact form fails
The site may be accessible while quote-request processing is broken. That needs a different investigation.
Who should you contact: registrar, host or developer?
For a domain expiry or ownership issue, start with the company managing your domain registration. If the origin server is not responding, the hosting operator can often inspect server-side indicators. If the website application is failing, developer investigation may be more appropriate.
Several parties may be involved: the domain could be registered with one provider, DNS managed by another and the website hosted elsewhere. In such cases, a precise problem description and clear access permissions matter more than randomly switching suppliers.
For more complex web systems, you might later consider custom web development and planning a more robust setup, but a simple DNS fault does not automatically justify a development project.
Five details to include when asking for help
- Exact domain and affected URL: for example, whether only the homepage or every subpage fails.
- Error message: full text, code and screenshot; Cloudflare Ray ID if shown.
- Start time: when did you first notice it, and is the failure continuous or intermittent?
- Environment: which device and network show the issue, and can others reproduce it?
- Recent changes: was there a domain renewal, migration, update or hosting change?
Do not send passwords, FTP or hosting credentials, or customers' personal data through a public contact form. Agree on a secure way to provide access separately if necessary.
Frequently asked questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It is a name-resolution error: the name did not return a suitable DNS response. The cause might involve the domain, DNS or local network environment.
Is every 5xx error a hosting-provider fault?
No. Intermediary systems and the website application can produce those responses too. Investigate the exact code and environment.
Does a 404 mean my whole website is down?
No. A 404 usually indicates that one particular URL is missing. If the homepage and other pages work, it is not a total site outage.
Why does it work on one device but not another?
Different networks, caches and DNS-resolution environments may produce different results. Record the difference instead of immediately changing settings.
How long will recovery take?
That depends on the actual cause, provider and changes needed. No universal recovery time can be promised.
Online availability · Kaluzsa
Keep the online entrance to your business open
If your website will not load, send the exact address and error message. The aim is a sensible, targeted next step, not a rushed migration or unnecessary full rebuild.