Guide / 22 November 2026
Is my business website secure? A 15-minute self-check
In about a quarter of an hour you can find out whether your company website has the basics in order: HTTPS, up-to-date software, protected admin accounts, working backups and protected email. What cannot be seen from the outside, such as real weaknesses in the application, only an audit will show.
The short answer: work through the list below, run the free website check for the public signals, and write down everything you are not sure about. Each "I don't know" is a point to raise with your IT provider. If the site holds customer data, orders or user accounts, a checklist is not enough; that is when an audit that proves what is real makes sense.
The checklist for business owners
Most of these points need no technical knowledge. Some are questions for whoever built or hosts your website.
- HTTPS and the certificate. Open the site in your browser and check that the address starts with https:// and that there is no warning. Ask who looks after renewing the certificate and whether renewal is automatic.
- The redirect from http to https. Type the address with http:// in front. The site should send you to the https:// version on its own. If it stays on http://, anything sent through its forms may travel unencrypted.
- The admin page. Try the usual address for your platform, for example /wp-admin on WordPress. If the sign-in page opens for anyone on the internet, ask whether access can be restricted, or at least protected with two-step verification.
- Platform and plugin versions. Ask for the list: which platform the site runs on, which version, which themes and plugins are installed and when each was last updated. Plugins that no longer get updates from their author are a risk even if they seem to work.
- Who has an admin account. Ask for the list of accounts with admin rights. Everyone should have their own account, former staff and contractors should be gone, and every account should have two-factor authentication (2FA) switched on.
- Backups and a restore test. Ask where copies of the site and its database are kept, how often they are made and when one was last restored as a test. A backup that has never been tried is an assumption, not a safety net.
- SPF and DMARC for email. These DNS records tell mail servers who may send for your domain and what to do with forged mail. Without them, anyone can send fake invoices that appear to come from your company.
- Forgotten sites and sub-sites. Think of old campaign sites, test shops, competition pages or trial versions such as test.yourcompany.com. They often stay online, unpatched, and can be a way in.
- Staff accounts in data leaks. Company email addresses sometimes turn up in databases stolen from other services. Ask whether anyone has checked, and whether staff reuse the same password in several places.
What the free check shows
The free check reads public signals only, the same any browser sees, plus public DNS records. It covers points 1, 2 and 7 of the list:
- whether the certificate is valid, when it expires and whether http:// sends visitors to https://;
- which security headers are missing and whether the server shows its software versions;
- SPF, DMARC and DKIM under common selector names, plus MX and CAA.
Use it only for your own company's domains, or ones you are allowed to check. We do not keep the domain you check.
What a self-check cannot see
The list above tells you whether basic hygiene is in place. It does not tell you whether someone can actually get in. Some things that stay invisible without testing:
- mistakes in the code of the site or web app, of the kind attackers try first;
- configuration files, database copies or the developer's working folders left public on the server;
- keys and passwords left in the site's JavaScript or in public code repositories;
- services running on the server on ports other than the website's;
- sub-sites pointing at a service you no longer use, which someone else could take over;
- which published weaknesses really affect you, and which are being exploited right now.
A scanner versus a proven audit
An automated vulnerability scan is a useful first step, but it has clear limits. The main difference is between "possible" and "proven".
| Automated scan | Audit with evidence | |
|---|---|---|
| What you get | A list of possible problems, often with many false alarms | Checked findings, each with evidence and a confidence level: proven, confirmed, possible or not affected |
| Order of fixes | By the generic severity score | A plan ordered by risk, with the effort for each fix |
| What was not checked | Usually not mentioned | Listed separately as not checked, never as "clean" |
| Who it is for | The technical team | Management gets a plain-language summary, the IT team gets the detail |
When an audit makes sense
A website security audit makes most sense when:
- the site holds customer data, orders, payments or user accounts;
- the list above produced several "I don't know" answers;
- the site was built by someone you no longer work with;
- a large customer, a partner or a legal duty asks you to show that you take security seriously.
For a small company with one website and email, the audit starts at €1,000 before VAT and takes about a week from signed permission to report. You get a fixed quote before we start, a signed and dated report, a walkthrough call and one retest of the findings within 30 days. Your own team or IT provider makes the fixes.
An audit does not guarantee the site will never be attacked. It shows what was exposed on the day of testing and what to fix first. If you want the check repeated, monthly monitoring runs the scan again every month and tells you when something new appears.
What to do after the check
- Send the "no" and "I don't know" answers to your IT provider or whoever runs the site.
- Fix the quick wins first: updates, old accounts removed, two-step verification switched on.
- Book a test restore of your backup.
- Repeat the list after every major change to the site or a change of provider.
If you suspect the site has already been compromised, read the guide on what to do when a WordPress site is hacked.
Last updated: 22 November 2026.