Area 08 of 11 · Hardening
The doors attacks use most, closed with one click each.
Closes the doors most attacks use and fixes risky defaults with one click.
A checklist of the basics, each with a "Fix" button.
XML-RPC, file editing, version numbers, user lists.
A full database backup is made before every tool runs.
Security health Free
A checklist of the most important security basics for this site.
This is a screen in the plugin rather than a list of switches: open it from the Keel menu. Free.
Security tools Free
One-click fixes: change user ID 1, the database prefix and the WordPress salts, and check file permissions.
This is a screen in the plugin rather than a list of switches: open it from the Keel menu. Free.
WordPress Free
Turn off WordPress features attackers like to use.
An old remote-control interface that bots use to guess thousands of passwords at once. Leave it on only if you use the Jetpack or WordPress mobile apps.
Stops tricks like ?author=1 and the public users list that reveal login names. Author archive pages redirect to the homepage for visitors.
Removes the theme and plugin file editor, so a stolen admin login cannot be used to insert malicious code.
Removes Appearance > Customize, so the site design and theme settings cannot be changed from wp-admin by mistake or by an intruder. Switch it off for a while when you need to change theme settings there.
Nobody can add or change custom CSS from wp-admin (Customizer and Site Editor). CSS that is already there keeps working.
Removes Appearance > Editor, where block themes edit templates, headers and styles. Only for finished sites: block themes are designed with it.
Bots use the version number to pick which known weaknesses to try.
Application passwords let external apps log in through the API without two-factor. Turn them off unless an app or a headless front end needs them.
SVG logos and icons can be uploaded; files that contain scripts are rejected.
Nobody can install, update or delete plugins and themes (or update WordPress) from wp-admin, and automatic updates stop too. Use it when you deploy updates yourself.
Browser protection Free
Instructions sent with every page that tell browsers to apply extra protections.
Stops other sites from showing yours inside a frame (clickjacking), stops browsers guessing file types, limits what is shared when visitors follow links and blocks camera, microphone and location access.
Browsers will refuse to open the site without HTTPS for a year. Only turn on when the whole site, and every subdomain you use, works over HTTPS.
Server rules Pro
Rules for the web server itself, written to .htaccess on Apache and LiteSpeed. On nginx the lines to add are shown above the settings.
The most common hiding place for a backdoor after a hack. Uploads only contain images and documents, so this never breaks anything.
wp-config.php, readme.html, license.txt, debug.log, error_log and similar files cannot be opened from a browser.
Files starting with a dot (.git, .env, .DS_Store) can leak passwords and source code. .well-known stays open for SSL certificates.
Folders without an index page show "forbidden" instead of a list of every file inside.
Good to know
Changing the salts logs everyone out, on purpose.
File permissions are checked and explained, never changed without asking.
(Pro) Server rules protect folders on Apache and LiteSpeed; nginx gets the rules to copy.
Questions about Hardening
Keel backs up the database, renames tables and rolls back if wp-config.php cannot be written.
Five minutes from now
Give your site a keel.
Steady when traffic spikes, calm when attacks come, found when people search. Start free; go Pro when a site needs more.