Security 'Not secure' in browsers: what it means and how to fix it
A 'Not secure' warning means a website lacks HTTPS or has an invalid certificate. What to check, whether a free certificate works, and what banks require.
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
Armenian hosts treat backups differently: some include them in every plan, others only in the higher tiers, and none of the four I checked state retention periods or restoration steps on their pricing pages. In the general terms of two of them, liability for data loss is capped at 10,000 and 100,000 ֏ per incident. So test a restore yourself at least once instead of trusting a “backups included” line.
On November 4, 2026, I went through the websites of four providers and wrote down everything they say about backups. All of these are public pages; the links are at the end.
| Provider | What they say about backups | What is missing from the page |
|---|---|---|
| HayHost, English cPanel pricing page | “Weekly full back-ups”, and “Free Backup” under free features. The Armenian homepage mentions nothing about backups | Retention period, restoration procedure |
| Web.am, hosting page | Backups are included in Mail-on-host, Simple, Standard, Master, and Profi plans; not included in Mail-on-web and Light | Frequency, retention period, restoration procedure |
| Name.am, homepage | Paid plans include JetBackup. The site says that all data, including servers, is backed up to the cloud every day. JetBackup isn’t available on free hosting | Retention period, and whether you restore the backup yourself or through support |
| Reg.am, homepage | “Անվճար արխիվացում”, which means “free archiving” | What exactly is archived, how often, how to restore |
The table shows two things. First, the cheapest plan may have no backups at all: Web.am leaves them out of Light and Mail-on-web. Second, “backups included” doesn’t tell you how far back you can go. With weekly backups, as on HayHost, a crash on a Friday could cost you up to seven days of orders and site edits.
The terms you accept when you order sit in a separate PDF. I read the general terms of HayHost (operated by ProITLab) and Reg.am (Global AR LLC). In both, clause 11.1 says the provider is liable only for actual damages, and only if it is at fault itself. HayHost caps liability at 10,000 drams per incident, Reg.am at 100,000 drams. Clause 11.2 in both: the provider doesn’t compensate for lost profit. I found no mention of backups in these general terms. There may be service schedules outside the PDF, so ask support.
This is my reading, not a legal opinion: hosts sell server space, and their contracts don’t promise that your data is safe. A backup mentioned on a pricing page is marketing until the promise is written into the contract or confirmed in an email from support. If your site takes orders, get it in writing.
Send these questions by email so you have a written record:
If the answer to question four is “support,” ask whether that applies only during business hours and how quickly they reply.
Download a backup yourself. In the HayHost dashboard, go to “Backup”, then “Download a Full Account Backup”, then “Generate Backup”; the file then appears under “Backups Available for Download”. The guide doesn’t say what’s inside the archive, so open it and look for both the site files and the database dump.
Deploy the backup on a test domain hidden from search engines, never directly over the live site. Open the homepage in every language, submit a test form, log in to the admin panel, and look for the latest entry. Here’s how to read what you see:
| What you see | What it means |
|---|---|
| Pages load, but text and images are blank | The backup contains files, but no database |
| Recent entries or orders are missing | The backup is older than you thought |
| Locked out of the admin panel | The database was only partially restored |
Write down how many hours it took and who did what. That’s your real downtime, and you want to know it before an outage, not after. For what to do when a site is already broken or hacked, see site was hacked.
Don’t restore over the broken version until you’ve saved its current state: it may contain recent orders that aren’t in the backup. Message hosting support with the exact time the site went down, and ask for the timestamp of the newest backup and where it’s stored. Restore to a test domain, check it against the table above, and only then point your live domain at it. If the downtime came from a hack rather than a technical failure, a backup isn’t enough: you have to close the vulnerability, or you’ll be hit again tomorrow.
When backups run daily, the retention period is clear, you’ve tested a restore once, and losing a day of data won’t hurt your business. A simple brochure site with no forms that you update once a year fits: download a full archive after every edit and keep it on your own computer.
Backups are part of website maintenance: we back up the site and database on a regular schedule, so a working version can be brought back after a failure. Maintenance starts at 20,000 ֏ a month. I earn money from this, so check what your host provides first. If backups run daily and you’ve tested a restore, you don’t need a maintenance plan just for backups. If we didn’t build your site, I first check whether backups exist and which server they’re on, then tell you what’s missing.
This article describes contract terms and isn’t legal advice. If your revenue depends on your website, have a lawyer read your hosting agreement.
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.