Wordfence or external monitoring? How to catch WordPress vulnerabilities in time
Wordfence is one of the most popular WordPress security plugins, and for good reason: it gives your site a firewall, a malware scanner and login protection. Many site owners assume that once Wordfence is installed, security is taken care of.
The plugin is still just one layer. It runs inside the site, and there are things you simply can't see from inside the site. So the short answer to the question in the title is: both. This article goes through what Wordfence does, what it doesn't do and how external monitoring complements it.
What Wordfence does well
Wordfence protects WordPress from the inside:
- The firewall recognises and blocks known attacks and malicious traffic.
- The malware scanner compares files with the signatures of known malware and with the original files of WordPress, plugins and themes.
- Login protection limits password-guessing attempts and adds two-factor authentication, in the free version too.
- Vulnerability alerts tell you if an installed plugin or theme has a known vulnerability.
The free version is enough for many sites. It's worth knowing, though, that according to Wordfence's own description, the free version receives new firewall rules and malware signatures 30 days after the paid version. When a vulnerability has just been published, updating quickly matters even more for free-version users.
What you can't see from inside the site
Because Wordfence runs inside WordPress, it sees the world from the site's point of view. That's why it can't tell you:
- When the site doesn't respond at all. If the server crashes, a PHP error stops WordPress or the domain stops working, the plugin doesn't run either, and it can't send an alert.
- When an attacker is already in. An intruder may disable the security plugin first thing. External monitoring still notices if the page content changes unexpectedly.
- When something changes outside the site. An expiring SSL certificate, a domain reaching its expiry date and changes to DNS or email records all happen outside WordPress.
- What visitors see. A browser warning page about an expired certificate doesn't show up in the WordPress dashboard, but every visitor sees it.
This isn't Wordfence's fault. A lock on the door can't tell you the house has burned down. For that, you need something on the outside.
What external monitoring does
External monitoring watches your site from the outside, the same way visitors and search engines see it. Digivahti, for example:
- checks that the site is up at regular intervals and confirms an outage from a second location before alerting, so a single network glitch doesn't wake you up for nothing
- tracks the expiry of your SSL certificate and domain, and your email records (MX, SPF, DKIM and DMARC)
- identifies the software and versions running on the site and compares them with known vulnerabilities, also when the site isn't WordPress
- in paid plans, alerts you if the content, DNS records or email records change unexpectedly, if the domain lands on a blocklist or if Google flags the site as dangerous
You can also check your certificate right away without an account with our SSL check (in Finnish).
On WordPress sites, the Digivahti plugin adds detailed update tracking: which core, plugin and theme updates are pending and which of them fix a security hole. It also reads WordPress's security settings from the inside, for example whether the file editor is enabled or whether debug output is visible to visitors. The Digivahti plugin is not a firewall and doesn't replace Wordfence; they do different things.
WordPress vulnerabilities: where do they come from?
Most known WordPress vulnerabilities are found in plugins and themes, not in WordPress core. A vulnerability usually isn't dangerous at the moment it's discovered. The danger starts when it's published and a fixing update is available, but the site isn't updated. That's when attackers know exactly what to look for.
So the most important question isn't whether your site has vulnerabilities, but how quickly you notice them and update. In practice:
- Keep updates current, especially those that fix a security hole.
- Remove plugins you don't use. Even a deactivated plugin can be vulnerable if its files are on the server.
- Follow vulnerability information with Wordfence, Digivahti or both, and make sure the alerts go to someone who reads them.
- Back up and test that restoring works.
- Monitor from the outside, so that you also notice what you can't see from inside the site.
Which one should you choose?
Both, because they don't compete with each other:
| Feature | Wordfence (plugin) | Digivahti (external monitoring) |
|---|---|---|
| Where it runs | Inside the site | Outside the site |
| Blocks attacks | Yes (firewall) | No |
| Notices an outage | No | Yes |
| SSL and domain | No | Yes |
| Vulnerabilities | WordPress, plugins and themes | All detected software, WordPress in more detail with the plugin |
| Blocklists | In the paid version | In paid plans |
| Works if the site is hacked and the plugin removed | No | Yes |
If your site runs on WordPress and you already have Wordfence, add external monitoring alongside it. If you have neither, start with updates and external monitoring. They tell you where you stand. For a quick overview, the free SEO audit (in Finnish) scores your site across 12 areas, one of which is security.
Frequently asked questions
Is the free version of Wordfence enough? For many small sites, yes, as long as updates are handled quickly. The free version receives new firewall rules and malware signatures 30 days after the paid one, so it doesn't replace updating.
Does Wordfence notice if my site goes down? No. Wordfence runs inside WordPress, so when WordPress doesn't start, neither does the plugin. Only external monitoring notices the outage.
Does Digivahti need a WordPress plugin? No. Uptime, the certificate, the domain and software vulnerabilities are monitored from the outside without installing anything. The plugin adds more detailed update tracking and a security settings check for WordPress sites.
Start using Digivahti for free → The free plan monitors one site, and new accounts get all of Digivahti Perus free for 28 days. After the trial, the account continues on the free plan unless you choose a paid plan yourself.