Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Plugin how-tos · Guide

Wordfence Settings Explained: What Each Option Does

Short answer

Wordfence settings control the firewall, the malware scanner, login limits, two-factor authentication, blocking, Live Traffic, and email alerts. Set the firewall to Extended Protection with the status Enabled and Protecting, run a Standard Scan daily, lock out an IP after 20 failed logins, and turn on two-factor authentication for everyone who can publish.

Key takeaways

  • Set the Wordfence firewall to Extended Protection with the status Enabled and Protecting for full coverage.
  • Wordfence recommends locking out an IP address after 20 failed logins counted over 5 minutes.
  • Run a Standard Scan daily, and turn on the theme and plugin repository comparison checks.
  • Free sites receive new firewall rules and malware signatures 30 days after Premium sites.
  • Wordfence sends an attack alert when its firewall records at least 100 blocks in 10 minutes.
  • Turn on two-factor authentication for every user who has publishing rights on your site.

What do Wordfence settings control?

Wordfence settings control the firewall, the malware scanner, login limits, two-factor authentication, blocking, Live Traffic, and email alerts.

Wordfence is a WordPress security plugin with an endpoint firewall, a malware scanner, and login security tools, as listed on its WordPress.org plugin page. The settings live on several screens, so this guide walks through each group in turn.

Setting groupMain jobKey choice
FirewallBlocks bad requests before they reach WordPressExtended Protection
ScanFinds malware and changed filesStandard Scan, run daily
Brute force protectionLimits login guesses from one IP addressLock out after 20 failures
Login SecurityAdds 2FA, passkeys, and CAPTCHA2FA for everyone who can publish
Email Alert PreferencesSends mail about attacks and scan resultsAttack alert threshold
Live TrafficShows visits and hack attempts as they happenFilter by Authentication

Wordfence 9.1.1 arrived on November 10, 2026, one day after 9.1.0, and it only updated the bundled certificate list, so no setting changed, according to the Wordfence 9.1.0 release post. Use 9.1.1 as the current version as of November 2026.

Where do you find the Wordfence settings?

You find most Wordfence settings under the Wordfence menu in your WordPress admin, with the full list on the All Options page.

The menu holds Dashboard, Firewall, Scan, Tools, Login Security, and Blocking, and the All Options link sits on the Firewall page and the Dashboard. Open All Options when you want to review every setting in one place.

The All Options page has an EXPAND ALL button that opens every section at once, which helps when you review settings, as Wordfence notes in its basic settings guide.

Work through the settings in this order on a first review:

  1. Open Wordfence → Dashboard and read the status circles.
  2. Open Wordfence → Firewall and check the protection level.
  3. Open Wordfence → Scan and check the scan type and schedule.
  4. Open Wordfence → Login Security and check who has 2FA turned on.
  5. Open Wordfence → All Options and work through each section, saving as you go.

What should the firewall settings be?

Set the firewall to Extended Protection with the status Enabled and Protecting, unless Learning Mode is still needed.

Basic WordPress Protection loads Wordfence as a normal plugin after WordPress loads, while Extended Protection loads the firewall before WordPress or any other PHP file, according to Wordfence's firewall optimization guide. That early load matters because some vulnerable code can run before plugins load.

To switch to Extended Protection, follow these steps:

  1. Go to Wordfence → Firewall and click All Firewall Options.
  2. Click Optimize the Wordfence Firewall in the Protection Level section.
  3. Download the backup copies of .htaccess or .user.ini when prompted.
  4. Click Continue and wait up to 5 minutes for the change to take effect.

Wordfence changes the PHP setting auto_prepend_file so the firewall file wordfence-waf.php loads first, and it prompts you to download backups first in case the change does not work on your host.

Learning Mode does not block with firewall rules yet, so treat it as a short setup phase, not as protection. Brute force login rules still work during Learning Mode, as Wordfence states in its basic settings guide.

If you want the full walkthrough, see our guide to setting up the Wordfence firewall.

What do the brute force protection settings do?

A brute force attack is an automated run of repeated username and password guesses, so the brute force settings limit how many guesses one IP address gets.

Wordfence recommends locking out an IP address after 20 login failures, because real users often need several tries when they forget a password, as its brute force guide explains.

Use these values as your starting point:

  • Lock out after 20 login failures.
  • Count failures over 5 minutes.
  • Lock out for 5 minutes at first, or 60 minutes for a stricter lockout.
  • Lock out after 5 forgot password attempts.

With 20 failures in 5 minutes and a 5 minute lockout, an attacker gets only 20 guesses every 10 minutes, or 2,880 guesses per day. A 60 minute lockout cuts that number far lower, according to the same Wordfence guide.

Turn on “Immediately lock out invalid usernames” only on small sites with 1 or 2 admins, because a real user who mistypes a name gets locked out too. You can unblock a real user from the Firewall → Blocking page.

Add names such as “admin” to the list that blocks an IP at once when it tries to sign in with that name, but never add a real username, since a typo could then block a real user. Usernames on that list are treated as case insensitive.

Wordfence can block logins that use a password found in a data breach. It can also force admins and publishers to use strong passwords of at least 12 characters.

A strong password needs upper and lower case letters, numbers, and symbols. It also needs no character repeated 3 or more times and no numeric run longer than 2 characters, such as 123.

WordPress core does not ship two-factor authentication, so you add it with a plugin, and it also has no built-in login limit, which is why these Wordfence settings matter, as the WordPress brute force guide explains.

How do you set up scan settings?

Set scans to run daily on the Standard Scan type, which Wordfence recommends for most sites.

A Wordfence scan looks for malicious code, backdoors, and shells in your files, and it also checks posts, pages, and comments for bad URLs, as its scan guide explains.

A scan takes from 1 minute to over 10 minutes on a very large site, so run it when traffic is low if your host has limited resources.

Pick the scan type that fits your site:

  • Limited Scan: for hosts with very limited resources, or scans that will not finish.
  • Standard Scan: the recommended choice for most sites.
  • High Sensitivity: for a site you know or strongly suspect is hacked, since it takes longer and uses more resources.
  • Custom Scan: the result when you change individual checks by hand.

Turn on “Scan theme files against repository versions for changes” and “Scan plugin files against repository versions for changes”, because Standard Scan does not include those two checks by default.

Scan results use 4 severity levels: Critical, High, Medium, and Low. Critical issues need a look at once, while Low issues can often wait.

The scanner checks for signatures of over 44,000 known malware variants, and it compares core, theme, and plugin files with the versions in the WordPress.org repository, as the WordPress.org plugin page states.

The vulnerability scan also flags out of date, abandoned, and vulnerable plugins, so use our guide to finding abandoned WordPress plugins when a scan names one.

You can repair a changed core, theme, or plugin file from a clean copy, delete a file that does not belong, or ignore a result you have checked and found safe. Back up first, because a repair can wipe a change you made on purpose.

Back up your site before you delete or repair files from scan results; see how to back up WordPress.

What do the login security settings do?

Login Security adds two-factor authentication, passkeys, and login page CAPTCHA to the password check.

Wordfence recommends that every user with publishing rights sets up two-factor authentication, and the settings live on the Login Security page, as its basic settings guide states.

Two-factor authentication asks for a second proof after the password, usually a code from an authenticator app, so a stolen password alone does not open the site.

Passkeys let users sign in with touch, face recognition, a device password, or a PIN instead of a password, as listed on the WordPress.org plugin page.

Wordfence can disable WordPress application passwords, which arrived in WordPress 5.6, and this option is active by default since Wordfence 7.4.14. Check this setting if a remote app needs an application password to connect.

A CAPTCHA or Turnstile check on the login page slows bots that guess passwords. See our Cloudflare Turnstile guide for WordPress if you use Turnstile.

Use HTTPS on every page so login details stay safe in transit, and check your setup with our Cloudflare SSL settings guide.

How do email alert settings work?

Email alerts tell you about scan results, lockouts, and attack spikes, and you control each alert under Email Alert Preferences.

Wordfence sends the Increased Attack Rate alert when its firewall records at least 100 blocks in 10 minutes, and the mail includes a sample of recent blocks, as its basic settings guide explains.

That alert does not mean an attacker got in. It means a large number of attacks were blocked, so read the sample before you change anything.

Since Wordfence 9.1.0, released November 9, 2026, you can set the “Number of attacks before sending an alert” and the “Attack counting window (minutes)”, so busy sites can raise the threshold and cut the noise, as the release post explains.

You find these fields at Wordfence → Dashboard → Global Options → Email Alert Preferences, under "Alert me when there is a large increase in attacks detected on my site".

Set the alert email address to an inbox you read every day, and add a second address if someone else also needs to act on alerts.

What do Live Traffic and blocking settings do?

Live Traffic shows visits and hack attempts as they happen, with the IP address, the time, and the page each visitor asked for.

You can block an attacker by IP, or build a rule from an IP range, hostname, user agent, or referrer, as the WordPress.org plugin page lists.

Since 9.1.0, Live Traffic also logs failed logins through application passwords and the REST API, two paths that skip wp-login.php. You can find them with the Authentication filter under Show Advanced Filters, as the release post explains.

Click a yellow row in Live Traffic to see who tried to sign in, as which user, and why it failed, and use the buttons there to block the IP or look it up.

Check the IP address Wordfence sees for you under General Wordfence Options, and compare it with the address shown on WhatIsMyIPAddress.com, because a wrong IP breaks rate limits and blocks.

Blocking is a short-term fix. Block the IP, then fix the weak password or old plugin that made the attack worth trying.

What is different in Wordfence Premium settings?

Wordfence Premium changes the timing of updates and adds a few settings, but the free settings above still cover the main protections.

Free sites get new firewall rules and malware signatures 30 days after Premium sites, as the WordPress.org plugin page states, so free sites wait a month for the newest rules.

These settings and features need Premium:

  • Real-time IP Blocklist, which blocks requests from the most malicious IPs.
  • Country blocking.
  • Reputation checks and premium scan signatures.
  • Security Audit Log.
  • More frequent scans and scheduled scan times.

The scan status circles reach 100% only with Premium scan signatures and reputation checks turned on, as the scan guide explains, so a free site shows a lower score by design.

Wordfence Central is free for unlimited sites and lets you manage security for several sites from one place.

How do you check that your settings work?

You check your settings by reading the Dashboard status, running a scan, and watching Live Traffic for a day.

Follow these checks after you change a setting:

  1. Open Wordfence → Dashboard and confirm the firewall shows Extended Protection and Enabled and Protecting.
  2. Open Wordfence → Scan, start a scan, and wait for it to finish.
  3. Read the results by severity and fix Critical items first.
  4. Log out and log back in to confirm 2FA still works for your account.
  5. Check Live Traffic the next day for blocked login attempts.

If a scan will not finish, switch to Limited Scan, which suits hosts with very limited resources, as the scan guide notes.

If the firewall still shows Basic WordPress Protection after you optimize it, wait 5 minutes, then ask your host about the server setup, since some hosts need manual steps.

What mistakes should you avoid?

The most common mistake is leaving the firewall on Basic WordPress Protection and assuming the site is fully covered.

  • Leaving Learning Mode on for weeks, so firewall rules never block.
  • Setting the lockout to 3 or 5 failures, which locks out real users who forget a password.
  • Turning on “Immediately lock out invalid usernames” on a site with many users.
  • Ignoring scan results, or deleting files without a backup.
  • Turning off email alerts, then missing a Critical scan result.
  • Blocking your own IP address and not knowing how to unblock it from the Firewall → Blocking page.

Frequently asked questions

Do I need to change settings after updating Wordfence?

No. In Wordfence 9.1.0, released November 9, 2026, every new feature is on by default. The only optional changes are the Security News Widget layout or visibility and the attack alert threshold, both under Global Options. Update to 9.1.1, which arrived November 10, 2026, and review your settings only if something looks wrong.

What is the difference between Basic and Extended Protection in Wordfence?

Basic WordPress Protection loads Wordfence as a normal plugin after WordPress loads, so some vulnerable code can run first. Extended Protection loads the firewall before WordPress or any other PHP file, using the auto_prepend_file setting. Wordfence recommends Extended Protection for every site that can run it.

How often should Wordfence scan my site?

Wordfence recommends a daily scan set to the Standard Scan type for most sites. A scan takes from 1 minute to over 10 minutes on a very large site. Use Limited Scan only if your host has very limited resources or scans will not finish, and use High Sensitivity only when you know or strongly suspect the site is hacked.

Why does Wordfence lock me out of my own site?

You were locked out because your IP address passed the limit for failed logins, usually 20 failures in 5 minutes, or because you tried an invalid username while that lockout was on. Ask another admin to unblock your IP on the Firewall Blocking page, or unblock it from your host. Then check that Wordfence sees your correct IP address.

Does the free version of Wordfence include two-factor authentication?

Yes. Two-factor authentication, passkeys, and login page CAPTCHA are listed among the login security features of the Wordfence plugin, and Wordfence recommends 2FA for every user with publishing rights. The main things Premium adds are real-time rule and signature updates, the real-time IP blocklist, country blocking, reputation checks, and the audit log.

Can I turn off Wordfence email alerts?

Yes. Go to Wordfence, Dashboard, Global Options, then Email Alert Preferences, and turn off the alerts you do not want, such as the large increase in attacks alert. Keep the scan result and critical issue alerts on, so you hear about a hacked file or a failed scan. Set the alert address to an inbox you read every day.

Sources

  1. Basic Plugin Settings Wordfence
  2. Brute Force Protection Wordfence
  3. Optimizing The Firewall Wordfence
  4. Scan Wordfence
  5. Wordfence Security - Firewall, Malware Scan, and Login Security WordPress.org
  6. Brute Force Attacks Developer.WordPress.org
  7. What's New in Wordfence 9.1.0: Security News, Faster Rules and Smarter Alerts Wordfence

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test