Description
Bollwerk helps keep your WordPress site safe from the moment you activate it. There’s nothing to set up. Every protection is already on with safe, recommended settings. You can review or change anything on the Settings → Bollwerk screen.
We protect your site in three simple ways: Closing Security Loopholes, Stopping Password Guessers, and Filtering Bad Traffic.
1. Closing Security Loopholes
- Hides your WordPress version: Attackers scan for specific WordPress versions with known bugs. We hide yours so you’re not an easy target.
- Locks down the file editor: Intruders often use the built-in editor to plant malicious code. We turn it off so a compromised account can’t ruin your site.
- Doesn’t reveal usernames: Shows the same generic error whether the username or the password is wrong, so attackers can’t tell which accounts are real.
- Turns off risky features: We switch off little-used features that attackers often abuse to get in, like XML-RPC and application passwords.
- Blocks AI requests: Turns off WordPress’s AI client so plugins and core can’t send prompts out from your site.
- Adds browser protection: Tells visitors’ browsers to be stricter with your pages, which blocks a few common disguise tricks and stops other sites from pretending to be you.
- Optional spam protection: Turn off comments entirely to stop comment spam bots (off by default).
2. Stopping Password Guessers
- Blocks “Brute Force” attacks: Attackers use automated bots to guess thousands of passwords a second. Bollwerk watches your login form and instantly locks out anyone who guesses wrong too many times (default: 5 failed attempts locks them out for 15 minutes).
3. Filtering Bad Traffic (Firewall)
Think of this as a bouncer at the door of your website. It checks every visitor before your site even loads and kicks out the troublemakers.
* Blocks malicious visitors: Recognizes known attack patterns and blocks them immediately.
* Protects your private files: Ensures sensitive files (like your site’s database settings, backups, log files, and files that reveal your software versions) can’t be downloaded by strangers.
* Stops malicious uploads: If an attacker manages to upload a file, this prevents the file from actually running any harmful code on your server.
Privacy
Bollwerk makes no external requests and collects zero user data. It runs entirely on your server. The only files it writes are its own local settings and the firewall rules it manages (with an automatic backup of your original file kept in the uploads folder).
Credits
The built-in firewall ruleset is a modified version of the excellent 8G Firewall by Perishable Press.
Installation
- Install and activate Bollwerk from your site’s Plugins screen.
- Done! Your site is instantly protected.
- (Optional) If you ever need to change a setting, you can review them on the Settings → Bollwerk screen.
FAQ
Do I need to configure anything?
No. Every protection is already turned on with safe, recommended settings. You can review or adjust them at any time under Settings → Bollwerk.
Does Bollwerk work on any hosting?
Yes! The core protections (closing loopholes and stopping password guessers) work on every hosting setup. The firewall feature requires an Apache or LiteSpeed server (which most shared hosting uses). If your site runs on nginx or IIS, the plugin detects that and skips the firewall, with a notice explaining why.
Does Bollwerk speed up my site?
It is not a caching or optimization plugin, but it does trim a little: emojis and self-pinging add background code to every page, and we remove it. The effect is modest; the main benefit is security.
Does Bollwerk send my data anywhere?
Never. The plugin runs 100% on your server, makes no external calls, and collects zero data. Your privacy is fully protected.
What happens to my site when I deactivate the plugin?
Everything goes right back to normal. The firewall’s rules are safely removed from your .htaccess file, and a backup of your original file is kept in your uploads folder just in case.
I am a developer. What exactly does it do technically?
- Disables XML-RPC, theme and plugin file editors, application passwords, AI prompts, emojis, and self-pingbacks.
- Hides the WordPress core and asset version strings, and returns generic login error messages.
- Sends conservative response headers on the front end:
X-Content-Type-Options: nosniff,Referrer-Policy: strict-origin-when-cross-origin, andX-Frame-Options: SAMEORIGIN. Each is only sent when nothing else has already set it. - Login protection throttles an IP address after too many failed attempts.
- The firewall uses the 8G ruleset by Perishable Press, written to
.htaccessand the uploads folder, to block malicious query strings, request URIs, user agents, and referrers. It also protectswp-config.php, denies public access to backup, dump, and log files (.bak,.old,.orig,.rej,.tmp,.swp,.swo,.save,.backup,.ini,.sql,.log) as well asreadme.htmlandlicense.txt, and blocks direct access to readme and changelog files, Markdown files (.md), translation catalogs (.po,.pot,.mo), and developer metadata (composer.json,package.json, lock files) inside plugin and theme folders, and PHP execution in/uploads.
Screenshots
Changelog
1.1.1
- Fixed the 8G ruleset blocking paths such as /wp-content/plugins/error-log-monitor/.
1.1.0
- Renamed the plugin internals, settings, hooks, and firewall markers to Bollwerk.
1.0.10
- Link the plugin homepage and author to the new store.
1.0.9
- Renamed the plugin to Bollwerk.
- New Bollwerk icon, banner, and screenshots.
- Updated the readme and admin branding.
- Existing settings and firewall blocks are preserved.
1.0.8
- Fix: Sites using a block theme no longer get a blank front page. The template guard now accepts WordPress’s block template canvas, and falls back to it when the active theme has no index.php.
- Fix: The template guard now rejects phar://, data: and php:// stream wrapper paths, and no longer rejects normal Windows drive paths.
- Improved: The firewall now hides plugin and theme metadata from direct downloads. readme.txt, changelog.txt and their common variants, Markdown files, .po/.pot/.mo translation catalogs, and developer files such as composer.json, package.json and lock files are denied inside plugin, must-use plugin and theme folders. Site-root readme files and files in uploads stay reachable.
- Improved: Copies of wp-config.php with a suffix (.bak, .txt, .orig, ~), and patch or editor leftovers (.orig, .rej, .swo, files ending in ~) are now blocked.
- Improved: The uploads guard also covers .pht, .phtm, .phps and multi-digit PHP extensions.
- Improved: .htaccess writes are read back and restored to the previous content when a write fails. An unreadable file or a broken firewall block marker is left untouched instead of being rewritten, and writing the same block twice no longer duplicates it.
1.0.7
- Hidden files and folders such as .git, .env and .svn are no longer reachable.
- Rotated logs such as debug.log.1 are blocked too.
- An optional setting blocks backup archives outside the uploads folder.
- Malformed Chrome and Googlebot user agents and injection probes are blocked.
- An optional setting blocks command-line download tools.
- Fixed the firewall rewrite base on subdirectory installs.
1.0.6
- Multisite networks: the main site now drives the shared firewall, and direct access to readme.html, license.txt and licencia.txt is blocked.
1.0.5
- Improved the settings screen: dependent options grey out with their switch, saving keeps the current tab, and a warning appears when the WordPress permalink rules are missing.
1.0.4
- New: Validates template paths so a page cannot load a template from outside your theme.
- New: Restricts the REST batch API to users who can edit content.
- New: Adds an option to keep every plugin and theme on its latest version automatically.
1.0.3
- New: A dismissible prompt on the settings screen to enable automatic plugin updates.
1.0.2
- New: Sends safer browser response headers (file-type sniffing, referrer, and clickjacking protection).
- Fixed: The firewall’s local-development detection now also works when the rules are generated from the command line or a scheduled task, so it no longer blocks the login page on a localhost site.
1.0.1
- New: Turn off the built-in theme and plugin file editor.
- Fixed: the firewall no longer gets in the way on local development sites (localhost/loopback).
1.0.0
- Initial release.



