A firewall that sees it first
ModSecurity sits in front of WordPress and filters the common attacks before your site is asked to deal with them. On by default, set per domain, and yours to switch off if a rule ever fights your site.
Feature
A firewall in front, and no invented numbers
ModSecurity filters common attacks before the request reaches WordPress, cpGuard watches for the files that should not be there, and your site runs in a container of its own.
At a glance
- Free HTTPS on every address
- IP allow and block rules
- Two-factor, and a second ask
- No security score, no attack counter
Malware watched behind it
cpGuard scans for the files that have no business being on your site. A firewall is about the request and a scanner is about what got through, and a serious answer needs both of them.
Your neighbours can't reach you
One WordPress site per container, with its own files, memory, CPU and database. On shared hosting a compromised site next door shares your account. Here it does not share your container.
The specifics
- Free HTTPS on every address
- Let's Encrypt on your Pressy address and on every custom domain, issued and renewed with nothing for you to click.
- IP allow and block rules
- Keep specific addresses out, or let only specific ones in. The allow-list can lock you out of your own site, so it asks you to type your domain and offers to add the address you are on first.
- Two-factor, and a second ask
- TOTP with recovery codes on your account, and sensitive actions asking for it again even while you are signed in.
- No security score, no attack counter
- Our panel reports neither, so we show neither. A number we made up would be the least trustworthy thing on a screen whose whole job is trust.
The questions people ask
What does the firewall actually do?
ModSecurity inspects requests before they reach WordPress and drops the ones matching known attack patterns, which is most of the automated traffic any WordPress site gets. It runs on the server in front of your site rather than inside it as a plugin.
Do I still need a security plugin?
That is your call, and plenty of people run one as well. The firewall is doing a different job from a plugin: it sees the request before WordPress is loaded, and a plugin sees it afterwards. Neither replaces the other.
Can you show me how many attacks were blocked on my Pressy?
Not yet. The firewall and the scanner run on the server and give us no per-site count we could show you honestly, so we show nothing rather than a made-up number.
The other five
The rest of what people switch for. The whole list is on the features page.
Protection you can name, not a badge
Firewall, isolation, HTTPS and backups on every Pressy.