Website Down or Hacked? What to Check First in Zimbabwe

Your website is down, or a page you did not create has appeared on it, and every minute it stays that way is a minute a customer spends on a competitor instead. Before you pay anyone to fix it, work through the checks below in order, cheapest and fastest first. This is for the owner staring at a broken site right now, often a site built by someone who is no longer answering the phone. If that sounds familiar, our guide to choosing a web developer in Zimbabwe without getting burned will help once the immediate problem is solved. Most outages are not a dramatic break-in, and several common causes need no developer to resolve once you know what you are looking at.

The goal here is simple: find out what is actually wrong before money changes hands, and know the exact point at which you should stop poking and call for help.

TL;DR

• Rule out the common causes first. A dead office connection, an expired .co.zw domain, or an unpaid hosting bill all look like "the website is broken" and none of them needs a developer.
• A "not secure" warning is usually an expired certificate, a renewal task, not proof of a hack.
• If it is a real compromise, the three answers that decide your recovery are: who controls the hosting account, whether a backup exists, and whether your passwords have been changed.
• Stop and get help the moment you find signs of a break-in and cannot restore a clean backup yourself.

Work through it in this order

Go down this list and stop at the first check that explains the problem. Each step is cheaper and faster than the one below it, so there is no reason to jump ahead.

1. Confirm it is actually down. Open the site on your phone using mobile data, not the office WiFi, and ask someone on a different network to try it too. If it loads for them, your site is fine and the fault is local.
2. Check the domain has not expired. A .co.zw or .com address that lapses will take the whole site offline on the renewal date, with no warning to visitors. Log in to wherever the domain is registered and look at the expiry date.
3. Check the hosting is paid and active. Hosting is a separate bill from the domain, often with a different provider. An unpaid or suspended hosting account takes the site down just as completely.
4. Check the security certificate. If the site loads but shows "not secure" or a broken padlock, the SSL certificate has almost certainly expired. This is a renewal, not a rescue.
5. Look for signs of a real compromise. Pages you did not create, a redirect sending visitors to another site, spam text on your pages, or a Google warning in the search result. If you see these, treat it as a hack and go to the recovery steps below.

If steps one to four explain it, you are done without paying a developer for an emergency rescue. If step five is where you land, keep reading.

Is it down, or is it just you?

This sounds obvious, and it is still the single most common false alarm. Office routers, a lapsed data bundle, a cached old version in your browser, or a local network fault all produce the same symptom: the site will not open for you. Before you conclude anything, open it on a phone on mobile data and get one other person, ideally on a different network, to open it as well. If it works anywhere else, the website is up and you have saved yourself an emergency call.

Has the domain or hosting simply lapsed?

In Zimbabwe this is where a large share of "my website disappeared" cases actually end. A domain and its hosting are two separate things, frequently paid to two different companies on two different dates, and either lapsing takes the site offline.

The complication is who holds those accounts. If a developer registered the domain and set up the hosting on your behalf, the renewal notices go to them, not to you, and a site can vanish because an invoice you never saw went unpaid. Two things are worth knowing before an emergency, not during one: which company the domain is registered with, and whether the hosting sits inside your own account or inside a developer's reseller account that bundles many clients together. If it is inside a reseller account, you cannot fix a billing lapse yourself, and getting back online depends entirely on reaching that person. Our guide on who is responsible for your domain, email and hosting walks through how that split usually works.

If the site loads but feels broken rather than absent, slow or half-loading on mobile data, that is a different problem with a different fix, covered in why your website is slow on Zimbabwean mobile data.

Signs your website has been hacked

A genuine compromise looks different from an outage. The site is usually still online, but wrong. The common signatures are a defaced homepage, pages of content in another language, a redirect that bounces visitors to a gambling or pharmacy site, links you did not add, or a red warning screen from Google saying the site may be dangerous. If you have a security plugin or your host emails you an alert, that counts too.

If that is what you are seeing, resist the urge to hand it to the first person who answers. What you check first matters more than who you call first.

What to check before you pay anyone

Three answers decide how quickly, and how cheaply, a compromised site comes back. Get them before you authorise any work.

• Who controls the hosting account? Whoever has the real login can take the site offline, restore it, and change passwords. If that is you, good. If it is a developer's reseller account, your recovery moves at the speed of whoever holds it, and that is worth knowing immediately.
• Is there a backup, and how old is it? Ask your host whether automated backups exist, what date the most recent one is, and whether a restore has ever actually been tested. A recent, clean backup turns a frightening hack into a thirty-minute rollback. A backup nobody has ever restored is a guess.
• Have the passwords been changed? Change the email password first because email can reset the other accounts, then change the site admin password and any hosting password you control. If the hosting sits in a developer's reseller account, ask the account holder to change it immediately. If an attacker still has the keys, any repair can be undone the same day.

Notice that none of these three is "pay an emergency specialist." They are the questions any competent helper will ask you first anyway, and having the answers ready is what stops an urgent situation from becoming an expensive one.

When to stop and call for help

Handle the obvious causes yourself. Renew a domain, settle a hosting bill, or wait for a certificate reissue: none of that needs a developer. Stop and bring in help at a clear line: you have confirmed real signs of a compromise, and you cannot restore a clean backup on your own, or you cannot even establish who controls the hosting. At that point you are not buying a quick fix, you are buying safe access and a proper clean-up, and it is worth doing once, properly, rather than paying several people to guess.

One thing this article deliberately does not cover: recovering a site from a developer who has gone silent and is holding your domain or logins hostage. That is an ownership and access problem, not a security incident, and it has its own steps in how to get control of your website back.

Your next step

Down for everyone, or just showing a certificate warning? You can very likely handle it yourself with the checks above, without paying a developer for a rescue. Facing real signs of a break-in with no backup you trust, or no idea who holds the hosting? That is the moment to get a hand rather than keep guessing. Either way, once you are back online it is worth closing the gap that let it happen, usually a missing backup and unclear account ownership, so the next scare is a five-minute fix instead of a lost week.

If you are stuck at that line, talk to TechTribe and we will help you get back online and set things up so an outage stays a small problem.

---

Author: Simon Published: August 2026