| 开发者 | wonderfulplugins |
|---|---|
| 更新时间 | 2026年8月24日 23:49 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
wfBlock::createIP()), not by writing into its database tables. That matters:
Yes. The plugin reads Wordfence's attack log and uses Wordfence's blocking API. Without an active Wordfence installation it stays completely inactive and shows an admin notice.
The plugin is built so that you cannot do so by accident. Your IP address is added to the allowlist when you activate the plugin, Wordfence's own allowlist is respected as well, and only addresses that Wordfence has already flagged as attackers are ever considered. Should you still end up blocked, remove the block in the Wordfence Blocking screen — every block created here is a normal Wordfence IP block.
No. Only requests that Wordfence's firewall has recorded as an attack are counted. A visitor who mistypes a password does not appear in that log.
The block reason in Wordfence starts with "Repeated Hit Blocker" and states how many attacks were logged in which time window.
Yes. Wordfence keeps a single, network-wide attack log and block list, and the plugin uses Wordfence's own table resolution, so it works the same way.
Every 5 minutes by default, configurable between 1 and 60 minutes. Scanning runs on WP-Cron, which only fires when your site receives traffic — on a very quiet site scans may happen less often than configured.
Not unless you configure a webhook URL yourself. See the "External services" section above.