Blog
Hosting, the Padlock, and Getting Your Website Back
The previous post in this library covered your website as software: updates, plugins and logins. This one covers the ground it stands on: where the site is hosted, the padlock in the browser bar, and whether you could get the site back if something went wrong.
These are the parts owners tend to know least about, because they were set up once, years ago, by someone else. They're also where a few simple questions can save a lot of trouble.
Where does your website actually live?
Your website runs on a server somewhere, owned by a hosting company. Hosting comes in roughly three flavors:
- Shared hosting: your site shares a server with many others. It's inexpensive and fine for simple sites, but you have limited control, and the quality of security varies a great deal between providers.
- Managed hosting: the host specializes in a platform such as WordPress and handles updates, backups and some security for you. It costs more and does more.
- Your own server or cloud account: maximum control, and maximum responsibility. Someone on your side has to patch and watch it.
There's no single right answer. What matters is knowing which one you have, and what the host does versus what's left to you.
The accounts that matter more than the website
Three accounts sit underneath your website, and each one can take it away from you:
1. The domain registrar. This is where you rent your domain name (yourcompany.com). Whoever controls this account can point your website and your email anywhere. It deserves MFA, a company-owned login, and auto-renew turned on with a current payment card. Ask whether "registrar lock" is enabled, a setting that blocks unauthorized transfers.
2. The DNS host. DNS is the internet's phone book: it tells the world where your website and email live. Often it's the same company as the registrar, but not always. Control of DNS means control of where your site and your mail go.
3. The hosting account. Where the site's files and database live.
When I ran IT at a company of about 200 people, the scariest moments with websites were almost never break-ins. They were near misses with renewals and ownership: a domain registered years before under a former employee's personal email, a card on file that had expired, a hosting account only an outside agency could log into. Each was easy to fix once found. The trick is finding them before they become emergencies.
The padlock: what TLS does and doesn't mean
The padlock in the browser bar, and the "https" at the start of the address, mean the connection between the visitor and your site is encrypted. The technology is called TLS (sometimes still called by its old name, SSL). It relies on a certificate, a small file that proves the site is really yours and expires on a schedule.
What the padlock means: nobody between the visitor and your site can read or change what's sent, such as contact-form details or login passwords.
What it doesn't mean: that the site itself is safe or well maintained. Criminal sites have padlocks too.
Three things to check
- Every page uses https, and anyone who types the plain "http" address is automatically sent to the secure version.
- The certificate renews automatically. Free certificates from services like Let's Encrypt are designed to renew automatically, and most hosts handle this for you.
- Someone notices if renewal fails. An expired certificate gives visitors a full-page browser warning, which looks to customers like your site has been hacked.
Certificates are getting shorter
The industry body that sets the rules for these certificates, the CA/Browser Forum, has approved a schedule that cuts the maximum certificate lifetime from 398 days down to 47 days, in steps from March 2026 to March 2029. If anyone at your company or your agency still renews certificates by hand once a year, that process won't keep up. Ask now whether renewal is fully automatic.
Security headers, briefly
Your web server can send instructions to visitors' browsers along with every page. These are called security headers. They tell the browser, for example, to always use the secure connection, or to refuse to let your site be embedded invisibly inside someone else's page. They're a quick configuration change for your developer or host, and they're one of the things outside security scans look at. You don't need to know the details; just ask whether they're set.
Could you get the site back?
This is the question I'd ask before any other. If the site were defaced, infected or accidentally deleted tomorrow, how long would it take to get it back, and who would do it?
A website backup needs two parts: the files (the design, plugins and uploaded images) and the database (the pages, posts and settings). A backup that has one without the other isn't a complete backup.
Good questions for your host or developer:
- How often is the site backed up, and how many days of copies are kept? If an infection goes unnoticed for two weeks, a three-day history won't help.
- Where are the copies stored? A backup on the same server as the site can be lost along with it. At least one copy should be somewhere else.
- Who can restore it, and how long does that take? Ideally, someone has actually done it.
- Do you have a copy you control? If the relationship with the host or agency ends badly, you want your own recent copy.
What to do Monday morning
- Find out which company hosts your website and which type of hosting it is, and get the company's own login to the hosting account.
- Check the domain registrar account: company-owned email, MFA, auto-renew, a current card and registrar lock turned on.
- Confirm certificate renewal is automatic, and ask who gets alerted if it fails.
- Ask how the site is backed up: files and database, how often, how long copies are kept, and where they're stored.
- Ask when someone last restored the site from backup, and get a copy you control.