Census › Plugin profiles › Limit Login Attempts Security
Limit Login Attempts Security – Login Security, 2FA, Firewall, Brute Force Prevention
Figures from the Plugin Directory Census · as of 28 Aug 2026
1M
Active installs, lower bound
Group: 1,000,000+ installs
16
Days since the last release
Group median: 8
4.8
out of 5, from 1,477 ratings
Group median: 4.7 (10+ ratings)
42.1%
Support threads marked resolved, two months
Group: 71.9%
Full profile on wordpress.orgShow on the mapCompare with your own plugins
What is Limit Login Attempts Security and who is behind it?
Limit Login Attempts Security is a WordPress plugin in the “Security” field, made by WPChef. It has been listed in the directory since 3 Aug 2016, so for 10 years. It is the only plugin by WPChef with at least 10,000 installs. With 1,000,000 to 1,999,999 active installs it belongs to the 1,000,000+ installs group; its last release came 16 days before the reference date, and it is tested up to WordPress 7.0.
This is how the author describes the plugin on wordpress.org:
“WordPress login security with brute force protection, Two-factor authentication (2FA/MFA), firewall, IP/country blocking, and login monitoring”
Self-description on wordpress.org, retrieved on 10 Sept 2026
When was Limit Login Attempts Security last released?
The last release of Limit Login Attempts Security came 16 days before the reference date; the group median is 8 days.
How many installs does Limit Login Attempts Security have?
Limit Login Attempts Security had 1,000,000 to 1,999,999 active installs on the reference date. Within its group, 28 plugins had a higher band and 38 plugins the same band.
The API reports installs only as a lower bound with one significant figure: 1,000,000 means at least 1,000,000 and at most 1,999,999.
Which WordPress version is Limit Login Attempts Security tested with?
No directory notice: tested up to WordPress 7.0, while core stood at 7.1 on the reference date. The notice appears once the field falls below 6.9; that applied to 3.0% of the group.
How does Limit Login Attempts Security compare with its group?
The group holds 67 listed plugins. 73.1% of them had a more recent last release than Limit Login Attempts Security; 1.5% had no release for more than 365 days.
| Figure | Limit Login Attempts Security | Group, 67 plugins |
|---|---|---|
| Days since the last release | 16 | median 8 |
| Rating | 4.8 (1,477) | median 4.7 (10+ ratings) |
| Support threads marked resolved | 42.1% | 71.9% |
| Tested up to | 7.0 | 65.7% on 7.1 |
| Requires PHP | not stated | most often 7.4 (49.3%) |
All values on the reference date
| Slug | limit-login-attempts-reloaded |
|---|---|
| Author | WPChef |
| Active installs | 1,000,000 to 1,999,999 |
| Last release | 16 days before the reference date |
| Tested up to | WordPress 7.0 · core on the reference date: 7.1 |
| Requires WordPress | 5.0 |
| Requires PHP | not stated |
| Rating | 4.8 out of 5 from 1,477 ratings |
| Support threads, two months | 8 of 19 marked resolved |
| Listed since | 3 Aug 2016 |
| Total downloads | 93,171,834, updates included |
| Tags | 2fa, brute-force, firewall, login-security, security |
Tags
| Tag | Plugins with 10,000+ installs and this tag | Rank by installs | Median days since release |
|---|---|---|---|
| 2fa | 12 | 3 | 16 |
| brute-force | 7 | 1 | 40 |
| firewall | 17 | 2 | 12 |
| login-security | 4 | 1 | 12 |
| security | 79 | 5 | 16 |
Rank 1 has the highest installation band among plugins with 10,000+ installs and this tag; equal bands share a rank.
Class of 2016
Limit Login Attempts Security has been listed since 3 Aug 2016. Of the 200 plugins with 10,000+ installs added in 2016, 87.0% released within the 365 days before the reference date.
Same group, shared tags
Not a recommendation; the same figures for comparison. Alphabetical.
| Plugin | Active installs | Last release | Rating |
|---|---|---|---|
| All-In-One Security | 1,000,000 to 1,999,999 | 15 days before the reference date | 4.7 (1,715) |
| Hostinger Tools | 3,000,000 to 3,999,999 | 3 days before the reference date | 3.5 (40) |
| Jetpack | 3,000,000 to 3,999,999 | 8 days before the reference date | 3.7 (2,406) |
| Loginizer | 1,000,000 to 1,999,999 | 9 days before the reference date | 4.8 (1,030) |
| ManageWP Worker | 1,000,000 to 1,999,999 | 7 days before the reference date | 4.6 (678) |
| Really Simple Security | 3,000,000 to 3,999,999 | 4 days before the reference date | 4.9 (8,862) |
| Safe SVG | 1,000,000 to 1,999,999 | 8 days before the reference date | 4.9 (79) |
| Security Optimizer | 1,000,000 to 1,999,999 | 0 days before the reference date | 4.5 (157) |
Do you maintain Limit Login Attempts Security?
If you maintain Limit Login Attempts Security, you can link to this profile, for example from your readme or your website. Both snippets show this badge:
HTML
<a href="https://hafenstudios.com/en/census/plugins/limit-login-attempts-reloaded/"><img src="https://hafenstudios.com/census/plugins/badge-en.svg" alt="Limit Login Attempts Security in the Plugin Directory Census 01/2026" width="220" height="40"></a>
Markdown
[](https://hafenstudios.com/en/census/plugins/limit-login-attempts-reloaded/)
The image is loaded from hafenstudios.com; as with every request, our server records the usual access data, which is deleted after 14 days. If you prefer not to, use a plain text link.
A value is wrong? Write to moin@hafenstudios.com; a documented correction leads to a new version.
How to cite
hafenstudios (2026): Limit Login Attempts Security – Login Security, 2FA, Firewall, Brute Force Prevention, profile in the Plugin Directory Census 01/2026, reference date 28 Aug 2026. https://hafenstudios.com/en/census/plugins/limit-login-attempts-reloaded/
Source and status
All values come from the full pull of the public wordpress.org API on 28 Aug 2026 (reference time 21:56:30 UTC). The analysis and text on this page are available under CC BY 4.0; the raw values come from the public wordpress.org API and are in the raw data. How the count was made is set out in the method, what the fields do not say under limits. hafenstudios builds WordPress plugins itself, see the conflict of interest. Corrections to moin@hafenstudios.com; a documented correction leads to a new version. From issue 02 this page will also show the change since the previous reference date. Collected and prepared by Horst Wenzel.
Plugin names and trademarks belong to their owners. hafenstudios is not affiliated with the authors named here.
