by Arttu Manninen 5 (2 reviews)

HTTP/1.1 403 Forbidden header on a failed login

Name: HTTP/1.1 403 Forbidden header on a failed login
Rating: 5.0 (2 reviews)
Author: Arttu Manninen

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

HTTP/1.1 403 Forbidden header on a failed login ranks #11,392 among WordPress.org plugins with 200+ active installations, is #704 of 5,058 in the Security category, a 5/5 rating from 2 reviews, and was last updated Mar 23, 2016. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 4.4 (Current: 7.1.4)

vtrunk Current Version vtrunk

Updated 10 years ago Last Update on 23 Mar, 2016

Refreshed 1 week ago Last Refreshed on

#704 of 5,058 in Security Top 25% by installs No update in over a year

View on WordPress.org

Rank

#11,392

— No change

Active Installs

200+

-30.1%

KW Avg Position

— No change

Downloads

2.1K

+2 today

Support Resolved

— No change

Rating

100%

Review 5 out of 5

5 (2 reviews)

Next Milestone 300

Total Progress 81%

200+ 300+

406

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 19 more installs to reach 300+

Rank Changes

Current #11,392

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

2 reviews

Overall 100%

2 (100%)

0 (0%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for HTTP/1.1 403 Forbidden header on a failed login. Checked 3 months ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: trunk
Last Updated: Mar 23, 2016
Requires WP: 4.0.0+
Tested Up To: 4.4
PHP Version: N/A
Author: Arttu Manninen

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 2
Support Threads: 0
Resolved: 0%

Keywords

fail2ban headers spam

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Akismet Anti-spam: Spam Protection

5M+ installs

Wordfence Security – Firewall, Malware Scan, and Login Security

5M+ installs

#11

Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention

View all Security-and-spam-protection plugins

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress site administrators who use external security tools to monitor login attempts. It makes failed logins return an HTTP 403 Forbidden header instead of WordPress's default 200 OK, so tools like fail2ban can detect and block brute-force attacks at the firewall level.

Sends 403 header on failed login
Replaces default 200 OK response
fail2ban compatibility
Firewall-level brute-force prevention
Requires PHP 5.3+

Frequently Asked Questions

Common questions about HTTP/1.1 403 Forbidden header on a failed login

HTTP/1.1 403 Forbidden header on a failed login has 200+ active installations on the WordPress.org plugin directory.

HTTP/1.1 403 Forbidden header on a failed login holds a 5 out of 5 star rating based on 2 user reviews on WordPress.org.

HTTP/1.1 403 Forbidden header on a failed login is developed by Arttu Manninen and published on the official WordPress.org plugin repository.

HTTP/1.1 403 Forbidden header on a failed login requires WordPress 4.0.0 or higher and is tested up to WordPress 4.4.

HTTP/1.1 403 Forbidden header on a failed login has been downloaded 2,121+ times from WordPress.org.

The latest version of HTTP/1.1 403 Forbidden header on a failed login is trunk. It was last updated on March 23, 2016.

Yes. HTTP/1.1 403 Forbidden header on a failed login is a free WordPress plugin available to download and install from the WordPress.org plugin directory.