PluginScout

HTTP/1.1 403 Forbidden header on a failed login — WordPress Anti-Spam Plugin

by atmosphear · WordPress.org page · Website

v1.0 Tested up to WP 4.4.34

HTTP/1.1 403 Forbidden header on a failed login has 200+ active installs on WordPress.org and 2,622 downloads all time. We have tracked it since September 4, 2026; download trends appear after 30 days of data. The last update was on March 23, 2016, tested up to WordPress 4.4.34.

HTTP/1.1 403 Forbidden header on a failed login at a glance

Active installs
200+
Total downloads
2,622
Downloads, last 30 days
–
available after 30 days of tracking
30-day growth
–
tracking since September 4, 2026

Is HTTP/1.1 403 Forbidden header on a failed login well maintained?

Support threads resolved
No open threads
nothing waiting on the WordPress.org forum
WordPress compatibility
Behind
tested up to WordPress 4.4.34, not yet with the current 7.1

HTTP/1.1 403 Forbidden header on a failed login reviews and ratings

2 reviews on WordPress.org, with the most recent ones as their authors posted them.

All reviews
5.0 out of 5

2 reviews

5★
2
4★
0
3★
0
2★
0
1★
0

  • Very useful plugin

    This functionality should be default behavior, implemented in the core of WP. Integration with Fail2Ban significantly increase security and performance of WP. Must have plugin

    sojic

  • Отлично

    Работает как заявлено, всё отлично.

    Ramzzes

Details

Send an "HTTP/1.1 403 Forbidden" header on a failed login instead of the default "HTTP/1.1 200 OK"

The full description, screenshots and every review live on the WordPress.org page.

Rankings HTTP/1.1 403 Forbidden header on a failed login competes in

Tags

  • fail2ban
  • headers
  • spam
Version
1.0
Last updated
Mar 23, 2016
First published
Mar 23, 2016
Requires WordPress
4.0.0
Tested up to
4.4.34
Requires PHP
–
Pricing
Free on WordPress.org

HTTP/1.1 403 Forbidden header on a failed login FAQ

How many active installs does HTTP/1.1 403 Forbidden header on a failed login have?

WordPress.org reports 200+ active installs for HTTP/1.1 403 Forbidden header on a failed login as of September 7, 2026.

Is HTTP/1.1 403 Forbidden header on a failed login still maintained?

The last release was on March 23, 2016, more than a year ago. WordPress.org shows a warning on plugins that go this long without an update.

Is HTTP/1.1 403 Forbidden header on a failed login free?

HTTP/1.1 403 Forbidden header on a failed login is free to install from WordPress.org. Many plugins also sell a paid version or add-ons.