Witen Blocker — AI Crawler Control, Login Lockout & 2FA

You decide who gets into your WordPress site. Choose which AI crawlers can read your content, lock out bots guessing your password, and stop comment spam. Protection starts the moment you activate it, with no account and no setup wizard. Choose which AI crawlers read your site Every recognized crawler gets its own allow or block switch. Welcome every AI crawler, block them all, or pick one by one. Nothing is blocked until you choose. Witen Blocker recognizes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Common Crawl, Meta-ExternalAgent, Amazonbot, and Applebot, plus the major search engines and ten uptime monitors, so a rule for one bot never catches the services you rely on. robots.txt states your preference; Witen Blocker enforces it. A crawler you block gets an HTTP 403. Crawlers are matched by their published network ranges as well as their user agent, so a scraper pretending to be Googlebot doesn't get Googlebot's pass. Lock out password guessers Five failed logins in five minutes locks the address out for an hour, and you can change all three numbers. Add two-factor sign-in with any authenticator app and printable recovery codes, so a stolen password alone no longer opens your dashboard. Move the login page to an address only you know. Block known WordPress exploits Template traversal and comment exploit requests are refused before they reach the vulnerable WordPress code. No account needed. Stop comment spam without a spam service A hidden field and a timing check catch bots. No comment text ever leaves your site. Connected sites can also use a separate shared spammer list for comments. Repeated honeypot detections from different sensors and customer licenses can contribute addresses to this list. Timing checks and hits on the shared list do not contribute new shared reputation. Comments marked as spam remain in the Spam folder for review. This protection does not create login or site-wide blocks; you can turn it off in Witen > Settings. Catch unexpected file changes A daily scan checks WordPress core against the official checksums, flags new and changed files, and looks for known malware patterns. Nothing is deleted or changed without you. Connected sites also receive maintained malware catalogs. Block attackers before they reach you Connect a free Witen account and your site gets blocklists built from attacks seen across every Witen site and server. An address caught attacking other sites is blocked on yours before it tries. Requests are checked against a local copy of the list, so no page load waits on Witen. Connecting requires a Witen account and security-event sharing. Every local feature stays free, with no trial expiry. Free connected sites get a daily blocklist update. Paid plans add more sites and servers, other feed profiles, and off-site backup storage. Shared hosting or your own server On shared hosting, blocked requests get an HTTP 403 from WordPress, with no server access needed. On your own Linux server, add the Witen Warden agent and blocks move to the firewall, before the traffic ever reaches PHP. Get started: activate Witen Blocker and open Witen > Dashboard to see what's already on. Use Firewall > Bots and AI crawlers to choose which crawlers can visit, and Login to set up two-factor sign-in. Setup guide | Witen plans | Support

1. Open Plugins > Add New Plugin, search for Witen Blocker, and install and activate it. You can also upload the plugin ZIP.
2. Open Witen > Firewall and add your own IP address to the never-block list. Then choose which bots and AI crawlers to allow.
3. Open Witen > Login to set up two-factor sign-in for your account.
4. Optional: to add shared blocklists, create a Witen account, add your WordPress site from the dashboard, and enter its one-time setup token in Witen > Settings. Review the terms and privacy information before connecting. The first blocklist arrives after background maintenance runs.

See the setup guide to connect a local Warden agent or configure your site through wp-config.php.

0.6.53

• Turn on Vulnerability alerts in Settings to share your installed plugin and theme versions. Witen then lists the ones with known vulnerabilities, and the version that fixes each, on the Vulnerability Intel page. It is off until you turn it on, and only plugin and theme names and versions are sent.
• Turning Vulnerability alerts off deletes the shared list from Witen.
• Sites connected through a local Warden share the list through Warden 0.1.35 or later, only when package listing is turned on for the server too.
• Bundle Witen SDK 1.8.

0.6.52

• Check comments on connected sites against a separate shared spammer list. An address joins it only after honeypot detections from different customer licenses and sensors. Matching comments go to the Spam folder for review and never block pages or logins. Turn it off in Settings.
• Report why a stored comment was marked as spam: honeypot, timing, or the shared list. Comment text and email addresses are never sent.
• Never ban an unlisted reverse proxy on a private network. Failed logins through it are still recorded and counted. Trusted proxies now says plainly when a public address that sends forwarding headers can be banned.
• Record a correct password still waiting for its two-factor code in the audit log. It never counts as a failed login, never resets the failure count, and never lifts a ban.
• Count each failed login against the account it tried. Signing in clears only that account's failures, so a valid password for one account cannot reset the count against another. Failed logins recorded before the update keep counting.
• With a local Warden, show which blocks live in the server firewall. WordPress cannot lift those, so the blocklist no longer offers Unblock for them, and a new note gives the exact server command for each kind of block.
• Never ask a local Warden to lock out an allowlisted address after failed logins.
• Bundle Witen SDK 1.7. See changelog.txt in the download for older releases.