SaaS والبرمجيات · Hushfort
WordPress security plugin: login, spam and fake signup protection
Hushfort is a modular WordPress security plugin built by Tati Creative: hidden login URL, attempt limits, 2FA, XML-RPC and username leak hardening, a CAPTCHA-free spam shield, fake signup protection request flood protection and Declutter, which finds the plugins you don’t use, in one dashboard.
Hushfort
حماية شاملة لـ WordPress
من تطوير Tati Creative
- رابط دخول مخفي (يخفي wp-login وwp-admin)
- حد للمحاولات حسب IP، وحظر وتنبيهات بالبريد
- مصادقة ثنائية (TOTP، رموز استرداد)
- حظر XML-RPC وهجمات multicall بالقوة الغاشمة
- إغلاق تسريبات أسماء المستخدمين (REST، المؤلف، خريطة الموقع)
- فحص للسطح مع أدلة إصلاح
Hushfort
حماية شاملة لـ WordPress
The day a WordPress site goes live, bots find it: password guessing on wp-login.php, bulk login attacks through xmlrpc.php, spam in comments and contact forms, thousands of fake user accounts overnight. Most owners only notice when the server slows down, the mail quota runs out or ‘new user registration’ emails start piling up.
Hushfort solves these problems with modules that know about each other instead of a pile of separate plugins. Hide Login, Limit Login & Alerts, Two-Factor Authentication and Surface Hardening cover the login side; Spam Shield, Registration Protection and Load Protection guard forms, signups and server resources; Declutter finds installed plugins and themes that do nothing, with evidence. All of them share the same IP resolution, the same allowlist and the same event log.
The plugin grew out of real incidents on Tati Creative’s own sites and client projects. On the West Riders Custom store, password attempts kept arriving through XML-RPC despite the hidden login URL; the Surface Hardening module and the Surface Scan, which measures with real requests, were written after that incident. Registration Protection was built in response to a flood of fake signups on another site.
Hushfort uses no CAPTCHA, sends no telemetry and loads no third-party code; form and comment data never leave your server. Spam, Registration and Load modules have a monitor mode (Load Protection starts in it): the module only logs for a few days, and you switch to enforcement once you see no false positives. No module ever blocks a WooCommerce checkout.
المشكلات التي يحلّها
Endless login attempts on wp-login.php
The default login URL is public knowledge; bots guess passwords around the clock and fill your server and logs. Hushfort moves the login to a secret path you choose, old addresses return 404, and remaining attempts are stopped with IP-based lockouts.
Hidden login URL, yet attacks keep coming
xmlrpc.php is a separate, fully privileged login door; hiding the login page does not close it, and system.multicall lets attackers try many passwords in one request. The Surface Hardening module closes XML-RPC logins without breaking pingbacks and rejects multicall requests.
Usernames are publicly exposed
WordPress publishes login names through the REST users endpoint, the ?author=1 redirect, the sitemap and oEmbed, doing half the attacker’s work. Hushfort closes these sources, unifies login error messages and shows leaked usernames by name in its Surface Scan.
Comment and contact form spam
Bot messages pour into comments, product reviews and form plugins such as Elementor, while CAPTCHAs annoy real visitors. Spam Shield filters bots with an invisible honeypot field, a minimum fill time and a signed token, and quarantines suspicious but possibly human submissions instead of deleting them.
Thousands of fake user registrations
On a site with open registration, bots can create thousands of accounts per hour; each one triggers a welcome email, burns SMTP quota and bloats the database. Registration Protection stops the flood with hourly limits per IP and network, a site-wide cap and a circuit breaker, and its Cleanup Wizard removes existing fake members with a backup.
Request floods slow the site down
Search requests, 404 scanning, form posts and fake Googlebot traffic choke PHP and the database. Load Protection gives each IP a per-minute point budget, pauses anyone over budget with a 429 for a few minutes and runs this check before the theme and plugins load.
Fear of locking yourself out
The biggest risk of any security plugin is the owner locking themselves out. In Hushfort, hiding does nothing while the slug is empty, the dashboard has an ‘if you lose access’ card, and a single line in wp-config.php instantly overrides the login path or 2FA.
الوحدات والميزات
Hide Login
Hides wp-login.php and wp-admin; the login opens only on the secret path you choose. Requests to the old addresses get a 404 or a redirect, and login links across the site automatically point to the new path.
- Secret login path entered on the settings screen
- Blocked access shows a 404, the home page or a custom URL
- admin-ajax, REST API, WP-Cron and required admin-post flows keep working
- Does nothing while the slug is empty, so no accidental lockout
- Emergency login path via a wp-config.php constant
- Step-by-step guidance on first setup
Limit Login & Alerts
Counts failed logins per IP and locks out once a threshold is reached, with longer lockouts for repeat offenders. Sends an email alert on lockout and keeps every event in a filterable history.
- Configurable attempts, time window and lockout duration
- Long lockouts for repeated attacks
- Counting by IP or by IP plus username
- Correct client IP behind Cloudflare and proxies, protected against header spoofing
- IP allowlist and manual IP blocking
- SMTP-aware email alerts to multiple addresses
- Failed 2FA and application password attempts also count
- Timeline and login history with a source column
Two-Factor Authentication (2FA)
A TOTP-based second step that works with authenticator apps. The QR code is generated inside the plugin with no request to any outside service, and recovery codes keep you in if you lose your phone.
- Works with TOTP apps such as Google Authenticator
- Built-in QR code and manual key
- 10 single-use recovery codes, downloadable and printable
- Secret key stored encrypted and signed in the database; if the security keys (salts) change, 2FA never silently switches off — login asks for a recovery code
- Each user starts setup from the Two-Factor section on their profile page; admins without 2FA get a reminder
- Admins can reset 2FA from the users list
- Emergency disable constant for wp-config.php; optional GATEKEEPER_2FA_KEY for salt-independent encryption
Surface Hardening
Closes the doors that bypass the hidden login URL and the endpoints that leak usernames. Each setting explains what it does and which integrations it might affect.
- XML-RPC: block logins (keep pingbacks), disable fully, block only multicall, or leave as is
- Blocks bulk password guessing via system.multicall
- REST /wp/v2/users closed to logged-out visitors (editor unaffected)
- Blocks ?author=N scans, keeping or fully disabling author archives
- Removes the sitemap author list and oEmbed author data
- Uniform login error message (lockout notices kept)
- Optionally disable application passwords
- Blocked probes logged to the history
Surface Scan & security dashboard
The dashboard looks at what your site actually exposes rather than what the settings claim: it sends real requests to your own site to measure XML-RPC, the REST users list, author scanning, the sitemap and application passwords. Every open point appears as a red card with a ‘What should I do?’ guide.
- Security Layers overview: every module’s status at a glance
- Shows leaked usernames by name
- Finds accounts whose username equals their display name
- ‘Fix’ link from each finding to the right setting
- Issue-specific guide: what it does, how it is abused, how to fix it
- Step-by-step ‘if an account was compromised’ recovery guide
Spam Shield
Protects comments, WooCommerce product reviews and form plugins without CAPTCHA. Visitors solve nothing and no data is sent to outside services; suspicious submissions go to quarantine, and marking one as ‘not spam’ teaches the shield that IP and email.
- Supports Elementor Pro, Contact Form 7, WPForms, Gravity Forms, Fluent Forms and Forminator
- Invisible honeypot field, minimum fill time, signed token unaffected by page caching
- Hourly limit per IP and per email (Gmail dot and +tag tricks count as one address)
- Disposable email domain list, link count and banned word filters
- Denylist for IPs, CIDR ranges, emails and domains
- Protected / Closed / Untouched modes for comments and reviews, pingback switch
- Strict mode for forms like newsletters: only major email providers
- Monitor mode, retention period, hooks into GDPR export and erase tools
Registration Protection
Layered defence against fake signup floods: WordPress registration, WooCommerce My Account and other plugins’ signup forms are covered. A suspicious account created during checkout is never rejected but opened as pending, so the order always goes through.
- Hourly signup limit per IP (IPv6 /64) and per network (IPv4 /24, IPv6 /48)
- Site-wide hourly cap with circuit breaker against distributed floods
- Soft mode: new accounts wait for approval and receive no email
- Disposable email blocking and email uniqueness against Gmail variations
- Invisible bot traps on signup forms (never on checkout)
- Early gate: IPs over the limit get a 429 before theme and plugins load
- Pending account approval screen and automatic deletion
- Cleanup Wizard: preview, back up, bulk delete, restore within 30 days
Load Protection
Keeps request floods from choking the server. Each IP has a per-minute point budget, and expensive requests (search, forms, XML-RPC, 404s) cost more. The check runs before the theme and plugins load, with counters kept in APCu when available.
- IPs over budget get a 429 with Retry-After for a few minutes
- Pages served from cache cost no points
- WooCommerce checkout and payment gateway callbacks pass even for banned IPs
- Blocks fake Googlebot/Bingbot; real search crawlers are exempt
- Extra points for bots scanning for 404s
- Monitor mode (default) and a self-expiring emergency mode
- Optional Cloudflare ‘Under Attack’ automation
- Alert email and a ‘where protection runs’ indicator
Declutter
Finds installed plugins and themes that do nothing, with evidence such as ‘35 Elementor widgets, none used anywhere, loads 886 KB on every page’. It shows what share of your page code is wasted, and nothing changes until you confirm.
- Unused plugins and themes, with evidence
- Wasted share of page code: red at 15% or more, orange 5–15%, yellow under 5%
- Two-step, reversible removal
- Background plugins such as cache, SEO, email and backup are never called unused
- When unsure it says ‘Can’t tell’ instead of guessing
- WP-CLI: wp hushfort declutter
Safe by design & recovery
A security plugin should never lock the owner out. In Hushfort every module is switched on separately, returns to WordPress defaults when turned off, and file-based escape routes exist for emergencies.
- Override the login path from wp-config.php with GATEKEEPER_LOGIN_SLUG
- Disable 2FA in an emergency with GATEKEEPER_2FA_DISABLE
- Copyable ‘if you lose access’ card on the dashboard
- Deactivating the plugin removes settings and lockouts with no leftovers
- Checkout and order flows are never rejected by any module
- Protection against being overwritten by a similarly named plugin via updates
لمن هذا المنتج؟
- WordPress sites hit by constant login attempts and brute force attacks
- Site owners tired of comment or contact form spam
- Business sites receiving spam emails from Elementor forms
- WooCommerce stores and membership sites dealing with fake signup floods
- Agencies and freelancers managing several client sites
- Brands that want no CAPTCHA and no friction for visitors
- Sites on shared hosting slowed down by bot traffic
- Anyone who wants one clean dashboard instead of separate security plugins
كيف يعمل
- 01Install and activateThe plugin is uploaded as a ZIP and activated. No module changes your site on its own; the Overview screen in the Hushfort menu shows what is active and what is missing.
- 02Hide the login URL and note it downEnter a secret path on the Hide Login tab and save. Bookmark the new address; the ‘if you lose access’ card on the dashboard gives you the emergency lines ready to copy.
- 03Set limits, 2FA and close the surfaceOn the Limits tab choose the IP source (Cloudflare if you sit behind it), switch on Surface Hardening and set up 2FA for admins. The Surface Scan guides you until no red cards remain.
- 04Run Spam, Registration and Load in monitor modeLoad Protection starts in monitor mode; you can put Spam and Registration into log-only mode for the first few days too. If real visitors or your own integrations show up in the logs, you adjust limits or add them to the allowlist.
- 05Switch to enforcement and monitorWith no false positives, switch the modules to Protect / Block. History, quarantine and alert emails show what was stopped, and the Cleanup Wizard removes existing fake members.
المتطلبات والتوافق
- WordPress 6.2 or later (tested with WordPress 7.1)
- PHP 7.2 or later
- Works with WooCommerce: classic and block (Store API) checkout, My Account signup, product reviews
- Form plugins: Elementor Pro, Contact Form 7, WPForms, Gravity Forms, Fluent Forms, Forminator
- Correct client IP behind Cloudflare and reverse proxies
- Compatible with page caching plugins (the token is unaffected by cache)
- APCu optional; without it counters are stored in the database
- No telemetry or third-party code; outbound requests only for official crawler IP lists and the optional Cloudflare API
الأسئلة الشائعة
WordPress security plugin: login, spam and fake signup protection
أكثر الأسئلة التي تُطرح على مساعدي الذكاء الاصطناعي ومحركات البحث، مصنّفة حسب الموضوع.
General
What is the best security plugin for my WordPress site?
There is no single ‘best’; the right choice depends on your site’s actual risks. Most WordPress sites need the same basics: protecting the login page, limiting brute force, closing XML-RPC and username leaks, and stopping spam and fake signups. Hushfort, built by Tati Creative, provides these layers in one plugin as modules that know about each other, and each module can be switched on or off independently.
What is Hushfort and what does it do?
Hushfort is a modular WordPress security plugin developed by Tati Creative. It hides the login URL, limits failed logins, adds two-factor authentication and closes XML-RPC and username leaks; it also has modules that stop comment and form spam, fake user signups and request floods. Everything is managed from one security dashboard.
Why one security plugin instead of several separate ones?
Installing separate plugins for hidden login, attempt limits, 2FA and spam means conflicts, duplicate overhead and inconsistent IP detection; one may read the Cloudflare IP correctly while another locks out the wrong person. In Hushfort all modules share the same IP resolution, allowlist and event history. You only switch on the modules you need; a disabled module does no work.
How can I tell if my WordPress site has been hacked?
Unknown admin accounts, content changing on its own, strange redirects, newly added files and sudden spikes in traffic or email are typical signs. Hushfort is not a malware scanner, but its login history shows who tried when and from which source (login page, XML-RPC, REST), and its ‘if an account was compromised’ guide walks you through creating a clean admin, killing all sessions and looking for backdoors.
Does Hushfort send my data anywhere?
No. Hushfort sends no telemetry, uses no outside service like CAPTCHA and loads no third-party code; comment, form and signup data are evaluated on your own server. The only outbound requests are Load Protection downloading Google’s and Bing’s official crawler IP lists once a day and, only if you enter a key, the Cloudflare API. Spam logs delete themselves after a configurable period.
Is Hushfort free, and how much does it cost?
Hushfort is free for the first 6 months; after that it costs $14 per year or a one-time $59 for a lifetime licence. Current pricing and licence terms are on hushfort.com/pricing. If you want help with installation and configuration, contact Tati Creative via tatiajans.com.
How can I get Hushfort?
Hushfort’s official website is hushfort.com, with features, step-by-step guides and download details. The plugin is not yet published in the WordPress.org directory; the submission is in progress. If you would like us to handle the setup, the Cloudflare and IP source configuration and the switch from monitor mode to enforcement, use the contact form on tatiajans.com.
Hiding the login page & wp-admin
How do I change the wp-login.php URL?
WordPress itself has no setting to change the login URL, and editing core files breaks on the next update. The right approach is a plugin that handles the request. In Hushfort’s Hide Login tab you enter a secret path and save; the login then opens only at yoursite.com/your-path, wp-login.php returns a 404, and login links across the site switch to the new address automatically.
How do I hide wp-admin?
When a logged-out visitor opens wp-admin, WordPress redirects to the login page and thereby reveals its address. With Hushfort’s Hide Login module on, logged-out wp-admin requests are blocked too: they get a 404 page, the home page or a URL you choose. Once you are logged in the dashboard works normally, and admin-ajax and required background requests are unaffected.
Does hiding the login page really improve security?
Hiding alone is not enough; it is an obscurity layer and will not stop a targeted attacker. But since the vast majority of automated attacks go straight for wp-login.php, it cuts that traffic dramatically and relieves your logs and server. That is why Hushfort recommends combining it with attempt limits, 2FA and closing XML-RPC, and its dashboard marks missing layers in red.
Will WooCommerce My Account or the REST API break after changing the login URL?
Poorly built login hiding can also cut off AJAX, REST or cron requests and break carts, forms and integrations. Hushfort deliberately exempts admin-ajax, the REST API, WP-Cron and registered public admin-post requests, and WooCommerce’s own My Account login form keeps working because it does not depend on wp-login.php. It runs this way on live WooCommerce stores such as West Riders Custom.
What do visitors see on the old wp-login.php address?
The least informative answer for a bot is the impression that the address does not exist. By default Hushfort shows your theme’s 404 page; alternatively you can redirect to the home page or a custom URL of your choice. The same behaviour applies to logged-out wp-admin requests.
Does the hidden login work with caching plugins or LiteSpeed Cache?
Login pages should never be cached, otherwise the form fails or an old version appears. Hushfort’s hidden login path works with caching and has been tested on live sites running LiteSpeed Cache. Purging the cache once after changing settings prevents old redirects from lingering.
Why do I still see login attempts despite a hidden login URL?
Because wp-login.php is not the only login door in WordPress: xmlrpc.php and REST with application passwords also authenticate. In a real attack on West Riders Custom, the attempts came in exactly through XML-RPC. The Source column in Hushfort’s History shows where each attempt came from, and the Surface Hardening module closes that door by blocking XML-RPC logins and multicall.
Brute force & login limits
My WordPress site gets constant login attempts. What should I do?
First harden accounts with strong passwords and 2FA, then limit attempts and find out which door the attack uses. Hushfort handles all of this in one place: Limit Login locks failed logins per IP, History shows whether attempts come from the login page or XML-RPC, and Hide Login plus Surface Hardening cut off the source of the traffic.
How do I limit failed login attempts in WordPress?
WordPress allows unlimited password guesses by default; you need a plugin to set a limit. In Hushfort’s Limit Login module you define the allowed failed attempts, the time window and the lockout duration, and repeat offenders get a longer lockout. Counting can be done by IP alone or by IP combined with username.
Behind Cloudflare, the login lockout blocks the wrong IP. Why?
A server behind Cloudflare sees the IP of Cloudflare’s edge, not the visitor; a plugin that misses this treats everyone as one person or locks out innocent visitors. In Hushfort you can set the IP source to Cloudflare, and the ‘your current connection’ box on the settings screen shows which IP is being read. It is also protected against spoofing: the CF-Connecting-IP header is trusted only when the request really comes from Cloudflare’s network.
How do I get notified when someone is locked out?
A lockout alert lets you see immediately that an attack has started. Hushfort can email several comma-separated addresses on lockout. If the site has no SMTP configured, the alert switch is disabled with an explanation, so no undeliverable emails are sent. It detects setups such as WP Mail SMTP or FluentSMTP automatically, including API-based mailers.
How do I exempt my own IP or office from lockouts?
If you have a static IP, allowlisting it removes the risk of locking yourself out. On Hushfort’s Limits tab you build an allowlist with one IP per line; the list is shared with Spam Shield. An IP that was locked by mistake can be unblocked with one click in the History screen.
Where can I see the history of login attempts?
WordPress does not log failed logins. Hushfort’s Overview shows a 14-day timeline and summary cards, while the History tab lists active blocks, attempted usernames and a filterable combined event list. Each event’s source (login page, XML-RPC, REST, author scan) has its own column, and you can block or unblock IPs manually from there.
The login error says the username is correct. Is that a vulnerability?
Yes, a small but real one: WordPress distinguishes ‘unknown username’ from ‘incorrect password’, so attackers learn which usernames exist. Hushfort’s Surface Hardening module reduces these identity errors to one uniform message, while useful notices such as the lockout countdown are preserved.
Two-factor authentication (2FA)
How do I add two-factor authentication (2FA) to WordPress?
WordPress core has no 2FA; you add an authenticator-app second step with a plugin. After enabling Hushfort’s Two-Factor module, each user scans a QR code with their phone app on their own setup page, confirms with the 6-digit code it generates and stores their recovery codes. From then on the code is requested after the password.
Which authenticator apps does it work with?
Hushfort uses standard TOTP (RFC 6238), so it works with all common apps that generate time-based codes, such as Google Authenticator. If the QR code cannot be scanned, the displayed manual key can be typed into the app. No SMS is used, which removes the risk of SIM swapping.
I lost my phone and 2FA locks me out. What now?
There are three ways out. You can log in with one of the single-use recovery codes issued at setup; another administrator can reset your 2FA from the users list; or, if no admin is left, add define( 'GATEKEEPER_2FA_DISABLE', true ); to wp-config.php to switch 2FA off temporarily. After logging in, remove the line and set up 2FA again.
Can the 2FA code be brute-forced too?
A 6-digit code could in theory be guessed with unlimited attempts, so the second step must be limited too. In Hushfort each verification session allows only a limited number of code attempts and is cancelled once that is exceeded. Failed 2FA attempts also feed the Limit Login counter, so a repeating IP gets locked out just like on a normal login.
Are the 2FA secrets stored securely?
If 2FA secrets leak in plain text with a database dump, the second factor becomes worthless. Hushfort stores secrets encrypted with AES-256 using a key derived from your site’s own security keys, and recovery codes are kept only as hashes, each usable once. Because the QR code is generated inside the plugin, the secret never goes to an outside service.
Is 2FA mandatory for all users?
Forcing 2FA on customer and subscriber accounts makes buying harder in most stores; the real risk lies with privileged accounts. In Hushfort 2FA is optional for every user, while administrators without 2FA see a dashboard notice that starts the setup directly. The Security Layers overview flags missing admin 2FA as a point needing attention.
Spam (comments & forms)
How do I stop WordPress comment spam?
Almost all comment spam comes from bots; the fix is either to close comments or to filter the bots. Hushfort’s Spam Shield offers three modes for post comments and product reviews: Protected (open, bots filtered), Closed (form, list, REST and admin menu removed completely) and Untouched. In Protected mode an invisible honeypot, a minimum fill time, link count and banned word checks apply, and pingbacks can be closed separately.
I get spam emails from my Elementor form. How do I block them?
Elementor Pro forms offer a built-in honeypot, but bots often get past it and every submission lands in your inbox. Hushfort’s Spam Shield hooks into Elementor Pro form validation: an invisible honeypot, a minimum fill time, a signed token unaffected by page caching, hourly IP and email limits and a disposable email check apply. Bot submissions are stopped before any email is sent, and suspicious ones go to quarantine.
Can form spam be blocked without reCAPTCHA?
Yes. reCAPTCHA annoys visitors, can lower conversions and sends data to an outside service. Hushfort works without asking visitors to solve anything: an invisible field that bots fill in, a timing check that catches submissions faster than any human, and a single-use signed token fetched via JavaScript work together. All evaluation happens on your own server.
Does it also stop spam in Contact Form 7, WPForms or Gravity Forms?
Each form plugin has its own spam hook, and configuring them one by one is tedious. Hushfort’s Spam Shield protects installed Elementor Pro, Contact Form 7, WPForms, Gravity Forms, Fluent Forms and Forminator forms with a single switch, using the same rules and limits for all. The quarantine list also shows which form a submission came from.
Fake email addresses keep signing up to my newsletter form. What can I do?
Newsletter forms are the easiest target for bots because they only have an email field. With Hushfort’s strict mode you list the form by name; that form then accepts only addresses from major email providers (an editable list), and everything else goes to quarantine. This mode is not recommended for contact forms that receive real customer requests, because company addresses would be caught too.
What happens if the spam filter blocks a real customer message?
Every filter makes mistakes now and then; what matters is that false positives are not lost. Hushfort rejects clear bot signals but never deletes suspicious submissions that could be human; it quarantines them. When you mark one as ‘not spam’, that IP and email are learned. On a new install, monitor mode lets you log for a few days and see in advance what would be blocked.
Is the spam protection compliant with GDPR?
Sending personal data to an outside spam service creates extra obligations under GDPR. Hushfort sends no submissions anywhere; blocked and quarantined records delete themselves after the number of days you set. It also hooks into WordPress’s personal data export and erase tools, so a person’s data can be found and erased on request. The legal assessment itself remains your site’s responsibility.
Fake registrations
How do I block fake user registrations in WordPress?
Fake signups usually come from bots calling the registration form directly; no single measure is enough, you need layered defence. Hushfort’s Registration Protection combines invisible bot traps, hourly limits per IP and network, a site-wide cap with circuit breaker, disposable email blocking and email uniqueness. It covers WordPress registration, the WooCommerce My Account form and signup forms of other plugins it does not specifically know.
Thousands of fake members signed up overnight. What should I do?
First stop the flood, then safely clean up the existing fake accounts. With Hushfort’s Registration Protection on, the circuit breaker trips once the site-wide hourly cap is exceeded, and IPs over the limit are cut off with a 429 at the early gate, before the theme and plugins load. The Cleanup Wizard then previews customer and subscriber accounts with no orders, comments or posts, backs them up and deletes them in batches; anything removed by mistake can be restored within 30 days.
Fake signups are eating up my SMTP quota. How do I prevent it?
Every new account triggers a welcome email and an admin notification; thousands of fake signups can exhaust sending quotas such as Gmail or Workspace in minutes and stop your real order emails too. In Hushfort’s soft mode, when the breaker trips registration stays open but new accounts wait for approval and receive no email. So even during an attack, your quota is left for order and password emails.
Does registration protection block WooCommerce checkout?
In stores that create accounts at checkout, a registration check that throws an error means a lost order, which is why many registration protections break checkout. Hushfort never rejects an account created during checkout: if it looks suspicious it is created as pending and the order goes through. This has been tested with both classic and block-based (Store API) checkout, and the invisible bot traps are never applied to the checkout page.
How do I block signups with disposable email addresses?
Bots and bad actors frequently use temporary email services like mailinator. Hushfort rejects signups from these addresses using a disposable domain list that ships and updates with the plugin; during checkout the account is opened as pending instead of being rejected. The same list is used by Spam Shield for form submissions.
One person creates many accounts with Gmail dot and + tricks. Can that be stopped?
Gmail ignores dots and everything after a + in an address, so unlimited ‘different’ addresses can point to the same inbox, a common trick for coupon or trial abuse. Hushfort’s email uniqueness feature compares normalised addresses: someone with an account under [email protected] cannot open another with [email protected] or a googlemail.com variation.
Are registration forms built with Elementor add-ons protected too?
Signup forms from page builder add-ons often send data through their own AJAX request and bypass standard protections. Hushfort applies IP limits and the circuit breaker to registration forms of plugins it does not specifically know, and also adds its invisible bot traps to forms that send their own data payload, such as the Ultimate Addons for Elementor registration form. This is how it runs on the West Riders Custom signup form.
Hardening, scanning & load
Should I disable xmlrpc.php?
For most sites, disabling XML-RPC logins is the right call, because xmlrpc.php is a separate door that bypasses the hidden login URL and lets attackers try many passwords in one request via system.multicall. Disabling it completely, however, stops Jetpack and the official WordPress mobile app from connecting. Hushfort offers four options: block logins but keep pingbacks (recommended), disable fully, block only multicall, or leave it untouched.
My WordPress username is visible (?author=1, REST users). How do I hide it?
WordPress publishes login names in several places: /wp-json/wp/v2/users lists users to anyone not logged in, yoursite.com/?author=1 redirects to the author archive and reveals the username in the address bar, and the core sitemap and oEmbed include author data. Hushfort’s Surface Hardening module closes all of these; the REST list is closed only for logged-out requests, so the Gutenberg and Elementor editors are unaffected, and author archives can be kept if you want.
How can I test which weaknesses my site exposes to the outside?
A setting that looks closed in the admin is not necessarily closed from the outside; caching, server rules or another plugin can change the result. Hushfort’s Surface Scan sends real requests to your own site to measure XML-RPC login, multicall, the REST users list, author scanning, the sitemap author list and application passwords. Results appear as cards, and open points come with a ‘Fix’ link and a ‘What should I do?’ guide.
Should I disable application passwords?
Application passwords allow authentication via the REST API that bypasses 2FA; if you use no external apps, disabling them shrinks the attack surface. Some mobile apps and integrations, however, depend on them. In Hushfort this setting is off by default, meaning nothing changes unless you enable it to disable application passwords. Failed application password attempts always count towards the lockout counter.
How do I find WordPress plugins I don’t use?
An active plugin is not necessarily a used one; add-on packs such as Elementor extensions can load CSS and JS on every page even when no page uses them. Hushfort’s Declutter module compares installed plugins and themes with real usage in your content, lists the unused ones with evidence and shows what share of page code is wasted. On one site we measured, unused plugins made up 44% of the code on every page. Removal is two-step and reversible.
Bot traffic is slowing down my WordPress site. What can I do?
Bots hitting the search page, 404 addresses and forms run PHP and the database on every request, and caching does not absorb them. Hushfort’s Load Protection gives each IP a per-minute point budget, charges more for expensive requests and pauses anyone over budget with a 429 for a few minutes. The check runs before the theme and plugins load, cached pages cost nothing, and WooCommerce checkout is never blocked.
How do I block fake Googlebot traffic without affecting the real Google crawler?
Bad bots pretend to be Googlebot or Bingbot to avoid being blocked, so filters that trust the user agent do not work. Hushfort checks any request claiming to be a search crawler against the IP lists officially published by Google and Bing; anything not on the list is blocked, while real crawlers are exempt from the budget. The lists are refreshed daily, so your SEO is not affected.
Can Cloudflare’s ‘Under Attack’ mode be switched on automatically during an attack?
A plugin can only stop requests that reach PHP; a large flood should be cut off at Cloudflare before it reaches the server. When emergency mode is switched on in Hushfort’s Load Protection, the IP budget drops to a quarter and, optionally and only if you have entered a Cloudflare API token limited to editing zone settings, Cloudflare’s ‘Under Attack’ mode is enabled too. When the time runs out, emergency mode switches itself off and Cloudflare returns to its previous level.
Setup, lockout recovery & performance
I forgot my login URL and cannot get into my site. What should I do?
Forgetting a hidden login URL can happen to anyone who uses login hiding. With Hushfort, add define( 'GATEKEEPER_LOGIN_SLUG', 'new-path' ); to wp-config.php via your file manager or FTP and the login immediately opens at yoursite.com/new-path. If even that is not possible, deleting or renaming the gatekeeper folder under wp-content/plugins disables the plugin and wp-login.php comes back.
How do I avoid locking myself out?
Knowing the recovery path before you set things up turns a lockout into a minor hiccup. In Hushfort hiding does nothing while the slug is empty, the dashboard has an ‘if you lose access’ card showing your hidden address and emergency lines ready to copy, you can allowlist your own IP, and 2FA recovery codes can be downloaded and printed. Just bookmark the new address right after saving it.
What happens if I deactivate the plugin?
Some security plugins leave .htaccess rules or leftover settings behind even after deactivation. When Hushfort is deactivated, settings return to WordPress defaults: the hidden login is removed and wp-login.php opens again, attempt limits stop and existing lockouts are lifted. Event logs are only cleared when the plugin is deleted entirely.
Will Hushfort slow down my site?
Heavy security plugins can slow a site by scanning files or writing to the database on every page load. Hushfort is modular, and a disabled module does no work. Load Protection keeps its counters in APCu when available instead of writing to the database per request, Surface Scan results are cached for 10 minutes, and probe logging is throttled so the table does not bloat during an attack. Blocked requests are cut off before the theme and plugins load, which actually reduces server load.
What is monitor mode and why is it recommended?
Every site’s traffic is different; a store’s payment integration or monitoring service could be mistaken for a bot if rules are too strict. Hushfort’s Spam, Registration and Load modules have a ‘log only’ monitor mode: the module records what it would block without blocking anything. Reviewing the logs for a few days, adjusting limits and then switching to Protect keeps the risk of false positives to a minimum.
Can I use Hushfort alongside an existing security plugin?
Two plugins doing the same job, such as two login hiders or two attempt limiters, can block each other’s requests and cause lockouts. Since each Hushfort module is switched on separately, you can enable only the modules your other plugin does not cover. For the cleanest result we recommend turning off one of any overlapping features; Tati Creative can help you plan the switch.
Which WordPress and PHP versions does Hushfort support, and does it run on shared hosting?
Hushfort requires WordPress 6.2 and PHP 7.2 or later and has been tested with WordPress 7.1. It runs on shared hosting as well as on a VPS: West Riders Custom is on shared hosting, other sites on a LiteSpeed VPS. If APCu is available it is used for Load Protection counters, otherwise the database is used; no special server configuration is required.
هل تريد رؤيته في عملك؟
في مكالمة قصيرة نستمع إلى احتياجاتك ونعرض عليك نسخة حيّة؛ ونتولّى الإعداد والانتقال.