Skip to content
Launch offer 50% off your first year of Keel Pro. See prices →

Area 07 of 11 · Firewall

Attackers are turned away before WordPress even loads.

Stops password guessing, file probing and attack code before WordPress loads.

9 sections40 free15 Pro
In plain words Every site is attacked every day by automated tools: they guess passwords, look for forgotten backup files and send attack code in search boxes. Keel counts every attempt per address. A few failures earn a short block; an address that keeps coming back is banned for good. Known attack patterns are logged, and with Pro they are blocked outright, along with countries you choose and public lists of known attackers.
01 Every attempt is counted

Failed logins, fake usernames and probes for files like .env.

02 Blocks grow

Short block first, longer after, a permanent ban for repeat offenders.

03 Shared with your sites

An address banned on one site can be banned on all your connected sites.

Blocked IPs Free+ Pro extras

Who is blocked for now, who is banned for good, who is always allowed, and the banned list shared by all your sites.

Share permanent bans with all my sites
Recommended Free

Addresses banned for good here are sent to the Keel Hub, and addresses banned on your other sites are banned here too (checked every hour). Needs the site to have joined the Hub. Remove an address for every site in the Hub > Banned IPs.

Stop banned addresses in .htaccess
Recommended Pro

Permanent bans are also written to .htaccess, so the web server refuses them before WordPress even starts, and cached pages are protected too. Only on Apache / LiteSpeed when the visitor IP is read from the direct connection.

The settings marked Pro switch on with any paid plan; the rest is free. See plans

Visitor IP Free

Every block depends on knowing the visitor's real IP address.

Read the visitor IP from
Free

Behind Cloudflare or a load balancer the server only sees the proxy's address, so one block would block everyone. Only pick a proxy option if the site really uses one, otherwise attackers could fake their IP.

Failed logins & bans Free

Too many failed logins block an address for a while; an address that keeps getting blocked is banned for good.

Block addresses after failed logins
Recommended Free

Wrong passwords, wrong two-factor codes and visits to wp-login.php or /wp-admin while the login page is hidden all count.

Failed logins allowed
Free

From one address. A successful login from it starts the count again.

Counted within
Free

Failed logins older than this no longer count.

Then block the address for
Free

A first block is temporary, so a person who mistyped can try again later.

Ban for good anyone who tries to log in on wp-login.php
Free

Only when the login address is hidden (Login & accounts > Login page). Your real users log in on the new address, so anyone sending a username and password to the old one is a bot or an attacker, and is banned on the first try. Just opening the old address still counts as a failed login. Whitelisted addresses are never banned.

Block it from the whole website
Free

On: the address sees "Access denied" on every page until the block ends. Off: it can still browse the site, just not log in.

Ban repeat offenders for good
Recommended Free

Every block counts: failed logins, fake usernames and file scanning. A banned address can never reach the site again; lift it in Firewall > Blocked IPs.

Ban for good after
Free

With 3, an address blocked 3 times is banned for good the next time it misbehaves.

Blocks counted within
Free

Older blocks are forgotten.

Block anyone trying fake usernames
Recommended Free

Only bots try "admin" on a site that has no user called admin. Their address is blocked on the first try, for the time set under File scanning.

Fake usernames
Free

Separated by spaces. Names that really exist on this site are never treated as fake.

Pause an account after
Free

Counted per account from any address, within the days above. Stops attacks spread over thousands of addresses. Password logins pause for the block length; the owner can still log in with a login link (Keel Pro). 0 = off.

Block anyone who tries a username that does not exist
Free

Bots guess names like "admin" or "test". Strong, but a person who mistypes their username is blocked too (they can be unblocked in Blocked IPs).

Email me about each block
Free

One email per address or account per hour, to the reports address. The weekly email sums them up anyway.

File scanning Free

Bots look for leftover files such as backups, .env or phpMyAdmin. Asking for several of them is a clear sign of an attack.

Block addresses that scan for files
Recommended Free

Requests for missing suspicious files are counted per address. Files that really exist are served directly by the server and are not counted. Every request is listed in the security log under "File probes".

Suspicious requests allowed
Free

Real visitors never ask for these files.

Counted within
Free
Then
Free

A permanent ban can be lifted in Firewall > Blocked IPs.

Block length
Free

Used when the choice above is "Block", and for fake-username blocks.

Count every "page not found"
Free

Stricter: any missing page counts, not only suspicious files. A visitor clicking a few broken links could be blocked, so raise the limit if you turn this on.

Bots & attacks Free+ Pro extras

Check each request for hacking tools and attack code. Logged-in administrators and whitelisted IPs are never filtered.

Block hacking tools
Recommended Free

Turns away about 30 known vulnerability scanners (sqlmap, nikto, wpscan, nuclei...) that announce themselves in their browser name.

Block requests without a browser name
Free

Every real browser identifies itself; crude scripts often do not. Whitelist your uptime monitor if it is blocked.

Also block browser names containing
Free

Extra words separated by spaces, for example aggressive crawlers like "semrush ahrefs".

Attack code in web addresses
Pro

Spots SQL injection, script injection and "../" tricks in addresses. Start with "only log" for a week; if the log shows no real visitors, switch to "Block".

Block addresses that send too many requests
Recommended Pro

Stops scrapers and floods. Only pages built by WordPress count (not cached pages or images); logged-in users and real Google, Bing and Apple crawlers are never limited.

Requests allowed
Free

From one address. A person clicking around fast makes 10 to 20.

Then block it for
Free

Counts as a block towards a permanent ban (Failed logins & bans).

Count password guessing through XML-RPC and the REST API
Recommended Pro

Wrong application passwords, and login calls sent to xmlrpc.php while XML-RPC is off, count as failed logins, so those bots get blocked too.

The settings marked Pro switch on with any paid plan; the rest is free. See plans

Form protection Free+ Pro extras

Stops bots and spam on every form of the site: comments, WooCommerce, Contact Form 7, WPForms, Gravity, Elementor, Fluent, Formidable and any other form.

Protect forms
Recommended Free

Invisible checks on every protected form. Real visitors notice nothing; logged-in editors are never checked.

Which forms
Pro

"Any other form" means every form with a message, email or password field that is sent with POST. Search boxes and cart buttons are never touched.

Refuse forms sent faster than
Free

Counted from when the page opened. People need a few seconds to fill in a form; bots send it at once.

Require a real visit
Free

The form must come from the page itself, with at least one tap, click or key press. Bots that post straight to the site are refused.

Captcha
Pro

The invisible checks stop most bots. Add a captcha if spam still gets through. Turnstile uses the keys from Login > Bot check. reCAPTCHA sends visitor data to Google: mention it in your privacy policy (EU).

reCAPTCHA site key
Free

From google.com/recaptcha/admin. Pick the same version (v2 checkbox or v3) as above.

reCAPTCHA secret key
Free
reCAPTCHA v3: lowest human score
Free

v3 rates each visitor from 0 (bot) to 10 (human). 5 suits most sites; lower it if real messages are refused.

hCaptcha site key
Free

From dashboard.hcaptcha.com.

hCaptcha secret key
Free
Refuse messages with more than
Pro

Spam is full of links; real messages rarely have more than one or two. 0 = no limit.

Refuse messages containing
Pro

One word or phrase per line, for example "casino", "SEO services", "crypto".

Refuse messages written in
Pro

Only if none of your customers write in these alphabets.

Refuse the same message sent 3 times in a day
Pro

Spam robots send the same text again and again.

Refuse fake email addresses
Pro

Throwaway addresses (mailinator, 10minutemail...) and domains that cannot receive email.

Block the sender after
Free

Refused messages are in the security log under "Form spam" and count towards a block, then a permanent ban like failed logins. 0 = never block.

Block length
Free
Share spam with your other sites (Hub)
Free

A message refused here is refused on your other sites too. Only a fingerprint of the text is shared, never the text, names or emails. Needs the site to have joined the Hub.

The settings marked Pro switch on with any paid plan; the rest is free. See plans

Countries Pro

Block countries you never get real visitors from, or allow only your own.

Country rule
Pro

The country comes from Cloudflare when the site uses it, otherwise from the free DB-IP database (downloaded monthly, about 3.6 MB).

Countries
Pro

Search, tick single countries, or tick a region to select all of it. Visitors whose country cannot be found are always allowed.

Where it applies
Pro

"Only login" keeps the site open to everyone and still stops logins from those countries.

This whole section is part of Keel Pro, on every paid plan. See plans

Allow & block lists Free

Addresses that are always trusted or always blocked. One per line, single IPs or ranges like 198.51.100.0/24; IPv6 works too. Text after # is a note.

Always allow
Recommended Free

Your office, your home, your uptime monitor. These addresses skip every lockout, filter and block list.

Always block
Free

These addresses see "Access denied" on every page.

Public blocklists Pro

Lists of known attacker addresses maintained by security organisations. They download once a day in the background and checking a visitor takes a fraction of a millisecond.

Block visitors listed on
Pro

Spamhaus DROP and FireHOL Level 1 are safe for every site. blocklist.de and CINS catch more bots, with a small chance of blocking a real visitor on a shared connection. Pages served from a page cache or CDN skip this check.

This whole section is part of Keel Pro, on every paid plan. See plans

Good to know

Your own address can be always allowed, so you never lock yourself out.

Behind Cloudflare, the real visitor address is used, and only from Cloudflare's own ranges.

(Pro) Bans can be written to .htaccess so banned addresses never reach PHP.

Questions about Firewall

Only after repeated failures. Every block is listed with the reason, and Unblock is one click.

No, it works well behind it. Cloudflare filters the network; Keel knows WordPress logins and files.

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.