Comment spam filters
A spam filter can send a comment to an outside service
Some spam filters check comments on your WordPress site. Others send comment text, IP addresses, and email addresses to an outside service. CleanTalk can also load a bot-detector script in the visitor browser. Compare the documented setups below; your settings can change which checks run.
Based on plugin documentation, not tests of your site. Your settings can change which checks run. This is not legal advice or a compliance rating.
Scan your site for third-party requestsHow we group spam filters
We separate checks on your site from comment data sent by your server and scripts loaded in the visitor browser. Sending a comment for a spam check does not by itself show that browsing history was collected. Consent timing has not been tested, and data retention has not been assessed.
How a spam filter checks a comment
Checked on your WordPress site
Antispam Bee (default settings) and WP Armour check comments with a honeypot field and local rules on your WordPress site. Comment text is not sent to a vendor API in these setups. Antispam Bee can optionally look up a country or language from your server; those options start off.
Scored by an outside service
Akismet, CleanTalk, and OOPSpam send comment text plus the commenter IP and email from your WordPress server to their scoring APIs. Sending a comment for a spam check does not by itself show that browsing history was collected. CleanTalk visitor pages also load a bot-detector script from fd.cleantalk.org by default. That script host is not the comment-scoring API. The host column covers documented browser requests only.
Before consent
Consent timing is not tested here. A consent checkbox or cookie modal in a plugin is not a test of your site. The Before consent column is not a scan finding. The site scan linked below checks for third-party requests on your pages; it does not access your WordPress database.
Comment spam filter plugins
No paid placement. Plugins that check comments on your WordPress site appear first, then outside scoring services, then plugins not yet reviewed. Names are alphabetical within each group.
| Plugin | Documented behavior | Documented outside browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Antispam Bee This row covers Antispam Bee on default settings. Comments are checked with a honeypot field and local rules on your WordPress site. Comment text is not sent to a vendor API in this setup. Optional country and language checks can call www.iplocate.io or api.pluginkollektiv.org from your server; those options start off. Consent timing is not tested here. | Checked on your WordPress site | No outside browser host documented for this setup. Server scoring calls are a different step. | Not assessed | Not tested |
| |
| WP Armour This row covers WP Armour (Honeypot Anti Spam) when the honeypot field is inserted from a local script. The listing states there are no external API calls for spam filtering. Comment text is not sent to a vendor API in this setup. Consent timing is not tested here. | Checked on your WordPress site | No outside browser host documented for this setup. Server scoring calls are a different step. | Not assessed | Not tested |
| |
| Akismet This row covers Akismet when a comment is checked. Your WordPress server posts comment text plus the commenter name, email, IP, and browser information, plus page URL and referrer, to rest.akismet.com. Sending a comment for a spam check does not by itself show that browsing history was collected. No visitor browser host is cited for this scoring step. Consent timing is not tested here. | Comment scored by an outside service | Outside browser hosts not verified | Not assessed | Not tested |
| |
| CleanTalk This row covers CleanTalk when comment protection is on. Your WordPress server sends the comment message plus sender IP and email to api.cleantalk.org (moderate.cleantalk.org). Visitor pages load fd.cleantalk.org/ct-bot-detector-wrapper.js by default. That script host is not the comment-scoring API. Sending a comment for a spam check does not by itself show that browsing history was collected. Consent timing is not tested here. | Comment scored by an outside service | fd.cleantalk.org | Not assessed | Not tested |
| |
| OOPSpam This row covers OOPSpam when a comment is checked. Your WordPress server posts comment text plus sender IP and email to api.oopspam.com. Sending a comment for a spam check does not by itself show that browsing history was collected. No visitor browser host is cited for this scoring step. Consent timing is not tested here. | Comment scored by an outside service | Outside browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table describes the named spam-filter setups, not requests measured on your site. Sending a comment for a spam check does not by itself show that browsing history was collected. The host column covers documented visitor browser requests, not every server scoring call. Other page requests are not covered. CAPTCHA widgets and security firewalls have separate pages. Plugins marked Not reviewed have not been assessed. Consent timing has not been tested, and vendor data retention has not been assessed. The linked site scan checks for third-party browser requests; it does not access your WordPress database or verify server-to-server scoring calls.
Documentation snapshot: Oct 6, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress captcha plugin privacy
- WordPress security plugin privacy
- WordPress comment plugin privacy
- Plugin Watch
- All privacy guides
/wp-antispam-plugin-privacy