Skip to content

Website security checklist for small businesses: what to fix first

18 Nov 2026

·

9 minute read

A small business website needs ten things in roughly this order: encrypted connections everywhere, software kept up to date, a protected admin login, backups you have restored at least once, forms that resist bots, security headers, email that cannot easily be forged, monitoring, a published security contact, and a record saying who may issue your certificates. Each item below comes with a test you can run in a minute. We ran the whole checklist on our own site, elrootlabs.com, the day after moving it to a new host. Of the nine items we could test from outside, it passed four, partly passed one and failed four. We fixed the two encryption failures and published a security contact that evening. The failures are the useful part, because they are easy to miss on any site, and one of ours was hidden by our own test.

Our own results first

CheckResult on elrootlabs.com
Modern encryption only (TLS 1.2 and 1.3)Fail: TLS 1.0 and 1.1 still accepted. Fixed the same day
Plain HTTP sent to HTTPSFail: the site answered over plain HTTP. Fixed the same day
HSTS, which tells browsers to use HTTPSPass, though not yet on the browsers' preload list
Security headersPass
Admin area protected outside the websitePass
Contact form protected against botsPass
Backups and restore windowPass
Uptime monitoringPass
Email authentication (SPF and DMARC)Partial: DMARC set to monitoring only
Security contact (security.txt) and certificate authority record (CAA)Fail: neither published. security.txt added the same day

We ran these checks with standard command-line tools on 17 November 2026, and re-ran the encryption checks that evening after finding a mistake in our first test. The sections below go through each, in the order we would fix them on a small business site.

1. Encrypt every connection, and send plain HTTP to HTTPS

Your site should only be reachable over HTTPS, using current versions of the encryption protocol. TLS 1.0 and 1.1 are formally deprecated by RFC 8996, so a site should accept only TLS 1.2 and 1.3.

Our first test said our site refused TLS 1.0 and 1.1. It did not. The refusal came from the testing tool: current versions of OpenSSL switch those protocols off on their own side, so the connection failed before our server was even asked. When we lowered the tool's own security level (-cipher DEFAULT:@SECLEVEL=0), the server accepted both. We only noticed because our host's dashboard showed the minimum version as TLS 1.0, which contradicted the test. A failed connection tells you something about the server only if the client was willing to try. We raised the minimum to TLS 1.2 in the host's settings, and the same test now gets a refusal from the server itself.

Our site also answered plain, unencrypted HTTP with the full page, and the www address typed with plain http redirected to the plain HTTP address. Visitors who type the address or follow an old link can land on an unencrypted page. Our site already sends an HSTS header, which tells browsers to use HTTPS from then on, but the HSTS standard has browsers ignore that header when it arrives over plain HTTP, so it does not protect a first visit. On most hosts the fix is a single setting, often called "Always use HTTPS" or "Force HTTPS". We turned ours on the same evening, and every plain HTTP address now gets a permanent redirect to its HTTPS version, with the page path kept.

Test it yourself: type your address starting with plain http and no s. The browser should always end up on the https version, for both the bare domain and the www version. For the protocol versions, use a free online TLS checker, or lower your own tool's restrictions as above, so that any refusal comes from your server and not from your computer.

2. Keep the software up to date

Most small business sites run on a content management system, a theme and a set of plugins, and each of them gets security updates. Attackers scan for sites running versions with known flaws, because those flaws are published along with the fixes. Turn on automatic updates where your platform allows it, delete plugins you do not use, and check monthly for anything that stopped updating.

Test it: log in to your site's admin area and look for pending updates. Anything waiting more than a week is a risk.

3. Put the admin login behind more than a password

The admin area is the front door. At minimum, use a unique, long password and turn on two-factor authentication. Better still, put the admin area behind a separate identity check that the website code cannot bypass. Ours sits behind a check run by our hosting provider that sends a one-time code to an approved address before the admin page even loads.

Test it: open your admin login page in a private browser window. If it loads straight to a username and password box, anyone on the internet can try passwords against it.

4. Back up, and restore once to prove it works

The UK's National Cyber Security Centre puts backing up your data first in its Small Business Guide. Two details matter more than the backup itself: keep copies somewhere separate from the website, and restore one at least once, because a backup nobody has restored is a hope. Ours exports the enquiries database every morning and keeps each copy for 90 days, and the database host keeps seven days of point-in-time history on top.

Test it: ask whoever runs your site when they last restored a backup, and how long it took.

5. Protect every form from bots

Contact and signup forms attract spam, and an unprotected form can also be used to flood your inbox or your database. Ours checks that a submission came from our own pages, limits repeat submissions from the same email address and runs a bot check before anything is saved. A free challenge service from a major provider covers most of this for a small site.

Test it: submit your own contact form twice quickly with the same details. A protected form refuses or slows the second attempt.

6. Send the security headers

Security headers are instructions your server sends with every page, telling the browser what is allowed: which scripts may run, whether other sites can frame your pages, and so on. Ours sends all of the common ones, including a Content-Security-Policy, which limits where scripts can be loaded from. A free online header scanner shows which ones your site sends.

Test it: run your address through a header scanner and look for Content-Security-Policy, Strict-Transport-Security, X-Frame-Options and X-Content-Type-Options.

7. Stop people sending email as you

Your domain's email settings decide whether someone else can send mail that appears to come from you. SPF lists who may send for your domain, and DMARC, defined in RFC 7489, tells receiving servers what to do with mail that fails the checks. Ours has SPF in place, but its DMARC policy is p=none, which means monitor only: forged mail is reported but still delivered. That is the right starting point while you confirm that all your real mail passes, and the plan is to tighten it once the reports show it does.

Test it: look up your domain's DMARC record with any free DNS lookup tool. No record at all, or p=none left in place for months, is the gap to close.

8. Get told when the site goes down

You should hear about an outage from your own monitoring, not from a customer. Ours loads the homepage and the contact page every 30 minutes and emails the owner after three failed attempts in a row. Free uptime services do the same for any site.

Test it: ask yourself how you would find out if your site went down at 2 am on a Saturday.

9 and 10. Publish a security contact and lock down certificate issuance

Two small records round off the list, and we were missing both. A security.txt file, standardised in RFC 9116, tells anyone who finds a problem with your site how to report it to you; without one, a well-meaning person may not bother. A CAA record, defined in RFC 8659, names which certificate authorities may issue certificates for your domain, which narrows one route to impersonating your site. Each takes minutes to add. A security.txt needs only two fields: a Contact line, such as an email address, and an Expires date, which the standard recommends keeping less than a year ahead. We published ours the same evening, with the same public email address as our contact page, and added a weekly automated check that starts failing 30 days before the date runs out, so the file cannot quietly go stale. Our CAA record is still to come.

Test it: open /.well-known/security.txt on your domain, and look up your domain's CAA record in a DNS lookup tool.

What a monthly website care routine should cover

Most of this list only needs setting up once. What needs doing every month is short: apply updates, check the backup ran and that one restores, read the uptime and DMARC reports, and look at the admin accounts for anyone who should no longer have access. Re-run the full checklist after any change of host, theme or developer, because that is when settings get lost.

If you would like your site checked against this list, or the gaps fixed, get in touch. We also measure speed, which is often the other thing a move breaks: see how we took our own homepage from 51 to 88.

AI tools

Ask ChatGPTAsk Claude

Start with the problem that matters