Security Website backups on Armenian hosting: what hosts copy and how to test restoration
What Armenian hosts say about backups, what their terms leave out (liability capped at 10,000 and 100,000 ֏), and how to verify your site can be restored.
Cookies on this site
The site stores what it needs itself: your theme, your animation setting and this choice. Analytics, marketing and external services switch on only with your consent. You can change your mind at any time. More about cookies
Security
If your website’s server password has ever been shared on Telegram, Viber, or WhatsApp, consider it known to everyone who has ever worked on your site. Switch from password logins to SSH keys: each person gets their own key, and cutting off someone’s access is as simple as deleting a single line.
This is a common story for small businesses: one freelancer builds the website, another takes over, then a friend of a friend steps in. Each one receives the exact same administrator password. Three years later, no one can tell you how many people have it. Meanwhile, automated bots are trying to guess it around the clock.
Between October 25 and 30, 2026, I counted the failed logins on the server of a client we took on for maintenance: 53,309 password attempts in six days. That is about 9,000 attempts a day, coming from 918 different IP addresses.
The server is located in Armenia and is completely ordinary; attackers were not specifically targeting it. Bots simply scan every IP address on the internet in sequence and try standard usernames. Most often, they tried ubuntu (3 871 times), admin (1 178), user (788), deploy (584), and test (406). The size of your business has nothing to do with it.
Over those same days, there were 1 341 successful logins to the server. Every single login used an SSH key, and not one used a password.
Sit down and write out your answers. If you do not know the answer, that is an answer in itself.
Who knows the password to your server or hosting control panel? Think back to everyone who built the site, edited it, or ran ads.
Where is this password stored? Look through your messaging apps and email. Chat histories keep passwords for years. If a former contractor loses their phone or has their account hijacked, your password goes right along with it.
What happens if you have a falling out today with the person who manages your website? Can you log in on your own without asking them? Are the domain and hosting registered in your name or theirs?
The answer depends on where the website is hosted.
| Where the website is hosted | Login type | What to do |
|---|---|---|
| Regular hosting with a control panel (cPanel, FastPanel, and similar) | Control panel username and password | Change the password, enable two-factor authentication if the panel supports it, and set up a separate account for the contractor |
| Dedicated server or VPS | SSH, often with the host’s default administrator password | Switch to keys, as described below |
| Website builder (Tilda, Wix, and others) | Builder account | Add the contractor as a project collaborator if your plan allows it, and never share your main password |
Protect access to your domain registrar account separately and most strictly of all. This applies to .am domains too: whoever controls the domain controls both the website and every email address on it. That is why your registrar account should always be in your name or your company’s name.
An SSH key is a pair of files. One stays on the developer’s computer, and the other sits on the server. You can safely send that second file over Telegram: without the first file, it unlocks nothing. A key like this cannot be guessed by brute force.
This is the main benefit for a business owner. The contractor sends only their public file to you or your system administrator. When the work is done, you simply delete their single line from the ~/.ssh/authorized_keys file. You do not have to change passwords, everyone else keeps working as usual, and the server logs show who logged in if each user has their own account.
Do not assume keys are bulletproof. The key file could still be stolen along with a laptop, which is why developers protect it with a passphrase. But it completely shuts down the nonstop automated brute-force attacks running every minute.
Ask the person who maintains your website to handle this. If you manage the server yourself, follow these steps in order:
ssh-keygen -t ed25519, with a passphrase.ssh-copy-id имя@адрес-сервера.PasswordAuthentication no and PermitRootLogin prohibit-password.sudo sshd -t, then apply them: sudo systemctl reload ssh.sudo sshd -T | grep passwordauthentication, log in from a new window, and only then close the old one.If you complete step 4 before step 3, only your hosting provider will be able to log in using the emergency recovery console. If you skip step 6, you could easily make a mistake: another setting might be sitting in the /etc/ssh/sshd_config.d/ folder, and the main file does not always override everything.
Make a checklist and run through it that same day. Remove their key from the server. Revoke their access to your hosting control panel, website admin panel, Google Search Console, Google Analytics, and ad dashboards. Change anything they could have seen: database passwords and payment gateway API keys. If your website takes payments via a bank or Idram, those keys are particularly sensitive; regenerate them in your merchant portal.
One more thing: it is best to include this requirement in the contract from the start: access is granted only through individual accounts, and everything is handed over to the client once the work is finished. Any reputable developer will agree to this without hesitation.
We can set this up as part of our website maintenance service. If you are not sure how access to your website is currently configured, write to us: we can review it together and figure out where to start.
/var/log/auth.log log of the client’s server we took on for maintenance, from October 25 to 30, 2026: our own count.Your site stays online and up to date while you work: monitoring, backups, updates and changes are on us.
Talk to us
Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.
Animation is off because your system asks for reduced motion.