- Every MSP website we could read uses HTTPS. But 128 of 241 send one of the six standard security headers or none, and only 19 send all six.
- 88 of 249 MSPs would not stop someone sending email that pretends to be from their domain: their DMARC is set to "none" or missing.
- WordPress sites were the weakest on headers: 99 of 140 send one or none, against 29 of 101 on other platforms.
- Firms showing Cyber Essentials were much better on email security, but no better on website headers or out-of-date plugins.
What we found
MSP website security is easy to check from the outside, and buyers do. When a business is choosing an IT provider, someone on their side will often check the provider's own setup. They might be a technical director, an IT-savvy finance manager or the outgoing provider. Free tools make it a two-minute job: paste in the website for its security headers, the domain for its email settings. What they find says something about how you'll look after them.
So we checked. We looked at the websites and email domains of 249 managed IT firms in 10 UK towns, all chosen at random. We only used passive checks: what any visitor's browser, or a public lookup, can see. We didn't test for weaknesses or try to get in.
The good news first: every website we could read uses HTTPS with a valid certificate, and almost all use the latest version of the encryption that protects it (TLS 1.3). The basics a browser enforces are done.
Past that, the picture is patchier than you'd expect from firms that sell security:
- 88 of 249 don't enforce DMARC. Their email policy is set to "none" or missing, so anyone can send email that claims to be from their domain.
- 130 of 241 show which version of their website software they run, which tells attackers exactly what to look for.
- 74 of 241 load at least one plugin or script library with a published security vulnerability.
- 13 of 241 publish a security.txt file telling researchers how to report a problem.
We don't name any firm, and we haven't tested anything we shouldn't. Where we found something serious, we're telling the firm concerned privately.
This piece uses two sets of data, and we keep them apart:
- The MSP Website Benchmark (50 firms, 9 November 2026). Its security results are in the main report.
- An extended scan of 249 MSP websites (12 to 13 November 2026) from the same 10 towns, with the same checks. 43 of the benchmark's 50 firms are in it.
Website checks are out of the 241 sites we could read; email and domain checks are out of all 249.
Website security headers: what most MSP sites are missing
Security headers are instructions a website sends to the visitor's browser. They tell it, for example, to only ever connect over HTTPS, not to let other sites frame the page, and which scripts it's allowed to run. They cost nothing, take minutes to add, and are the first thing a free security scanner grades.
We checked six:
| Header | What it does | Sites that send it (of 241) |
|---|---|---|
| Strict-Transport-Security (HSTS) | Tells browsers to only ever use HTTPS for your site | 109 |
| X-Content-Type-Options | Stops browsers guessing file types, a route for some attacks | 92 |
| Referrer-Policy | Limits what your URLs give away when visitors click links | 78 |
| Frame protection (X-Frame-Options or frame-ancestors) | Stops other sites putting your pages in a frame to trick visitors | 75 |
| Content-Security-Policy (CSP) | Controls which scripts and content can run on your pages | 68 |
| Permissions-Policy | Switches off browser features you don't use, like the camera | 57 |
Source: extended scan, 249 MSP websites in 10 UK towns, 12 to 13 November 2026.
Most sites send very few:
241 MSP websites, homepage response.
| Group | Count (of 241) |
|---|---|
| None | 83 of 241 |
| One | 45 of 241 |
| Two or three | 51 of 241 |
| Four or five | 43 of 241 |
| All six | 19 of 241 |
83 of the 241 sites send none at all. A buyer who runs your site through a free header checker will see a failing grade, and many of these tools show the grade in big red letters.
Why WordPress sites score worst
The platform makes a big difference. 99 of the 140 WordPress sites send one header or none, against 29 of the 101 sites on other platforms. 65 WordPress sites send none at all.
That's not because WordPress is insecure. Hosted website builders add some headers for you; WordPress leaves it to whoever runs the site, through the server, a security plugin or a service in front of the site. So headers are easy to forget.
A service in front of the site helps. 60 of the 100 sites behind Cloudflare send HSTS, against 49 of the 141 that aren't. Cloudflare can add HSTS with one setting, and the rest of the headers with a short rule.
How to add security headers
These values are a safe starting point for most small business websites:
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
X-Frame-Options: SAMEORIGIN
Permissions-Policy: camera=(), microphone=(), geolocation=()
Content-Security-Policy-Report-Only: default-src 'self'; report-uri /csp-report
Where to add them depends on how your site is run:
- Behind Cloudflare: turn on HSTS in the SSL/TLS settings, and add the others with a response header rule.
- WordPress on your own hosting: use a security plugin that sets headers, or add them in the server configuration (
.htaccesson Apache, the server block on Nginx). Ask your host if you're not sure which you have. - Hosted builders (Wix, Squarespace, Webflow): some headers are set for you and others can't be changed. Check what you have before trying to add more.
Two cautions. Only add includeSubDomains to HSTS if every subdomain you use works over HTTPS. And start Content-Security-Policy in report-only mode, as above: a strict policy can block chat widgets, analytics and forms until you've listed every source they load from.
Software on show, and out of date
Most websites run on software that needs updating: the content management system (CMS), its plugins, and the script libraries pages load. We checked what a visitor's browser can see.
- 130 of 241 sites reveal which version of their CMS they run, usually in a "generator" tag in the page code. It's a small thing, but it tells an attacker exactly which known weaknesses to try. It's also how we could check the next point.
- Of the 69 WordPress sites where we could compare the version, 18 were behind the latest release. 9 of them run a version that WordPress itself flags as insecure: it has security fixes they haven't installed.
- Of the 93 sites where we could see plugin versions, 56 run at least one plugin with a published vulnerability. That doesn't mean they've been hacked, or that the weakness can be used on their site. It means a fix exists and hasn't been applied.
- Of the 138 sites where we could see script library versions, 25 load at least one with a published vulnerability. Old copies of jQuery are the usual culprit.
Across all 241 sites, 74 run at least one component with a published vulnerability that we could see from outside. The real number is likely higher: most sites don't reveal every version, which is exactly why they shouldn't.
MSP email security: SPF, DKIM and DMARC
For an MSP, email security is the one that matters most. If your domain can be spoofed, a criminal can email your clients as you. That's an invoice-fraud and phishing risk to the people who trust you most.
Three DNS records protect a domain:
- SPF lists the servers allowed to send email for your domain.
- DKIM signs your outgoing email so receivers can check it wasn't forged or changed.
- DMARC tells receiving servers what to do with email that fails those checks: nothing (
p=none), send it to spam (p=quarantine), or reject it (p=reject).
Only a DMARC policy of quarantine or reject actually stops spoofed email. p=none just monitors.
249 MSP email domains. Only quarantine and reject stop spoofed email.
| Group | Count (of 249) |
|---|---|
| Reject | 67 of 249 |
| Quarantine | 94 of 249 |
| None (monitoring only) | 56 of 249 |
| No DMARC record | 32 of 249 |
| Check | MSP domains (of 249) |
|---|---|
| SPF record | 237 |
| DKIM found on a common selector* | 201 |
| DMARC set to quarantine or reject | 161 |
| All three in place | 148 |
| MTA-STS (forces encrypted delivery to you) | 31 |
| DNSSEC (protects your DNS answers) | 11 |
| CAA record (limits who can issue your certificates) | 11 |
*We can only find DKIM on the selector names most providers use, so the true number may be a little higher. Source: extended scan, 249 MSP domains, 12 to 13 November 2026.
So 88 of 249 MSPs don't enforce DMARC: 56 have it set to "none" and 32 have no record at all. Many will have started with "none" to monitor, as you should, and never moved on.
Most of these firms run their email on Microsoft 365 (133 of the 243 where we could tell), which makes enforcing DMARC straightforward. Even so, 40 of those 133 don't enforce it.
Is DMARC mandatory?
Not by UK law for a private business. But the big mailbox providers now expect it. Since February 2024, Google and Yahoo require SPF, DKIM and a DMARC record from anyone sending large volumes to their users, and Microsoft's Outlook.com followed in May 2025. A p=none record meets those rules, which may be why so many firms stop there. It doesn't stop anyone spoofing your domain.
Moving DMARC from "none" to "reject"
A DMARC record is one line of text in your DNS. A typical path looks like this:
v=DMARC1; p=none; rua=mailto:[email protected]
v=DMARC1; p=quarantine; rua=mailto:[email protected]
v=DMARC1; p=reject; rua=mailto:[email protected]
Start with p=none and read the reports for a few weeks. They show every service sending email as you, such as your helpdesk, invoicing and marketing tools. Make sure each one passes SPF or DKIM, then move to quarantine, and to reject once nothing legitimate is failing.
Does Cyber Essentials mean a more secure website?
Cyber Essentials is the UK government-backed certification most MSPs sell to their clients, and many show the badge on their own site. Does it go with better security on that site?
We split the 234 readable sites where the AI could tell whether a Cyber Essentials badge or claim was shown:
- Email: yes, clearly. About four in five firms showing Cyber Essentials enforce DMARC (94 of 117), against about half of those that don't show it (59 of 117).
- Website headers: no. About half in both groups send one header or none (57 of 117 with the badge, 68 of 117 without), and the difference wasn't clear.
- Out-of-date components: no. About three in ten in both groups load something with a published vulnerability (35 against 36).
- Cookies: the opposite. Firms showing the badge were more likely to load tracking cookies before the visitor agrees (88 of 117 against 71 of 117).
That fits what Cyber Essentials covers. It certifies a firm's own devices, network and accounts, not its public website. So a badge on the homepage says nothing about the homepage itself. A buyer who checks may notice the gap.
Whether a site shows Cyber Essentials was judged by AI from the page content. Two runs of the same model agreed on about 7 in 10 answers for fields like this, so treat these as broad patterns.
“Buyers can't see your internal security, but they can see your website and your email settings in two minutes. For a firm that sells security, those are the shop window. Getting them right takes an afternoon.”
Cookies: privacy on show too
Privacy is the other thing a buyer can check from outside, and it matters to MSPs that sell compliance. In the UK, advertising and tracking cookies need the visitor's consent before they're set. Since the Data (Use and Access) Act 2025, some analytics used only to improve your own site can run without consent, as long as visitors are told and can easily object (the ICO's guidance, April 2026).
- 164 of 241 sites load third-party tracking scripts before the visitor has made any choice. Some of these may be analytics that now fall under the new exception, but only if the site explains them and offers a way to object.
- 109 of 241 show no cookie banner or notice at all, and 69 of those still load trackers.
- 70 of 241 offer "Reject all" on the first layer of their banner, next to "Accept all".
The 50-firm benchmark found the same pattern on 9 November: 31 of 48 sites loaded trackers before consent.
Does any of this affect who Google shows?
No. We compared the 90 firms on Google's first page for IT support in their town with the 151 that weren't. On every security check in this piece, the two groups looked the same. Google doesn't reward or punish these settings directly.
The one exception is HTTPS. Google has used it as a ranking signal since 2014, though it describes it as a very lightweight one, and it still lists HTTPS as part of page experience. Every MSP site we could read already uses it, so it doesn't separate anyone here. It's the minimum: without it, Chrome labels your site "Not secure", which no buyer of IT services should see.
That's the point. Website and email security isn't an SEO tactic. It's what a prospect, a client's auditor or an insurer sees when they look, and for an MSP it's part of the product.
The two datasets agree
The 50-firm benchmark ran the same checks on 9 November. Its results sit close to the extended scan's on most measures:
| Check | Benchmark (of 48) | Extended scan (of 241 or 249) |
|---|---|---|
| HTTPS with a valid certificate | 48 | 241 of 241 |
| DMARC set to quarantine or reject | 30 | 161 of 249 |
| No plugin or library with known issues | 29 | 167 of 241 |
| Strict-Transport-Security (HSTS) | 22 | 109 of 241 |
| CMS version not on show | 22 | 111 of 241 |
| Frame protection | 17 | 75 of 241 |
| Content-Security-Policy | 9 | 68 of 241 |
| security.txt published | 2 | 13 of 241 |
Sources: MSP Website Benchmark (48 websites, 9 November 2026); extended scan (249 MSP websites, 12 to 13 November 2026). The two samples overlap: 43 firms are in both.
How to check your own setup
You can see what a buyer sees in about ten minutes:
- Security headers. Run your homepage through a free security header checker. It lists which of the six you send and grades the result.
- SPF, DKIM and DMARC. Use a free DNS or DMARC lookup tool on your email domain. Check that SPF exists and ends in
-allor~all, that DKIM is published for your email provider, and that DMARC saysp=quarantineorp=reject. - Software versions. View the source of your homepage and search for "generator" and "ver=". If you can see version numbers, so can anyone else.
- security.txt. Visit
yourdomain/.well-known/security.txt. If it doesn't load, you don't have one. - Cookies. Open your site in a private window and, before clicking anything, check your browser's developer tools for cookies and requests to analytics or advertising services.
What to fix first: a checklist for MSPs
In order of risk to your clients and how quickly a buyer would spot it:
- Enforce DMARC. If you're on
p=none, check your DMARC reports to make sure every service that sends email for you (your helpdesk, invoicing, marketing tool) passes SPF or DKIM. Then move top=quarantine, and laterp=reject. Turn on DKIM signing in Microsoft 365 or Google Workspace if you haven't. - Update everything, and remove what you don't use. Update your CMS, plugins and theme, and delete inactive plugins. Out-of-date plugins are one of the most common ways small business websites get hacked.
- Hide version numbers. Remove the CMS generator tag and version strings from scripts and stylesheets. A security plugin or a few lines of configuration will do it.
- Add the six security headers. Start with HSTS, X-Content-Type-Options, Referrer-Policy and frame protection, which rarely break anything. Add Permissions-Policy. Build a Content-Security-Policy last, starting in report-only mode, because a strict one can block scripts your site needs.
- Publish a security.txt file at
/.well-known/security.txt(RFC 9116), with a contact address for anyone who finds a problem. For a security firm, it's a credibility signal. - Add MTA-STS, CAA and DNSSEC if your DNS provider supports them. They're quick wins once the rest is done.
- Fix your cookie banner. Don't load advertising or tracking scripts until the visitor agrees, put "Reject all" next to "Accept all", and if you rely on the new analytics exception, say so and offer an easy way to object.
- Check it the way a buyer would. Run your site and domain through a free header checker and a DMARC lookup, and fix anything that shows red.
What our data can't tell you
- Passive checks only. We looked at what any visitor or public lookup can see. We didn't test for weaknesses, log in or try to get in. A site can pass every check here and still be vulnerable, and a missing header doesn't mean a site has been breached.
- Known versions only. We could only check software whose version a site reveals, so the counts for out-of-date components are lower bounds.
- One point in time. The extended scan ran on 12 to 13 November 2026. Some firms will have changed settings since.
- Some fields are judged by AI. Whether a site shows Cyber Essentials was judged by AI from the page content. Every other check in this piece was measured by a tool.
About the data
About the data. This piece uses two datasets. The MSP Website Benchmark: 50 managed IT firms in 10 UK towns, half visible on Google and half not, checked on 227 data points on 9 November 2026 (website counts are out of 48). An extended scan: 249 MSP websites from the same 10 towns, drawn at random from the 276 firms that passed the benchmark's screening and collected on 12 to 13 November 2026. The extended scan checks what a visitor and a browser see, not Google rankings, reviews or AI answers. 43 firms are in both. Every figure says which dataset it comes from, the two are never added together, and the main report is unchanged.
Questions
Do MSPs secure their own websites?
The basics, yes: every site we could read uses HTTPS. Past that, fewer than you'd expect. 128 of 241 MSP websites send one of the six standard security headers or none, and 74 run at least one component with a published vulnerability.
What should an MSP's own email security look like?
SPF, DKIM and a DMARC policy of quarantine or reject, at a minimum. 148 of 249 MSPs in our study had all three. Add MTA-STS for encrypted delivery once those are in place.
Does a Cyber Essentials badge mean a secure website?
Not on its own. Cyber Essentials covers a firm's own devices, network and accounts, not its public website. In our data, firms showing it were much better on email security but no better on website headers or out-of-date plugins.
Is DMARC mandatory?
Not by UK law for most businesses, but Google, Yahoo and Microsoft's Outlook.com now require a DMARC record from anyone sending large volumes of email to their users. A policy of p=none meets that rule but doesn't stop spoofing. Only quarantine or reject does.
How do I check my SPF, DKIM and DMARC?
Use a free DNS or DMARC lookup tool on your email domain. You want an SPF record, DKIM published for your email provider, and a DMARC policy of quarantine or reject. In our study, 148 of 249 MSPs had all three.
How do I check my website's security headers?
Run your homepage through a free security header checker. It shows which of the six standard headers you send. In our study, 128 of 241 MSP websites sent one or none.
Will security headers improve my Google rankings?
Not directly. HTTPS is the exception (see below). In our study, firms on Google's first page and firms that weren't had the same security results. Fix them because buyers, auditors and insurers check, not for SEO.
Does HTTPS affect Google rankings?
A little. Google confirmed HTTPS as a ranking signal in 2014 and calls it lightweight. Its bigger effect is trust: browsers mark HTTP pages "Not secure". Every MSP site in our study already uses HTTPS.
Is it safe for you to publish this?
We don't name any firm or show anything that would help someone attack a specific site. Every figure is a total across many sites. Where we found something serious, we're telling the firm privately.
Bálint builds the NetNav platform: the agents that check every website, and the rules that turn what they find into a prioritised list of tasks. Every new check is tested on real websites before customers see it, so what NetNav tells you is accurate and its fixes are safe to make. He also writes NetNav’s guides on site speed, security and legal compliance.