Spamify – Anti-Spam, Login Security & Vulnerability Scanner

By Spamify

0+ active installationsVersion 1.3.0

Anti-spam for every form plus site security: login lockouts, one-click hardening, vulnerability scanner and core file checks. No account needed.

Description

Stop the spam. Lock every door.

Spamify protects your WordPress site in two ways at once. It stops spam on every form, and it secures the site itself with login protection, one-click hardening and a vulnerability scanner. It is one lightweight plugin instead of three, with no account, no API key and no cloud subscription.

Everything runs on your own server. Spamify never sends data to the plugin author or to any tracking service, and the free version has no limits, nag screens or trial period.

Why Spamify?

  • One plugin, two jobs. Form anti-spam and site security, from one Dashboard with one Security Score.
  • Self-contained. No sign-up, no API key and no monthly quota. Spam checks run locally on your server.
  • Guided, not overwhelming. The Dashboard shows your Security Score and how many steps are left. The Security screen walks you through each one, and most are a single switch.
  • Explains every decision. Every block shows the evidence behind it, so you never wonder why a real customer was stopped.

Form anti-spam

Spamify scores every submission and blocks or flags the ones that look fake, invalid or automated.

  • Email checks: It validates syntax and catches gibberish, keyboard-mash and fake addresses. It also asks the recipient’s own mail server whether the mailbox exists, without sending a message (on by default; see External Services).
  • Bot behaviour signals: Mouse, keyboard, scroll and focus activity, headless-browser detection and a JavaScript challenge, all collected locally.
  • Honeypot & timing: Hidden decoy fields plus a minimum fill time catch automated submissions.
  • Rate limiting: Caps submissions per IP, with per-form overrides.
  • Invisible CAPTCHA (optional): Cloudflare Turnstile or Google reCAPTCHA v3, using your own free keys.
  • Allowlist: Trusted domains, email addresses and IP / CIDR ranges always get through.
  • Review Queue: Flagged submissions from every form wait in one screen for you to approve or dismiss.

Email verification settings in one place

  • One SMTP tab: Mailbox verification, the real-time as-you-type check and the hard-block rules all live together under Settings → SMTP.

Login security

  • Limit login attempts: IPs that keep guessing passwords are locked out of wp-login.php, XML-RPC and application passwords. Repeat offenders get longer lockouts, up to 24 hours. Includes a lockout log, one-click unlock and optional email alerts.
  • Hide the login page: Moves wp-login.php to a secret address and returns a 404 at the old one and at /wp-admin/. Every login link, including those in WordPress emails, is rewritten for you. Multisite compatible.
  • Generic login errors: The login form stops telling attackers which usernames exist.

Vulnerability scanner & file integrity

  • Vulnerability scanner: Checks WordPress core and every installed plugin and theme against a free public database of disclosed vulnerabilities. Shows severity (CVSS) and the exact version that fixes each issue.
  • Daily monitoring: Re-checks every day and emails you only when something new affects your site.
  • Core file integrity: Verifies every WordPress core file against the official wordpress.org checksums. Flags modified, missing and unexpected files in wp-admin and wp-includes, the classic malware hiding places.

One-click hardening

  • Disable XML-RPC, a favourite brute-force and DDoS-amplification target.
  • Block username enumeration through author scans, the REST users endpoint, oEmbed and the users sitemap.
  • Lock the theme and plugin code editor.
  • Send security headers: X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy.
  • Hide the WordPress version.
  • Disable application passwords.

Every switch is reversible, and the Security Score tracks your progress from 0 to 100.

Dashboard, reports & privacy

  • Dashboard: Per-day charts of blocked, flagged and allowed submissions, the Security Score with a “Secure your site” shortcut, and a WP Dashboard widget.
  • Timeline: Look up any email or IP and see its full history, with the evidence behind every hit.
  • Spam Scan: Retro-checks existing user accounts and comments that predate the plugin.
  • Digest emails: A daily, weekly or monthly summary, optionally with a CSV report attached.
  • GDPR tools: Automatic log purge by retention window, IP anonymisation, and WordPress privacy exporter and eraser support.
  • Setup wizard: Get protected in about a minute.
  • Translations: German, Spanish and French included.

Works with

  • WordPress core forms: registration, comments, profile update, lost password and multisite signup
  • Contact Form 7
  • WPForms
  • Jetpack Forms
  • Elementor Forms

Need WooCommerce, Gravity Forms, Ninja Forms or Fluent Forms, a firewall or country blocking? See Spamify Pro below.

Upgrade to Pro

Spamify is free forever on WordPress.org — everything described above runs standalone, with no account, licence key, or nag screens required.

Spamify Pro adds the rest of the detection engine and site-wide protection tools for busier or higher-traffic sites:

  • Disposable domain blocking – 100,000+ throwaway and temporary-inbox providers, refreshed automatically.
  • IP threat intel & DNSBL – matches the sender’s IP against aggregated abuse feeds and DNS blocklists.
  • VPN / proxy / Tor detection – flags anonymised traffic from VPNs, open proxies, Tor exit nodes and datacenter ranges.
  • Content analysis – link stuffing, spam keywords, homoglyph and Unicode obfuscation.
  • Behavioural reputation – per-sender history layered on top of honeypot and timing.
  • Custom rules – your own if-this-then-that logic on any field or signal.
  • Network firewall – VPN/Tor/ASN blocking with escalating temporary bans.
  • Geo report & country blocking – a world map of where blocked spam comes from, powered by a free offline database.
  • Uptime monitor & deliverability tools – scheduled URL checks, bulk email-list verification, and an SPF/DKIM/DMARC checker.
  • More integrations – WooCommerce, Gravity Forms, Ninja Forms, Fluent Forms, newsletter opt-ins, and a universal connector for any form.

Plans start at $49/year for up to 3 sites, with Agency and Lifetime options for larger portfolios. Buy Spamify Pro →

External Services

Four features can connect to an external service. The vulnerability scanner and core file integrity check only run when you start them or switch on daily monitoring (Spam Shield → Security). SMTP mailbox verification is on by default (you can turn it off under Settings → SMTP); CAPTCHA verification stays off until you enable it and add your own provider keys. Neither sends any data to the plugin author.

1. SMTP mailbox verification (on by default)

When you turn on SMTP Verification (Settings → SMTP), the plugin opens a direct connection to the mail server (MX host) of the recipient email address’s own domain and performs an SMTP handshake to check whether the mailbox exists. What is sent: the email address being validated, sent only to that address’s own mail provider, and only at the moment a form containing that address is submitted or checked. No email message is ever sent, and no data is sent to the plugin author or to any third-party service. Because each address is verified against its own provider’s server, there is no single service, account, terms of service, or privacy policy involved. Turn this feature off under Settings → SMTP if you prefer that submitted addresses are never contacted.

Outbound-port connectivity probe. Many hosts block outbound port 25, which makes mailbox verification impossible. To detect this, the plugin makes a one-off TCP connection to a well-known public mail server — by default Google’s inbound MX, gmail-smtp-in.l.google.com on port 25 — and closes it immediately without sending any data. Only a yes/no “is port 25 open” result is kept (cached for up to a week). This probe runs when SMTP verification is enabled, and when you open the Advanced settings tab or the Tools → Site Health screen (so the status can be shown). No personal data is transmitted. You can change or disable the probe host with the spamify_port25_probe_host filter.

2. CAPTCHA verification (optional, disabled by default)

If you enable CAPTCHA (Settings → Bot Protection) and enter your own provider keys, the visitor’s CAPTCHA token is sent to your chosen provider’s verification endpoint so the provider can confirm the visitor is human:

  • Cloudflare Turnstile – token sent to https://challenges.cloudflare.com/turnstile/v0/siteverify. Terms: https://www.cloudflare.com/website-terms/ — Privacy: https://www.cloudflare.com/privacypolicy/
  • Google reCAPTCHA v3 – token sent to https://www.google.com/recaptcha/api/siteverify. Terms: https://policies.google.com/terms — Privacy: https://policies.google.com/privacy

Only the CAPTCHA token and the visitor IP are sent, only on form submission, and only if you have configured a provider. This feature is off until you supply keys.

3. Vulnerability scanner (optional, runs only when you click “Scan now” or enable daily monitoring)

The plugin asks the free WPVulnerability database (https://www.wpvulnerability.net/) whether known vulnerabilities exist for your installed WordPress version and each installed plugin and theme. What is sent: only the component slug (e.g. contact-form-7) or the WordPress version number — no visitor or user data. Results are cached for 12 hours. Terms & privacy: https://www.wpvulnerability.net/

4. Core file integrity check (optional, runs only when you click “Check now” or enable daily monitoring)

The plugin downloads the official MD5 checksums for your WordPress version from WordPress.org (https://api.wordpress.org/core/checksums/1.0/) using WordPress’s own get_core_checksums() function — the same request WordPress itself makes during core updates. Only the version number and locale are sent. Privacy: https://wordpress.org/about/privacy/

Installation

  1. Upload the spamify folder to the /wp-content/plugins/ directory, or install it through the Plugins screen in WordPress.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Open Spamify in the admin menu and follow the setup wizard to configure protection.

FAQ

Does this plugin send any data to your servers?

No. Spamify never contacts the plugin author’s servers, and it sends no data to any analytics or tracking service. It runs on your own site. The only outbound connections are those described in External Services — SMTP mailbox verification and its port-25 connectivity probe (verification is on by default; you can turn it off under Settings → SMTP), and CAPTCHA verification (off until you add your own keys).

Is SMTP verification required?

No. It is on by default, but you can turn it off under Settings → SMTP. The plugin still validates syntax and protects your forms with the honeypot, timing, rate-limiting, allowlist, and CAPTCHA features without it.

Which PHP version is required?

PHP 7.4 or higher.

Why are some submissions marked “unverifiable”?

Many hosts block outbound port 25, and many mail servers greylist or use catch-all addresses, so a mailbox cannot always be confirmed. By default these are flagged for review rather than blocked; you can change this in Settings.

Is there a Pro version?

Yes. Spamify Pro adds the rest of the detection engine (disposable-domain blocking, IP threat intel, VPN/Tor detection, content analysis, custom rules), a network firewall, a geo report, deliverability tools, and integrations for WooCommerce, Gravity Forms, Ninja Forms and Fluent Forms. The free version on WordPress.org is fully functional on its own and is not a limited trial. See spamify-pro.github.io or Buy Spamify Pro.

I hid my login page and locked myself out. What now?

Add define( 'SPAMIFY_HIDE_LOGIN_DISABLE', true ); to your wp-config.php. wp-login.php works normally again, and you can change or switch off the setting from Protection → Hide login.

The login limiter locked me out. What now?

Wait for the lockout to end, log in from another network and unlock your IP under Security → Login security, or add define( 'SPAMIFY_LOGIN_LIMIT_DISABLE', true ); to wp-config.php. Add your own IP to the Allowlist (Protection → Advanced filters) so it is never locked again.

Is Spamify a replacement for Wordfence, Patchstack or CleanTalk?

Spamify covers form anti-spam, login brute-force protection, hardening, vulnerability alerts and core integrity checks in one free, self-contained plugin with no account or cloud subscription. It does not include a malware signature scanner or virtual patching; if you need those, Spamify can run alongside other security plugins (turn off overlapping features such as login limiting in one of them).

Does hiding the login work on multisite?

Yes. Every site in the network sets its own address on its own Protection screen, and on a subdirectory network the address lives under that site’s folder (example.com/team/secret-login/). To use one address everywhere, add define( 'SPAMIFY_HIDE_LOGIN_SLUG', 'secret-login' ); to wp-config.php. wp-signup.php and wp-activate.php stay reachable so registration and activation keep working. The feature needs pretty permalinks.

Screenshots

Changelog

1.3.0 (2026-11-10)

  • New Security screen (Spam Shield → Security) with five sections: Security score, Login security, Hardening, Vulnerabilities and File integrity.
  • New: Security Score (0–100) with a checklist and “Fix it” links; also shown as a card on the Spamify Dashboard.
  • New: “Secure your site” panel on the Spamify Dashboard shows the Security Score, how many steps are left, and a button to the Security settings.
  • New: Limit login attempts — per-IP lockout after repeated failed logins across wp-login.php, XML-RPC and application passwords, escalating on repeat offences, with a lockout log, per-IP unlock and optional email alert.
  • New: Vulnerability scanner for core, plugins and themes, with severity, CVSS score and fixed-in version; optional daily re-scan with email alerts for newly affected components.
  • New: Core file integrity check against the official wordpress.org checksums, including unexpected files in wp-admin / wp-includes; optional daily check with email alerts.
  • New: One-click hardening — disable XML-RPC, block username enumeration, generic login errors, disable the code editor, security headers, hide the WordPress version, disable application passwords.
  • Changed: one SMTP settings tab now holds everything about checking a submitted email address: mailbox verification and its hard-block threshold (from Advanced filters), Real-time validation and the Hard-block rules (each formerly its own tab). Old links to those tabs open the SMTP tab.
  • Fixed: on sites whose admin language is not English (e.g. German, Spanish, French), the Protection, Activity, Spam Scan and Tools screens loaded without their stylesheet and scripts, because the translated menu title changed WordPress’s internal page names.
  • Fixed: the setup wizard showed some icons hundreds of pixels wide (Welcome, Detection, Security and Done steps), because the wizard page did not include the icon sizing rule; its CSS/JS now also refresh in the browser cache whenever they change.

1.2.0 (2026-10-16)

  • Added German (de_DE), Spanish (es_ES), and French (fr_FR) translations covering the admin screens and the visitor-facing form messages.
  • Per-zone rate-limit overrides — give a specific zone (e.g. comments) its own, independent submission budget instead of sharing the global limit.
  • Honeypot and “submitted too fast” detections can now be set to flag-for-review instead of always hard-blocking (Settings > Bot Protection).
  • SMTP mailbox checks that get a temporary/greylisting response now get one automatic re-check a few minutes later, instead of caching the inconclusive result for a full hour.
  • A “Hide Login Attempts” stat card now appears on the Dashboard when Hide Login is enabled, showing today’s and this week’s denied probes against the real login address.
  • Spam Scan: a new “Review candidates” filter surfaces accounts the scan reports as clean but that have prior flagged or blocked activity on file — a signal that would otherwise be buried in individual evidence rows.
  • “Send test digest now” button (Settings > Alerts & Logging) previews the digest email immediately, regardless of the digest toggle or how quiet the period has been.
  • “Run GDPR purge now” button applies the configured retention window immediately instead of waiting for the nightly automatic purge.
  • The Review Queue’s “Dismiss all” clears every currently-filtered flagged submission in one action instead of one at a time.
  • The onboarding wizard’s “Zones” step now pre-checks a form-plugin zone only when that plugin is actually active on the site, instead of defaulting every zone on regardless of what’s installed.
  • Fixed: the honeypot’s “submitted too quickly” message never actually appeared to a blocked visitor — a text-matching bug always fell back to the generic blocked message instead.
  • Fixed: a domain with no mail server at all (no MX or A record) was only flagged, never blocked, even though this is a more certain “cannot receive email” signal than an explicit SMTP rejection, which was already hard-blocked.
  • Fixed: the Real-Time Check Mode setting offered “fast” and “full” as separate choices that were actually identical; the redundant option has been removed (existing sites already set to “full” are unaffected).
  • Fixed: the settings written on first activation could silently differ from “Reset to Defaults” on the same install (e.g. the IP-anonymisation and log-retention defaults disagreed) — both now come from the same single source.

Internal / Maintenance
– The Dashboard’s stat-cards row was extracted into its own class to keep the Dashboard page under the project’s per-file size limit.
– The Spam Scan results table gained a new indexed column (DB schema v15) to support the “Review candidates” filter above — upgrades automatically on activation, no action needed.

1.1.0

New Features
– The Activity screen’s banner now appears on every tab (Log, Review Queue, Timeline, and any Pro-contributed section), not just the Log tab.
– A loading indicator now shows for every AJAX action and full page navigation/refresh across the admin screens.

Security Fixes
– Re-audited every AJAX endpoint to confirm nonce verification and capability checks are in place.

Other Fixes
– Flag Threshold and Block Threshold now behave distinctly on real form submissions. Previously, “Strict — reject unverified on submit” (on by default) escalated any score at or above the Flag Threshold straight to a hard block, so the Block Threshold had no real effect and the Review Queue never received real submissions. Flag Threshold now genuinely means “allow, but mark for review”; only the Block Threshold rejects.
– The admin banner is now light instead of dark, matching the rest of the admin UI.

Internal / Maintenance
– Internal code-quality refresh. Every source file is now under 400 lines, large admin pages and engine layers were split into focused, single-responsibility files, and the admin stylesheet was broken into per-screen partials — no behaviour or settings change.
– JavaScript is now internationalised through the standard wp.i18n API (with wp_set_script_translations), so every user-facing string in the browser is translatable; all named callbacks, added file-level documentation, and no anonymous functions remain.

1.0.1

  • New Feature: Continuous Spam Scan — retro-scanning legacy accounts/comments now survives a page reload or navigating away instead of stopping, and Pause/Resume picks up exactly where it left off rather than starting over.
  • New Feature: Behavior & Bot Signals detection layer — scores headless/automation-browser detection, keystroke rhythm, mouse/keyboard/focus activity, and a JavaScript challenge, all collected locally on every form with no third-party service involved.
  • New Feature: Review Queue — every currently-flagged submission across comments, registrations, profile changes, and every connected form, in one screen instead of scattered across the native Comments/Users screens.
  • New Feature: Visual “why was this blocked” Timeline per IP/email — chronological history of every hit from that address across all zones.
  • New Feature: A “Spamify” dashboard widget on the core WP dashboard (wp-admin/index.php) — today’s and this week’s blocked/flagged counts at a glance, no need to visit the plugin page.
  • New Feature: Digest emails can now be sent daily, weekly, or monthly, optionally with a CSV summary report (totals, source breakdown, top offending domains) attached.
  • Fix: The Activity Log’s “Delete entry” button did not actually delete the log row.
  • Fix: The Spam Scan page’s “no offline Tor/ASN dataset” notice rendered as a garbled, unreadably narrow box instead of a normal banner.

1.0.0

  • Initial release.
  • Feature: Hide login — serve wp-login.php from a custom address and answer the old one, plus /wp-admin/ for logged-out visitors, with the theme’s 404 page, a home-page redirect, or a URL of your choice. All generated login/logout/lost-password/registration links are rewritten automatically.
  • Multisite: per-site login addresses, subdirectory-network aware matching, network-level links resolve against the main site, and an optional SPAMIFY_HIDE_LOGIN_SLUG constant enforces one address across the whole network.
  • Major: syntax validation, optional SMTP mailbox verification (off by default), honeypot & timing, per-IP rate limiting, allowlist, invisible CAPTCHA (bring your own keys), GDPR log tools, Site Health checks, and a setup wizard. Integrations for WordPress core forms, Contact Form 7, WPForms, Jetpack Forms, and Elementor Forms.