by DanDawson 1 (0 reviews)

ProbeGuard 404 Firewall for Cloudflare

Name: ProbeGuard 404 Firewall for Cloudflare
Author: DanDawson

Monitors 404 requests and blocks or challenges abusive IPs at the Cloudflare edge using IP Access Rules.

ProbeGuard 404 Firewall for Cloudflare ranks #56,619 among WordPress.org plugins with 1+ active installations, is #2,394 of 4,566 in the Security category, a 1/5 rating from 0 reviews, and was last updated Sep 15, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v2.0.0 Current Version v2.0.0

Updated 1 week ago Last Update on 15 Sep, 2026

Refreshed 6 hours ago Last Refreshed on

#2,394 of 4,566 in Security Actively maintained

View on WordPress.org

Rank

#56,619

+10653 this week

Active Installs

-2%

KW Avg Position

N/A

— No change

Downloads

112

+6 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 20%

0+ 10+

55,919

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 8 more installs to reach 10+

Rank Changes

Current #56,619

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

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: 2.0.0
Last Updated: Sep 15, 2026
Requires WP: 5.3+
Tested Up To: 7.1
PHP Version: 7.2 or higher
Author: DanDawson

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

404 Brute Force block bots cloudflare firewall

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,758

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

Frequently Asked Questions

Common questions about ProbeGuard 404 Firewall for Cloudflare

No. It uses IP Access Rules, which are available on all plans. Cloudflare enforces an account-level quota on the number of rules.

Each line is matched against the request path, the path plus query string, and both of those prefixed with the requested host. That means an entry can be a path (/tracking/*), a host and path (tracking.example.com/tracking/*), a "contains anywhere" pattern (*tracking.example.com*, which also matches that text in a path or query string) or a pasted URL. Use * for wildcards; a pattern with no wildcard must match exactly. Entries saved by earlier versions gain a trailing * on upgrade so previous prefix behaviour is preserved. My email click-tracking links are logged as 404s They are 404s, so they are logged. Hosts that rewrite links in outgoing mail serve them from a tracking subdomain, so add an entry such as /tracking/* or tracking.example.com/* to the whitelist; matching includes the requested host, so host patterns work too. Nothing host-specific is whitelisted by default.

Blocking falls back to running inline if the scheduled event cannot be created, but expiry, log pruning and diagnostics rely on the scheduled task. Server-level cron and external schedulers work; the plugin warns only when its own maintenance task has not run for two hours, and the warning can be dismissed permanently.

404 records are kept for the configured retention period (1-168 hours, 12 by default). Expired block records are removed a day after expiry. Diagnostic warnings and errors are kept for 7 days and capped at 500 rows. Credentials are redacted from diagnostic output.

Either works. An account token (Manage Account -> Account API Tokens) belongs to the Cloudflare account, so it keeps working when the user who created it loses access, which makes it the better default. A user token (My Profile -> API Tokens) is the only option for a zone reached through an account you are not a member of. One token can serve several sites if its Zone Resources include each zone.

It gets progressively harder to shake off. While an IP is blocked, Cloudflare handles its requests at the edge, so they never reach WordPress to be counted — which is why a returning IP is re-blocked on its first 404 instead of having to earn the full threshold again, and why each successive block within the "Remember offenders" window is twice as long as the last, up to the "Maximum block duration" ceiling. If a 404 does get through while a block is live, the existing block is extended rather than duplicated. Set "Remember offenders" to 0 to treat every block as a first offence.

Deactivating cancels every scheduled task and, unless "Keep Cloudflare blocks when the plugin is deactivated" is enabled in Settings, deletes the Cloudflare access rules the plugin created — nothing would remain to expire them otherwise. Deleting the plugin removes its rules, database tables and options.