HTTP/1.1 403 Forbidden header on a failed login vs ReportAttacks — Brute Force & Login Protection
Compare reviews, downloads, installs, update activity, support responsiveness, maintenance score, and WP/PHP compatibility.
Metric
HTTP/1.1 403 Forbidden header on a failed login
ReportAttacks — Brute Force & Login Protection
Rating
HTTP/1.1 403 Forbidden header on a failed login
ReportAttacks — Brute Force & Login Protection
Active installs
HTTP/1.1 403 Forbidden header on a failed login
200
ReportAttacks — Brute Force & Login Protection
30
Downloads
HTTP/1.1 403 Forbidden header on a failed login
1,934
ReportAttacks — Brute Force & Login Protection
7,863
Last updated
HTTP/1.1 403 Forbidden header on a failed login
3618 days ago
ReportAttacks — Brute Force & Login Protection
132 days ago
Maintenance score
HTTP/1.1 403 Forbidden header on a failed login
22/100
ReportAttacks — Brute Force & Login Protection
52/100
Support resolved
HTTP/1.1 403 Forbidden header on a failed login
—
ReportAttacks — Brute Force & Login Protection
—
Languages
HTTP/1.1 403 Forbidden header on a failed login
1
ReportAttacks — Brute Force & Login Protection
1
Requires WordPress
HTTP/1.1 403 Forbidden header on a failed login
4.0.0
ReportAttacks — Brute Force & Login Protection
4.0
Tested up to
HTTP/1.1 403 Forbidden header on a failed login
4.4.34
ReportAttacks — Brute Force & Login Protection
6.8.3
Requires PHP
HTTP/1.1 403 Forbidden header on a failed login
f
ReportAttacks — Brute Force & Login Protection
f