Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To stop an IP address from commenting, use WordPress’s built-in controls at Settings → Discussion. That blocklist filters comments; it does not stop the address from visiting the rest of your site. For a site-wide block, use a host or server access rule, a firewall/CDN control, or a suitable security plugin.
Choose the block you actually need
| Goal | Where to enforce it | What it affects |
|---|---|---|
| Stop a particular address from leaving comments | WordPress Discussion settings | Comments matching the configured keys; other site requests remain accessible |
| Prevent an address from reaching the site | Hosting/server access rule, firewall/CDN, or a plugin that configures one | Requests covered by that rule; exact scope depends on the control and configuration |
WordPress’s Discussion settings documentation describes comment matching, not a network-level block. A site-wide restriction must be enforced outside that built-in comment feature.
Block an IP address from commenting
- In your WordPress dashboard, open Settings → Discussion.
- Find the Comment Blocklist box and enter the IP address on its own line. Add other entries on separate lines.
- Save the settings.
The blocklist can match text in a comment’s content, author name, URL, email address, IP address, or browser user-agent—not just IPs. Comments matching a blocklist entry are marked as spam or deleted without warning, so a broad entry can catch legitimate comments too. The behavior and field labels are covered in WordPress’s Discussion settings documentation.
Prefer review over automatic deletion?
Use Comment Moderation keys when you want matching comments held for review rather than automatically removed. WordPress’s guide to understanding comment spam distinguishes moderation keys, which send matches to the queue, from disallowed comment keys, which delete matches immediately without notification. Starting with moderation is the less destructive choice if you are unsure whether a match will catch genuine comments.
#1 Best Overall
Block an IP from accessing the whole site
The Comment Blocklist does not deny an IP address access to pages or other requests. For a broader block, configure an access rule at the hosting or server level, or use a firewall/CDN control. A security plugin may also manage such a rule, but check where it enforces the block and whether it fits your hosting and proxy setup.
Example: a Cloudflare-integrated plugin
The WordPress.org listing for Block Logins with Cloudflare describes a plugin that adds and removes IP blocks through Cloudflare firewall rules after configured activity thresholds. The listing says it requires a Cloudflare account and valid API credentials; those requirements apply to this integration, not to WordPress IP blocking generally.
The plugin listing also says blocked IP and rule information is sent to Cloudflare’s API. Before enabling any integration with an external service, review its data and service disclosures, along with the permissions its credentials grant.
Choose an enforcement point that fits your setup
- Comments only: Use Comment Moderation for a review queue, or the Comment Blocklist when you intend to automatically filter matching comments.
- All covered requests: Use a host/server rule or edge firewall if the address should be denied access beyond commenting. Confirm the rule’s scope with your hosting provider or firewall documentation.
- Plugin-managed rules: Check the plugin’s supported WordPress and hosting configuration, required accounts or API credentials, update history, documentation, and support. The WordPress.org plugin directory recommends considering update recency, compatibility with your WordPress version, and the quality of documentation and support when assessing spam plugins.
Whichever method you choose, verify how the real visitor IP is detected in your environment, especially if traffic passes through a proxy or CDN. Misidentification can make an IP rule ineffective or target the wrong address. The reviewed options do not establish one universally best configuration; the right choice depends on the block’s scope and the site’s hosting and proxy arrangement.
Quick Recap
Best Value
- Used Book in Good Condition
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
