WordPress plugin intelligence profile

Wonderful Repeated Hit Blocker for Wordfence

Blocks IP addresses that Wordfence has logged as attacking your site repeatedly within a short time window.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.1
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.2 · PHP 7.4
Directory statusactive
Last directory update4 Oct 20261mo ago
Active installations30Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Wonderful Repeated Hit Blocker for Wordfence version 1.0.1 as active, updated 1mo ago and tested up to WordPress 7.1.

Overview

About this plugin

Wordfence records every request its firewall classifies as an attack. A single

attack rarely justifies a block — but the same address showing up again and

again within a few minutes almost always does.

Wonderful Repeated Hit Blocker watches that attack log and blocks the repeat

offenders for you. You decide how many logged attacks within how many minutes

are enough, and how long the resulting block lasts.

How the blocks are created

Blocks are created through Wordfence’s own public blocking API

( wfBlock::createIP() ), not by writing into its database tables. That matters:

  • Wordfence’s allowlist is always honoured — allowlisted addresses are never blocked.
  • The block shows up in the normal Wordfence Blocking screen and can be removed there.
  • The Wordfence firewall is synchronised the same way it is for a manual block.
  • Wordfence’s own block counters stay correct.
  • Schema changes in future Wordfence releases cannot corrupt your block table.

Safety rails

  • Only requests Wordfence flagged as attacks are counted. Ordinary traffic — visitors, crawlers, your own browsing — is never part of the calculation.
  • Your own IP address is added to the plugin’s allowlist when you activate it, and the settings screen tells you if it is not covered.
  • Wordfence’s allowlist is respected in addition to the plugin’s own list.
  • Addresses that already carry an active Wordfence block are skipped, so blocks are never silently extended and alerts are never repeated.
  • Without Wordfence the plugin does nothing at all and says so with an admin notice.

Optional alerts

Set a webhook URL (Slack, Discord, Mattermost, or your own endpoint) and you

get a message for every new block. Leave the field empty and the plugin makes

no outbound connections whatsoever.

External services

This plugin contacts no external service by default.

If — and only if — you enter a webhook URL on the settings screen, the plugin

sends one HTTP POST request to exactly that URL each time it creates a new

block. The endpoint is chosen by you; this plugin is not affiliated with any

particular provider.

Data transmitted with each request:

  • the URL of your site,
  • the IP address that was blocked,
  • the number of attacks Wordfence logged for it,
  • the length of the time window in minutes.

Nothing else leaves your server. No data is transmitted while the webhook field

eu or any other

service of ours.

If you use a hosted service such as Slack or Discord as the endpoint, their

terms and privacy policies apply to the data you forward to them — for example

com/trust/privacy/privacy-policy)

com/privacy).

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • brute force
  • ip blocking
  • firewall
  • security
  • wordfence
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.2 · PHP 7.4
Update activity4 Oct 20261mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.0.01.0.1
WordPress compatibility7.17.1.2
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.