My website has stopped working, what to do in Algeria (2027): check from elsewhere, five links in order, read the error message, know who to call, and find out before your customers

“Since this morning our site no longer displays. On my computer the browser says ‘This site can’t be reached’; a customer tells me he sees a security warning. I do not know whether it is the domain name, the hosting or the site itself, nor who to call: the agency that built it no longer answers. Where do I start?” With the error message: it already says at which link the visit stops. Then one check from your phone, and five links to look at in order.

Symloop13 min read
My website has stopped working five links, one error messageCheck from elsewhere, read the message, know who to call, and find out before your customersWEBSITE DOWN · ALGERIA · 2027My website has stopped workingfive links, one error messageCheck from elsewhere, read the message, know who to call, andfind out before your customersHEARD FROM A CUSTOMER35 hours downHEARD FROM AN ALERT45 minutessymloop.com

Short answer. First note the error message word for word, with the time. Then open the site from another network, your phone on 4G: if it opens, the fault is at your end. If not, five links, in this order. The domain name: has it expired? DNS: does the name still lead to the server? Hosting: is the account active, does the server answer? The certificate: has its date passed? The application: what changed yesterday? “Not found”, “timed out”, “connection not private” and “error 500” point neither to the same link nor to the same person to call. For afterwards: an outside test every minute, which warns you before your customers.

This guide is for the manager whose company site no longer displays, or shows an error, and for the founder based in France who hears about it from a customer. The definitions quoted come from public sources: the response codes of a web server, the Domain Name System, the certificate, website monitoring. The messages are those Chrome displays; the words change from one browser to another. The outage, its times and the number of visits are a constructed example. If the site shows something other than yours or sends visitors elsewhere, it is not an outage but an intrusion: see the guide to the hacked website.

First from elsewhere, then five links in order

The first step is accented: open the site from another network.

Figure 1 · The accented step is the first: open the site from another network, to know whether the fault is at your end or on the site. The next five go up the path of a visit, from the domain name to the application: you check what is furthest upstream first, because nothing works behind it.

From elsewhere. Open the site from your phone with Wi-Fi off, or ask someone outside the company. If it opens, the site is fine: the problem is in your network, your computer or your browser, which sometimes keep an old address in memory. If it opens nowhere, the outage is real. The domain name. It is rented by the year; its expiry date can be read in the registrar's customer area. If it has expired, everything stops, email too: see the guide to the domain name and, for mailboxes, the guide to professional email.

DNS. The name has to lead to the server's address; one deleted record or a change of name servers is enough to cut everything, and the correction takes from a few minutes to a few hours to be seen everywhere, depending on the caching time set in the zone. Hosting. The customer area tells you in a minute whether the account is suspended, the invoice unpaid or the disk full. The certificate. A click on the browser's warning gives its end date. The application. If everything else is in order, ask what changed the day before: an update, a plugin, a replaced file.

01

Where the visit stops: five links, five messages

The figure shows, for each link that breaks, how far the visit gets and what the visitor sees.

Figure 2 · Five links a visit crosses in order. Each row shows how far it gets when a link breaks, what the visitor then sees, and who has to act. The shorter the bar, the further upstream the cause. Messages as Chrome displays them; constructed example.

The path. To display a page, a visit crosses five links, always in the same order. The domain name first, which has to have been renewed. Then DNS, a hierarchical and distributed name service that provides a naming system for computers, services and other resources: it is what translates the name into an address. Then the server, rented from a host. Then the certificate, an electronic document used to prove the valid attribution of a public key to the identity of its holder: it is what puts the padlock in the address bar. Finally the application, meaning the site's code and its database.

Reading the figure. The shorter the bar, the further upstream the cause, and the more it takes down with it: an expired domain name cuts the site, email and everything carrying that name. Three people to call. The registrar for the name, the host for the server, the developer for the application; DNS and the certificate are managed by one or the other, depending on the set-up. Knowing which one to call saves hours. If you hold the access for none of the three, that is the first job, outage or not.

«The further upstream the cause, the more it takes down: an expired domain name cuts both the site and email.»
02

Reading the error message: it says where to look

The figure sets six messages against what they mean and the person to call.

Figure 3 · Six messages, from the furthest upstream to the furthest downstream. The first three come from the browser: the site was not reached, or not safely. The next three come from the server: it answered, with a three-digit code. Note the message word for word before calling.

The browser's messages. “This site can’t be reached”, with NXDOMAIN, means the name leads to no address: look at the domain name, then DNS. “Timed out” or “connection refused”: the name leads somewhere, but nothing answers. “Your connection is not private”: the server answers, it is the certificate that has expired or does not match the name.

The three-digit codes. They come from the server; those beginning with 5 indicate that the server is aware that it has encountered an error. Code 500 is a generic error message, given when an unexpected condition was encountered and no more specific message is suitable: look in the application. 502 and 504: the server was acting as a gateway and received an invalid response, or no timely response, from the machine behind it. 503: it cannot handle the request, because it is overloaded or down for maintenance. 404: the requested resource could not be found, which concerns one page, not the site. 403: the request was valid, but the server refuses action. Some content management systems spell it out as “error establishing a database connection”: then it is the database to look at.

03

An outage lasts mostly as long as it takes to find out

The figure runs the same outage twice, without monitoring and then with a test every minute.

Figure 4 · The same outage, twice: a certificate that expires on a Friday at 11 pm. Without monitoring, you hear about it on Sunday morning from a customer, and the site stays down for 35 hours. With a test every minute, the alert goes out three minutes later, and everything is restored in 45 minutes. Times, delays and visits are a constructed example.

The example. A certificate expires on a Friday at 11 pm. Without monitoring, nobody knows for 33 and a half hours: it is a customer who calls on Sunday morning. It takes another hour and a half to find who to call and repair. Total: 35 hours down and, at five visits an hour, about 175 visitors facing a security warning. With a test every minute, the alert goes out at 11.03 pm and the site is back at 11.45 pm.

What monitoring does. Website monitoring is the process of testing and verifying that end-users can interact with a website as expected. In practice, a robot placed outside your network opens the real page every minute, checks that an expected text is there and measures the response time; after three failures in a row, it warns two people. It also follows two dates, the certificate's and the domain name's, and alerts thirty days before. A reference point. An availability of 99.9 % over the year leaves about 8 hours 46 minutes of downtime; 99 %, a little over three and a half days. Ask your host which one it commits to. A site that is slow without being down calls for another diagnosis: see the guide to the slow application.

«An outside test repairs nothing; it turns a weekend outage into a three-quarter-hour incident.»
04

What keeps a site up, in five layers

The accented layer is monitoring.

Figure 5 · The accented layer is monitoring: without it, the other four give way silently. The first three are due dates and accounts to keep in the company’s name; the fourth is a way of updating; the fifth says, every minute, whether the whole thing holds.

Name, DNS, hosting. The accounts are in the company's name, with two up-to-date contacts; renewal is automatic and an alert goes out sixty days before the due date. The server's disk and memory are followed, and backups leave the server, as in the guide to backups. The certificate. Let's Encrypt certificates are valid for 90 days by default and, according to the public information about the organisation, it plans to reduce that period to 64 days from February 2027; the forum that brings together certificate authorities and browsers approved in April 2025 a reduction of certificate lifespans down to 47 days by 2029. A renewal done by hand no longer holds: it has to be automatic, and the automation itself has to be watched.

The application. An update is first tried on a copy of the site; a rollback takes one action; the error log is read, not just filled. Monitoring. Without it, the other four layers give way silently. All of this belongs to the routine upkeep described in the guide to managed IT.

05

The first hour, minute by minute, in 2027

One hour in the example, whose first five minutes decide the rest.

  • What the manager receives: the list of the five links with, for each, who manages it, where the access is and what the next due date is; and, after each outage, the time, the cause and the fix.
  • What the company no longer does: hear about the outage from a customer, call the developer about an expired domain name, renew a certificate by hand, hunt for a password on a Sunday.
  • What is measured: minutes of downtime per month, time between the outage and the alert, time between the alert and the return, days left before the certificate and the domain name end.
  • What Symloop does: the diagnosis and getting the site back up, taking the access back in the company's name, automatic renewals, monitoring with alerts, updates and, when the site justifies it, its move to hosting that is looked after.
Figure 6 · One hour in the example. The accented period is the first: five minutes to note the message and check from another network, which avoid calling the wrong person. Not every outage fits into an hour; the ones that last are often those for which nobody holds the access.

Minutes 0 to 5. The message, the time, a try from another network: you already know whether the fault is at your end, and which link to look at. Minutes 5 to 15. The domain name and DNS: a date, a few records. Minutes 15 to 30. The host: the customer area, then a ticket quoting the exact message and the time.

Minutes 30 to 50. The certificate is renewed, the last update is rolled back, the error log is read. Minutes 50 to 60. The site is opened from two networks, a form is tried, customers are told, and the cause is noted with what will avoid it. Not every outage fits into an hour; the ones that last are often those for which nobody holds the access.

My website has stopped working, where do I start?
Note the error message word for word and the time, then open the site from your phone on 4G. If it opens, the fault is in your network or your computer. If not, check in order the domain name, DNS, hosting, the certificate, then the application.
Why does my site no longer display when it worked yesterday?
Because a due date has passed or something has changed. The due dates: the domain name, the hosting invoice, the certificate. The changes: an update, a plugin, a modified DNS record. The error message says in which family to look.
How do I know whether the problem is my computer or the site?
By opening the site from another network: your phone on 4G with Wi-Fi off, or a person outside the company. If it opens elsewhere, the site is fine. The problem is then at your end: browser memory, office network, firewall.
What does “This site can’t be reached” mean?
That the browser did not reach the site. With NXDOMAIN, the name leads to no address: expired domain name or modified DNS zone. With “timed out” or “connection refused”, the name leads to a server that does not answer: see the host.
What does “Your connection is not private” mean?
That the site's certificate has expired, or does not match the name. The site itself works, but the browser refuses to display it without a warning. The certificate has to be renewed, and then you need to understand why the automatic renewal did not happen.
What do errors 500, 502, 503 and 504 mean?
That the server answered, and is aware that it encountered an error. 500: an unexpected condition in the application. 502 and 504: it was waiting for an answer from another machine, received invalid or too late. 503: it is overloaded or down for maintenance.
My site is down and the agency that built it no longer answers: what do I do?
Contact the registrar and the host directly: they hold the name and the server, and can hand control back to the legitimate holder. Gather what proves the site is yours. Then have every access taken back in the company's name.
Who do I call: the host or the developer?
The message tells you. Name not found: the registrar. Server not answering, errors 502 to 504, certificate: the host first. Error 500, blank page, database error after an update: the developer.
My email has stopped working too: is it related?
Often, yes. If the site and email go down together, the cause is upstream: the domain name has expired, or the DNS zone was modified. If email works and the site does not, look further down: hosting, certificate, application.
How can I be warned when the site goes down?
With an outside test that opens the page every minute and warns two people after a few failures in a row, by SMS and by email. The same tool follows the end date of the certificate and of the domain name, and alerts thirty days before.
Send us the site's address, the error message word for word and the time: we tell you which link gave way and who has to act

A site that no longer displays, a security warning, an error 500, an agency that cannot be reached, or a founder in France hearing it from a customer: we get the site back up, and from then on you will know before they do

Diagnosis, getting the site back up, access taken back in the company's name, automatic renewals, monitoring every minute with alerts. We work from Algiers and Sétif, in French, Arabic and English.