Description
Locktura Security helps you filter suspicious requests, secure logins, and spot risky file changes from one dashboard. Its local firewall, two-factor authentication, File Scanner, logs, and alerts are included in this free plugin. Enable only the protections your site needs; no account or license is required.
What you can do with Free
- Filter suspicious traffic – Use firewall rules, brute-force limits, country rules, and Monitor only mode before blocking.
- Protect accounts – Add authenticator-app or passkey 2FA, recovery codes, password policies, account locks, and a custom login URL.
- Find risky changes – Scan files and permissions, verify official checksums, monitor file integrity, and review HTTPS and software health.
- See and respond – Review local security and user logs, live traffic, email alerts, and File Scanner quarantine or restore.
- Harden daily operations – Configure anti-spam, access rules, updates, and email obfuscation.
Included modules
- Firewall
- Brute Force Defense
- Hardening
- Update Manager
- Access Control
- Geo Blocking
- Hide Login
- Anti-Spam Shield
- Usernames & 2FA
- Password Manager
- Email Alerts
- Security Logs
- Live Traffic
- User Log
- File Scanner
- File Permissions
- SSL Control
- Email Encoder
Separate Premium plugin
Locktura Premium is separately distributed outside WordPress.org and is not included in this package. Every Free feature above works without a license.
The separate Premium plugin adds:
- Pattern Recognition
- Behavior Analytics
- Admin Lockdown
- Virtual Patching
- Header Hardening
- API Guardian
- Neural Bot Suppressor
- Network Reputation Control
- Domain Security
- Cookie Security Center
- Malware Scanner & Cleanup
- Smart 404
- Extra Hardening Tools
- Monthly Reports
- Session Management
- Extra User Safety Tools
- Premium Signature Pack
Privacy
Locktura stores security data locally, including IP addresses, request and login details, usernames, events, alert settings, password-policy and 2FA settings, encrypted TOTP secrets, public passkey credential data, hashed recovery codes, enrollment state, scan history, and update history. Passkey private keys remain on the user’s authenticator and are never stored by Locktura. Optional geolocation and password-breach checks use the services below. Administrators control retention, recipients, lookups, and privacy settings.
Unique traffic estimates count each IP address once per calendar day, excluding recognized bots and blocked requests. This local counter stores a keyed hash of the IP address and date, without the raw IP address or a browser cookie. Identifiers change each day and follow the traffic aggregate retention period (up to 90 days). Shared IP addresses count together, and visits served without running WordPress may not be recorded. Daily unique counts are not a deduplicated total across multiple days.
External services
Locktura loads no scripts, styles, fonts, or images from third parties. It makes only the requests documented below when the related feature is enabled or used.
WordPress.org and extension update providers
Used for core, plugin, and theme update checks and downloads through WordPress.org and update endpoints declared by installed extensions. Requests occur during administrator-requested or scheduled checks and can contain the site URL, software versions, locale, and extension metadata. A manual Software Health scan and enabled Trusted Integrity Scanner also request official WordPress.org core and plugin checksums; the Software Health scan can additionally request plugin last-update metadata. These checksum requests contain the installed version, locale, and plugin slug. Scan results, local baselines, integrity findings, and update history are stored locally. Local file contents are never sent to WordPress.org by the integrity scanner.
Documentation: https://developer.wordpress.org/apis/handbook/wordpress-org/update-api/ and https://developer.wordpress.org/cli/commands/plugin/verify-checksums/
Policies: https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/ and https://wordpress.org/about/license/
Privacy: https://wordpress.org/about/privacy/
Have I Been Pwned Pwned Passwords
Used for optional breach checks through https://api.pwnedpasswords.com/range/{first5-sha1}. Only the first five characters of the password’s SHA-1 hash are sent, never the password or complete hash. Results can be cached locally, and stored status is discarded when the credential changes.
Documentation: https://haveibeenpwned.com/API/v3#PwnedPasswords
Terms: https://haveibeenpwned.com/TermsOfUse
Privacy: https://haveibeenpwned.com/Privacy
Geolocation providers
When enabled geolocation needs uncached data and no trusted country header exists, Locktura sends the public IP being looked up. Results can be cached locally for 24 hours. Providers are tried in this order:
- Country (
https://api.country.is/{ip}) – Primary provider. Service information and privacy: https://country.is/ | Source and self-hosting: https://github.com/lineofflight/country - IPWhois (
https://ipwho.is/{ip}) – First fallback. Documentation: https://ipwhois.io/documentation | Terms: https://ipwhois.io/terms | Privacy: https://ipwhois.io/privacy - ipapi.co (
https://ipapi.co/{ip}/json/) – Final fallback. Documentation: https://ipapi.co/api/ | Terms: https://ipapi.co/terms/ | Privacy: https://ipapi.co/privacy/
Performance and SEO tool verification
The optional Geo Blocking settings “Allow verified performance and SEO tools” and “Allow verified UptimeRobot monitoring” are independent and off by default. The first downloads the public GTmetrix locations page (https://gtmetrix.com/locations/) and Pingdom probe lists (https://my.pingdom.com/probes/ipv4 and /probes/ipv6). The second downloads UptimeRobot’s combined IPv4/IPv6 list (https://cdn.uptimerobot.com/api/IPv4andIPv6.txt). Only enabled services are contacted, on settings save or when an uncached verification is needed. Lists are cached locally for 12 hours; failed downloads are retried after five minutes and do not grant an exception. Requests send a fixed verification user agent, never visitor IPs, tested URLs, cookies or account credentials. Providers receive the server’s outgoing IP as part of the connection.
PageSpeed Insights requests are checked with reverse and forward DNS against Google-controlled google.com hosts. DNS lookups disclose the candidate IP/hostname to the server’s configured DNS resolver. General Google Cloud tenant hostnames are not trusted. Siteliner uses its four published server IPs, bundled locally. These exceptions only bypass country rules for GET and HEAD; other protections still apply. Independent hosting/CDN rules are not changed and may need separate provider-IP exceptions.
GTmetrix documentation: https://gtmetrix.com/locations/ | Terms: https://gtmetrix.com/terms-of-service.html | Privacy: https://gtmetrix.com/privacy-policy.html
Pingdom documentation: https://documentation.solarwinds.com/en/success_center/pingdom/content/topics/pingdom-probe-servers-ip-addresses.htm | Terms: https://www.solarwinds.com/legal | Privacy: https://www.solarwinds.com/legal/privacy
UptimeRobot documentation: https://uptimerobot.com/help/locations/ | Terms: https://uptimerobot.com/terms/ | Privacy: https://uptimerobot.com/privacy/
Google verification: https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests
Siteliner documentation: https://www.siteliner.com/faqs
Own-site HTTPS and TLS checks
SSL Control checks the configured home_url() or site_url(). An administrator-requested HEAD request or TLS handshake sends ordinary network metadata and a Locktura user-agent to the site’s own host. System Health also sends up to five small daily GET requests: one random missing path, /.env, /wp-config.php.bak, and the homepage use home_url(); debug.log uses content_url(). Requests stay within the configured home/site origins. An external content/CDN URL is not probed and produces an inconclusive check. These requests check public exposure and unexpected external redirects. Response bodies and possible secrets are never stored; only status information is retained. No third-party endpoint is selected by Locktura.
Site-configured email delivery
Enabled alerts and tests can contain the recipient, site URL, event type, timestamp, IP address, relevant context, and remediation links. WordPress uses the site’s configured mail transport; Locktura selects no provider.
Locktura website links
Links to https://locktura.com/ open only after an administrator clicks them; there are no background calls.
Terms: https://locktura.com/terms-and-conditions/
Privacy: https://locktura.com/privacy-policy/
Translations
Dutch translations are managed through translate.wordpress.org and delivered by WordPress when an approved package is available.
Bundled assets
Runtime assets are bundled locally. Flag Icons, QRCode for JavaScript, and lbuchs/WebAuthn use the MIT License; Inter and Bebas Neue use the SIL Open Font License 1.1. The modified Wikimedia Commons world map is public domain. Source and license details are included under assets/ and vendor/lbuchs/. Locktura artwork is GPLv2 or later.
Installation
- Upload the
lockturafolder to/wp-content/plugins/, or install it through the WordPress Plugins screen. - Activate Locktura Security and open the Locktura dashboard.
- Review the modules, enable the protections you need, and save changed settings.
FAQ
Is Locktura Security free to use?
Yes. Everything under Included modules works without a license or paid account and has no time or usage restrictions. Locktura Premium is a separate, optional plugin.
Which protections should I enable first?
Start with the dashboard and Firewall’s Monitor only mode, then review Security Logs before enabling blocking rules. Add login protection and two-factor authentication as needed. Test login, password recovery, forms, and checkout after changing settings. Save your custom login URL before enabling Hide Login, and keep a backup before changing files or server rules.
Can I test firewall rules before blocking visitors?
Yes. The firewall’s Monitor only mode records requests it would block without stopping them. Manual IP blocks and existing automatic bans still apply, and other protection modules remain independent. Review Security Logs before switching the firewall to blocking mode.
Can I use Locktura with WooCommerce?
The firewall includes WooCommerce Safe mode for checkout, Store API requests, WooCommerce AJAX, webhooks, and payment callbacks. High-confidence attack checks remain active. Test your own checkout and payment integrations after changing security settings; third-party extensions can behave differently.
How does Locktura work with page caching or a CDN?
The firewall offers Strict, Cache-compatible, and Early PHP Firewall modes. Early PHP Firewall can check PHP page-cache hits before WordPress; server and CDN responses that bypass PHP cannot receive those checks. The Firewall page offers a browser-based cache protection check without a Locktura external test service. After changing cache settings, clear existing caches and test both public pages and login or checkout flows. The browser check covers the tested page, not every URL or CDN rule.
Does a File Scanner warning mean my website is infected?
Not necessarily. Suspicious patterns, configuration risks, or files that differ from official checksums need review; legitimate customizations can also cause findings. Inspect the details and compare with a trusted source before repairing or quarantining a file. A clean scan is not a guarantee that a site is uncompromised.
Does Locktura replace website backups?
No. Scan history, quarantine, and recovery copies are not full website backups. Keep independent backups of both your database and files, and verify that you can restore them.
How do users set up two-factor authentication?
Users manage their authenticator app, optional passkeys or security keys, and recovery codes under Users > Profile. Administrators can require 2FA for selected roles and set an enrollment grace period. A passkey is not required to use authenticator-app 2FA.
What if I lose my authenticator device?
Use an unused recovery code to sign in, then configure your replacement authenticator. Save recovery codes somewhere safe before you need them. If you have no working second factor or recovery code, contact your site administrator for help resetting your 2FA enrollment.
Which password protections are included?
Password Manager includes password policies, optional password reuse prevention and history, configurable expiration, and Password Emergency Reset. History records password hashes when passwords change while the feature is enabled; it cannot recover earlier password history. Emergency Reset signs out other eligible users and requires password recovery.
Do I need a cloud account, and what data leaves my site?
No external account is required for the WordPress.org edition. Protection and log storage run locally. Features such as geolocation, optional password-breach checks, software updates, and official checksum checks make network requests when used. See External services for the exact data, providers, and policies before enabling those features.
What information is stored in the logs?
Depending on enabled modules, logs can include IP addresses, requests, login attempts, usernames, and security or account activity. Records are stored locally, with retention controls and an IP anonymization setting. Security Logs and User Log include integrity checks to help detect altered or missing records.
Can I give someone limited access to Locktura?
Yes. The Permissions tab lets administrators assign specific Locktura permissions to roles or individual users, such as viewing logs or running scans. Administrators retain full access. Changing these permissions requires fresh two-factor verification.
Where can I get help or report a problem?
Use the WordPress.org support forum. Include your WordPress, PHP, and Locktura versions, the affected module, and steps to reproduce the issue. Remove passwords, recovery codes, API keys, personal data, and sensitive log details before posting publicly.
Screenshots







Changelog
2.7.2
- Improved early firewall handling of dynamic requests and cached pages.
- Hardened direct access to early firewall files.
- Improved Unicode-escape scanning compatibility.
- Clarified Free protections, setup guidance, and screenshots on the plugin page.
2.7.1
- Updated firewall request handling.
- Refined admin layouts and styling.
- Improved HTTPS and certificate checks.
- Improved Geo Blocking verification and controls.
- Improved File Integrity Monitoring scheduling and scans.
2.7.0
- Added Password Emergency Reset.
- Added password reuse prevention and password history.
- Added configurable password expiration policies.
- Added manual login locks for user accounts.
- Fixed password policy handling and File Scanner checks.
- Improved code efficiency and input validation.
2.6.5
- Fixed CAPTCHA challenge refresh on cached pages.
2.6.4
- Fixed Firewall handling of WooCommerce payment return URLs.
- Preserved public author and comment names with Usernames protection enabled.
- Improved Access Control navigation for active IP bans.
- Fixed Brute Force ban duration and centralized ban management in Access Control.
