Atlant Security
Enterprise-grade WordPress security: WAF, brute force protection, malware scanner, 2FA, honeypots, AI crawler control, and post-breach recovery.
Safe pick
Yes — Atlant Security is a safe, well-maintained plugin to use in 2026. It runs on 400+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 86/100 on our health check.
- Actively developed — last update 2 weeks ago
- Tested with the latest WordPress (7.1)
- Responsive support — 100% of recent threads resolved
- Momentum — downloads up 164.6% vs the previous 30 days
- Small user base (400+ active installs)
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Atlant Security stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| Brute Force | #38 |
| firewall | #52 |
| malware scanner | #21 |
| security | #21 |
| two factor authentication | #26 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 5 from 6 reviews
About Atlant Security
From the official readme · v1.1.32Description
Atlant Security is a comprehensive WordPress security plugin that provides enterprise-grade protection through 17 integrated security modules organized in a 5-layer defense architecture.
5-Layer Defense Architecture
- Early-Request WAF – Firewall, rate limiter, and IP blocking inspect every request at
initpriority 0, early in WordPress’s load – before the page is queried or rendered and before other plugins process the request. - Application-Aware – Login security, custom login URL, two-factor authentication, session hardening, cron monitoring, and REST API policies.
- Content & Config – WordPress hardening, security headers, AI crawler management, and honeypot traps.
- Outbound & Data – SSRF prevention, malware scanning (files and database).
- Response & Recovery – Post-breach recovery, notifications, visitor log, and audit log.
Key Features
Web Application Firewall (WAF)
Inspects every request against 28+ attack pattern families including SQL injection, XSS, remote code execution, path traversal, PHP object injection, and WordPress-specific attacks. Block or log-only mode. Triple URL decoding prevents evasion.
Brute Force Protection
Progressive lockout system (5 min > 30 min > 24 hours) with configurable thresholds. Generic login error messages prevent username enumeration. Author ID scans are blocked, and author archive URLs can be rebuilt from display names so they no longer publish valid login names.
Malware Scanner
Local file and database scanner with 38 malware signatures. Detects backdoors, webshells (WSO, c99, r57), crypto miners, credit card skimmers, and obfuscated code. Quarantine system with web access blocking.
Two-Factor Authentication (2FA)
TOTP (Google Authenticator, Authy) and email OTP. Per-role enforcement, 10 recovery codes, 5-minute challenge timeout, replay attack prevention.
Honeypot Traps
Zero-false-positive bot detection: hidden link traps, fake login pages, comment honeypots, and Contact Form 7 integration. 3-layer safe bot protection ensures Googlebot, Bingbot, and allowed AI crawlers are never blocked.
AI Crawler Management
Control 20+ known AI/LLM training crawlers (GPTBot, ClaudeBot, Google-Extended, Bytespider, and more). Per-crawler toggles, robots.txt integration, and 403 enforcement. Block training crawlers while allowing browsing bots.
Security Headers
Manage HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, CSP, CORP, and COOP. Letter-grade scoring system. Remove X-Powered-By and Server headers.
Session Security
Cookie hardening (HttpOnly, Secure, SameSite). Session binding via IP + User-Agent fingerprint detects hijacking. Concurrent session limits. Idle timeout. Optional admin bypass for all session restrictions.
Rate Limiter
Sliding-window rate limiting across 11 endpoint categories: frontend, login, search, feed, REST API, WooCommerce checkout, XML-RPC, and cron.
REST API Policies
Per-route access control with authentication requirements, HTTP method restrictions, rate limits, and IP whitelists. 5 built-in policies protect user enumeration, search, and write endpoints.
Cron Guard
Monitors wp-cron.php for flood attacks. Detects suspicious scheduled tasks via baseline comparison. System cron migration helper.
Outbound Monitor (SSRF Prevention)
Monitors all outgoing HTTP requests. Blocks requests to private/internal IP ranges including cloud metadata endpoints. Domain allowlist with wildcard support. Caller detection traces requests to specific plugins.
Post-Breach Recovery
12 emergency actions: terminate sessions, force password reset, rotate secret keys, emergency lockdown, reinstall core, reinstall plugins, audit admin accounts, clear caches, malware scan, disable plugins, and downloadable incident report.
Real-Time Dashboard
Live visitor monitoring with 15-second auto-refresh. Stat cards, traffic charts, top IPs with VirusTotal integration, browser distribution, and IP detail modals.
Visitor Log & Audit Log
Complete request history with filters (IP, URL, bots, blocked, time range). Admin action audit trail (who did what, when, from which IP).
Notifications
Email alerts (HTML formatted, color-coded severity), Slack webhooks, custom JSON webhooks, and daily digest. Configurable severity threshold with 5-minute deduplication.
WordPress Hardening
One-click toggles: disable XML-RPC, hide WordPress version, block REST API user enumeration, block author ID scans, hide usernames in author URLs, disable file editor, block PHP execution in uploads.
What Makes Atlant Security Different
- Early-Request WAF – Inspects and blocks malicious requests at
initpriority 0, before the page renders and before other plugins handle the request - Outbound HTTP Monitor – Detects SSRF attacks and unauthorized outbound connections
- Database Backdoor Scanner – Scans wp_options and wp_posts for eval(), base64, and hidden backdoors
- Client-Side Bot Detection – JavaScript challenges and browser fingerprinting catch sophisticated bots
- AI/LLM Crawler Blocking – Identify and block AI training crawlers scraping your content
- Honeypot Traps – Hidden links, fake login pages, invisible form fields that only bots trigger
- Cron Guard – Monitors wp-cron for unauthorized scheduled tasks planted by malware
- Post-Breach Recovery – Guided recovery toolkit with 12 emergency actions in one place
- Session Fingerprint Binding – Binds sessions to IP + User-Agent so stolen cookies are useless
- Real-Time Visitor Dashboard – Live visitor feed updated every 15 seconds
- Smart Password Policy – Minimum length, complexity, common-password blocking, and passphrase support
- Granular REST API Policies – Per-endpoint control, not just a global on/off switch
- Safe Mode Override – One constant in wp-config.php disables all blocking features instantly
- Deactivation Data Control – Choose to keep or wipe all security data when deactivating
- Zero phone-home – No telemetry, no tracking, fully GDPR-compliant (external services used only when explicitly enabled by the admin – see External Services section)
Why Atlant Security?
- All-in-one – Replaces 5-6 separate security plugins
- No external dependencies – Core security features run locally on your server
- Zero phone-home – No telemetry, no tracking (optional features like GeoIP use external services only when explicitly enabled – see External Services section)
- GDPR-friendly – No external fonts, no CDN resources
- Setup wizard – Configure core security in under 2 minutes
- Clean uninstall – Removes all database tables and options when deleted (opt-in)
- Safe Mode – Emergency override if you get locked out of your site
External Services
This plugin connects to the following third-party services under specific conditions:
Cloudflare IP Ranges
When Cloudflare integration is enabled, the plugin periodically fetches the current list of Cloudflare edge IP ranges from Cloudflare’s official endpoints. This is used to correctly identify visitor IP addresses behind the Cloudflare proxy and to whitelist Cloudflare edge servers.
- Data sent: No user data is sent. The plugin fetches publicly available IP range lists.
- When: Once per week via a scheduled cron job (aswp_refresh_cloudflare_ips), only when Cloudflare integration is enabled.
- Endpoints: https://www.cloudflare.com/ips-v4 and https://www.cloudflare.com/ips-v6
- Cloudflare Terms of Use
- Cloudflare Privacy Policy
MaxMind GeoLite2 GeoIP Database
When GeoIP country detection is enabled and a MaxMind license key is configured, the plugin downloads the GeoLite2-Country database from MaxMind. This database is stored locally and used to resolve visitor IP addresses to country codes for display in the visitor log and dashboard.
- Data sent: Your MaxMind license key is sent to authenticate the download request. No visitor data is sent to MaxMind.
- When: On initial setup and once per week via a scheduled cron job (aswp_update_geoip_db), only when GeoIP is enabled and a license key is configured.
- Endpoint: https://download.maxmind.com/app/geoip_download
- MaxMind End User License Agreement
- MaxMind Privacy Policy
Google IP Ranges
When Google integration is enabled in the IP Whitelist, the plugin periodically fetches the current list of Google IP ranges from Google’s official endpoint. This is used to automatically whitelist known Google infrastructure IPs (Googlebot, Google Cloud, etc.) so legitimate Google traffic is never blocked.
- Data sent: No user data is sent. The plugin fetches a publicly available JSON file containing Google IP ranges.
- When: Once per week via a scheduled cron job (aswp_refresh_google_ips), only when Google integration is enabled.
- Endpoint: https://www.gstatic.com/ipranges/goog.json
- Google Terms of Service
- Google Privacy Policy
Microsoft / Bing IP Ranges
When Microsoft integration is enabled in the IP Whitelist, the plugin periodically fetches the current list of Bing bot IP ranges from Microsoft’s official endpoint. This is used to automatically whitelist known Bing crawler IPs so legitimate Bing traffic is never blocked.
- Data sent: No user data is sent. The plugin fetches a publicly available JSON file containing Bing bot IP ranges.
- When: Once per week via a scheduled cron job (aswp_refresh_microsoft_ips), only when Microsoft integration is enabled.
- Endpoint: https://www.bing.com/toolbox/bingbot.json
- Microsoft Services Agreement
- Microsoft Privacy Statement
WordPress.org Core Checksums API
The Malware Scanner verifies the integrity of WordPress core files by comparing their MD5 hashes against the official checksums published by WordPress.org. Files that match are skipped during pattern scanning (vendor-verified, safe by definition). Files that mismatch are flagged as critical “core_modified” findings.
- Data sent: WordPress version number and locale. No site data, no visitor data, no PII.
- When: Once per WordPress version (cached for 24 hours), only when the Malware Scanner runs and the “Use core checksums” setting is enabled.
- Endpoint: https://api.wordpress.org/core/checksums/1.0/
- WordPress.org Terms of Service
- WordPress.org Privacy Policy
WordPress.org Secret Key API
The Post-Breach Recovery module can generate new WordPress secret keys and salts using the official WordPress.org API. This is used when an administrator manually triggers the “Rotate Secret Keys” emergency action after a security breach.
- Data sent: No user data is sent. The plugin fetches randomly generated keys from the API.
- When: Only when an administrator manually triggers the “Rotate Secret Keys” action in the Post-Breach Recovery module.
- Endpoint: https://api.wordpress.org/secret-key/1.1/salt/
- WordPress.org Terms of Service
- WordPress.org Privacy Policy
Slack Webhooks
When Slack notifications are enabled and a Slack webhook URL is configured, the plugin sends security alert messages to the specified Slack channel. This allows administrators to receive real-time security notifications in Slack.
- Data sent: Security alert messages containing the alert subject, description, severity level, site URL, and the IP address that triggered the alert. No visitor personal data or cookies are sent.
- When: Only when a security event occurs (e.g., brute force attempt, WAF block, honeypot trip) and Slack notifications are enabled.
- Endpoint: Administrator-configured Slack Incoming Webhook URL (e.g., https://hooks.slack.com/services/…)
- Slack Terms of Service
- Slack Privacy Policy
Custom Webhooks
When webhook notifications are enabled and a webhook URL is configured, the plugin sends security alert payloads in JSON format to the specified endpoint. This allows integration with any external monitoring or alerting system.
- Data sent: JSON payload containing the alert subject, description, severity level, site URL, timestamp, and the IP address that triggered the alert. No visitor personal data or cookies are sent.
- When: Only when a security event occurs and webhook notifications are enabled.
- Endpoint: Administrator-configured webhook URL.
- Terms and privacy: Determined by the third-party service the administrator configures.
Google reCAPTCHA
When CAPTCHA bot protection is enabled and the provider is set to “Google reCAPTCHA v2” or “Google reCAPTCHA v3”, visitor browsers load Google’s reCAPTCHA library and the server verifies submitted tokens with Google. This is OPT-IN – disabled by default.
- Data sent (browser → Google): visitor IP address and standard reCAPTCHA telemetry that Google uses to score human-vs-bot likelihood. Google’s reCAPTCHA library is loaded from www.google.com/recaptcha/api.js.
- Data sent (server → Google): the verification token returned by the visitor’s browser, the configured secret key, and the visitor’s IP address (
remoteipfield), to https://www.google.com/recaptcha/api/siteverify. - When: only when the configured provider is reCAPTCHA AND the visitor reaches /wp-login.php, the WordPress registration form, or the lost-password form (per-form toggle).
- Endpoints: https://www.google.com/recaptcha/api.js and https://www.google.com/recaptcha/api/siteverify
- Google reCAPTCHA Terms of Service
- Google Privacy Policy
Cloudflare Turnstile
When CAPTCHA bot protection is enabled and the provider is set to “Cloudflare Turnstile”, visitor browsers load Cloudflare’s Turnstile library and the server verifies submitted tokens with Cloudflare. This is OPT-IN – disabled by default. Turnstile is the privacy-respecting alternative to reCAPTCHA – Cloudflare states it does NOT track users across sites.
- Data sent (browser → Cloudflare): visitor IP address and standard Turnstile telemetry. The Turnstile library is loaded from challenges.cloudflare.com/turnstile/v0/api.js.
- Data sent (server → Cloudflare): the verification token returned by the visitor’s browser, the configured secret key, and the visitor’s IP address (
remoteipfield), to https://challenges.cloudflare.com/turnstile/v0/siteverify. - When: only when the configured provider is Cloudflare Turnstile AND the visitor reaches /wp-login.php, the WordPress registration form, or the lost-password form (per-form toggle).
- Endpoints: https://challenges.cloudflare.com/turnstile/v0/api.js and https://challenges.cloudflare.com/turnstile/v0/siteverify
- Cloudflare Terms of Service
- Cloudflare Privacy Policy
Upgrade Notices
1.1.8
Restores the policy: legitimate vendor bots (Google, Anthropic, OpenAI, Bing) are NEVER blocked unless the site operator explicitly opts in. Two fixes – AI crawler defaults flipped to “allow”, and the Honeypot reverse-DNS check now fails open so transient DNS issues can’t ban real Googlebots. Recommended for everyone running an SEO-sensitive site.
1.1.7
Critical security release. Fixes 14 CRITICAL and 12 HIGH issues found during a full external audit, including a fatal-at-login bug, IP-block bypass via IPv6-mapped addresses, an SSRF DNS-rebinding race in the outbound monitor, and a wp-config-backup-leaks-old-keys flaw. Recommended upgrade for every install.
1.1.6
Big scanner-accuracy improvement. Verified WordPress core files are now skipped (MD5-matched against the official api.wordpress.org checksums), tightened iframe/base64 signatures, fixed an over-broad path match, and added a “Mark as False Positive” button. Recommended upgrade for everyone running scans.
1.1.5
Adds CAPTCHA support on login / registration / lost-password forms. Three providers: reCAPTCHA v2, reCAPTCHA v3, and Cloudflare Turnstile. Configure in Login Security → Bot Protection (CAPTCHA).
1.1.4
Adds CSV export on the Malware Scanner (per Reddit community suggestion) – download full untruncated File + Database Findings before committing to Quarantine. Compatibility declared through WP 7.0.
1.1.3
Security hardening release. Fixes custom-login-URL cookie bypass, 2FA enforcement, SSRF log-only default, session-limit token/verifier mix, and adds real wp-config.php rewriting for key rotation. Existing 2FA recovery codes generated before 1.1.3 may not verify – regenerate them from your user profile after upgrading.
1.1.2
New About page consolidates defense architecture and competitive features. Setup wizard no longer auto-redirects on activation. Dashboard is cleaner with focus on operational data.
1.0.7
Major UI overhaul: inner sidebar navigation replaces 23 WordPress submenu items with a clean, persistent sidebar panel. All page URLs remain the same – bookmarks still work.
1.0.4
Adds GeoIP country flags in visitor log, custom login URL, password policy enforcement, and Force SSL Admin setting. Internal prefix migration runs automatically – no action required.
1.0.3
Adds honeypot traps, security headers management, two-factor authentication, and notification channels. Fixes IP management and status code logging. Recommended update.
1.0.0
Initial release. Run the Setup Wizard after activation to configure your site’s security.
Installation
- Upload the
atlant-securityfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to Atlant Security in the admin sidebar to access the dashboard.
- Optionally run the Setup Wizard from the sidebar to configure core security settings quickly.
The Setup Wizard configures your WAF, login protection, hardening, visitor logging, and notifications. You can run it at any time from the inner sidebar navigation.
Minimum Requirements
- WordPress 6.0 or higher
- PHP 8.0 or higher
Safe Mode
If you ever get locked out of your site, add this line to wp-config.php:
define( 'ASWP_SAFE_MODE', true );
This disables all blocking features (custom login URL, IP blocking, WAF, rate limiting) while keeping the admin interface accessible so you can fix settings.
Frequently asked questions
I locked myself out with the Custom Login URL
Add define( 'ASWP_SAFE_MODE', true ); to your wp-config.php. This disables all blocking features while keeping the admin accessible. Alternatively, rename the plugin folder via FTP to atlant-security-disabled, log in normally, rename it back, then whitelist your IP.
The WAF is blocking my page builder (Elementor, Divi)
Switch WAF to Log Only mode, reproduce the issue, then check the Audit Log for the triggered rule. Page builders may trigger false positives due to base64-encoded content in their save payloads.
Users keep getting logged out unexpectedly
This is caused by Session Binding with IP binding enabled. Go to Session Security and disable “Bind to IP” while keeping “Bind to User-Agent” enabled. Mobile and VPN users frequently change IPs. You can also enable “Exempt Administrators” to bypass all session restrictions for admin users.
Will this slow down my site?
No. The WAF runs at init priority 0 with optimized pattern matching. Rate limiting uses APCu when available for microsecond lookups. The visitor log is a single lightweight INSERT per request.
Email notifications are not arriving
WordPress default wp_mail() uses PHP mail() which many hosts block. Install an SMTP plugin like WP Mail SMTP or FluentSMTP to route emails through a proper mail provider.
The malware scan is running slowly
Reduce “Files per Batch” to 20-30 on shared hosting. The scanner processes files in AJAX batches to avoid timeouts. Files larger than 5 MB are automatically skipped.
How does the honeypot protect legitimate crawlers?
Three layers of protection: (1) Trap URLs are added as Disallow rules in robots.txt, (2) hidden links use rel=”nofollow”, and (3) 35+ known-good bot user agents (Googlebot, Bingbot, etc.) are pattern-matched and receive a 404 instead of a ban. AI crawlers marked “allowed” in your settings are also protected.
Does this plugin work with multisite?
The plugin is designed for single-site WordPress installations. Multisite support is planned for a future release.
What happens to my data when I deactivate the plugin?
Nothing is deleted on deactivation. When you delete the plugin, a dialog asks whether to keep or remove all data. You can also control this in Settings > “Delete data on uninstall”.
Changelog
1.1.32 – Author URL Repair: Rebuild, Rollback, and a Fix for Broken Slugs
Fixes a bug in the “Hide Usernames in Author URLs” feature added in 1.1.31, and adds the repair and rollback controls it should have shipped with. Thanks to Francesco for the detailed report.
* Fixed (important): the feature could write an empty or meaningless author slug when a display name used a non-Latin script – Cyrillic, Greek, Chinese, Japanese, Arabic, Hebrew or emoji. WordPress percent-encodes those names when building a slug, then strips the encoded characters again when saving the user, so an empty value reached the database and WordPress handed out “-2”, “-3” to each following account. Latin display names, accented ones included, were never affected.
* Fixed: non-Latin display names are now transliterated to Latin first. Where the server cannot transliterate (the PHP intl extension is missing), the plugin refuses to change the slug and says so on the Hardening page, rather than writing something meaningless.
* Fixed: the feature could not repair its own damage, because it only ever acted on slugs that still matched the username. It now recognises and rebuilds unusable slugs.
* New: every slug change is verified after writing. If WordPress stored something other than what was requested (which happens when another plugin filters user_nicename), the original is put straight back and the reason is recorded in the Audit Log.
* New: “Rebuild author URLs from display names” and “Restore original author URLs” buttons on the Hardening page. The slug each user had beforehand is recorded, so the change is fully reversible.
* New: previous author URLs are redirected to the new ones, so existing links, bookmarks and search results do not break. This stays active even after the feature is switched off.
* New: enabling the setting now warns first that public URLs will change and that it can be undone.
1.1.31 – Author Enumeration: The Block Now Actually Runs
- Fixed (important): “Block Author Enumeration” did nothing on almost every site. WordPress core registers its own canonical-redirect handler on the same hook at the same priority, and because core loads before any plugin it always ran first – sending /?author=1 on to the author archive, spelling out the username, before our block was reached. It only ever worked for authors with no published posts. The block now runs ahead of core, and is renamed “Block Author ID Scans” to match its scope.
- Changed: the ?author=N bounce is a temporary (302) redirect now. A permanent one is cached by browsers and CDNs, so turning the setting off later used to leave visitors stuck on a cached redirect.
- Fixed: on plain permalinks the author archive IS ?author=N, so the block would have removed author archives altogether. It now stands down on those sites.
- New: “Hide Usernames in Author URLs” (Hardening). Author archives stay where they are, but their URL is rebuilt from each user’s display name instead of the login name. The users sitemap, oEmbed and feeds read the same fields, so this closes those routes at the same time. Each author needs a display name that differs from their username; the Hardening page lists any that do not. Off by default.
- Corrected the wording across Hardening, Settings, the Setup Wizard, the vulnerability audit and the About page. The old copy promised username enumeration was “blocked” while only covering the ?author=N probe.
1.1.30 – Hardened Against Fatal Errors From Unexpected Hook Arguments
- Fixed: a fatal error could be triggered inside Atlant when WordPress or another plugin called one of the hooks we listen to with an argument type we did not expect. Two cases were guaranteed: on multisite, network_site_url() passes a null scheme to its filter, which fataled whenever the Custom Login URL was enabled; and any theme or plugin calling site_url( null ) fataled on every page. Reported on WordPress 7.1 / PHP 8.3 as a dashboard crash.
- Every hook callback in the plugin now validates what it receives and passes anything unexpected through untouched instead of crashing.
- Fixed: 1.1.29 was published with the plugin header still reading 1.1.28, so WordPress kept offering that update to sites which already had it.
1.1.29 – Full Audit Release
A top-to-bottom review of every module. All migrations run on their own on the next page load after updating; nothing needs doing.
* Fixed (security): the Post-Breach “Emergency Database Scan” results table rendered matched content without escaping, so a site that had been injected with a malicious script could have that script run in the administrator’s browser the moment they ran the scan.
* Fixed (security): after a plugin update, the first visitor to the site had their IP removed from the block list – the “unblock the activating admin” safety net ran on every internal upgrade, not just a real activation. A blocked attacker could unblock themselves by being first to load the site after an auto-update.
* Fixed: ASWP_SAFE_MODE now really pauses every blocking feature. It previously skipped the WAF, brute-force login lockouts, REST API policies and honeypot bans, so an admin who followed the documented recovery stayed locked out. A shared office IP in a 24-hour lockout no longer locks the administrator out either.
* Fixed (2FA): “Disable 2FA” silently did nothing; an administrator can now reset another user’s 2FA; email-code delivery failures are surfaced instead of silently waiting; TOTP secrets are encrypted at rest.
* Fixed: dead buttons across the admin – REST API Add and Edit Policy, Outbound Monitor “Save Allowlist”, Malware Scanner scan settings, the whitelist remove button and “+ Block IP” – and saving the CAPTCHA panel no longer wipes the stored secret key. Re-running the Setup Wizard no longer resets customised settings.
* Fixed: false positives that blocked legitimate traffic – WooCommerce checkout rate limiting, editors saving posts that contain code samples, routine browser updates logging users out, CAPTCHA breaking every login form that is not wp-login.php, and the outbound monitor killing WP-Cron on hosts that resolve the site internally.
* New: scheduled background malware scans. Quarantine now warns before touching WordPress core, the active theme or an active plugin, and has a one-click Restore.
* Fixed: multisite network activation, deactivation and uninstall now cover every subsite.
* Performance: removed a legacy check that ran 7 database queries on every request, autoloaded around 80 small settings, batched log-retention deletes, and cached dashboard statistics.
1.1.28 – GeoIP “Download Database” Button No Longer Stuck Disabled
- Fixed: the “Download Database” button stayed greyed out even after entering a MaxMind license key, because it only came alive after clicking a separate “Save GeoIP Settings” button that the on-screen instructions never mentioned. It now activates the instant a key is typed or pasted, and clicking it saves the key and downloads the database in one step.
1.1.27 – Daily Digest Turns Itself Off on Upgrade
- Fixed: sites receiving the unwanted morning “daily digest” email now stop automatically on update – no wp-config edit, no visiting each subsite. The digest cron is only scheduled while the digest is enabled, so a disabled digest can never fire. Re-enable it in Notifications with one toggle if you want it.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Atlant Security alternatives
All Brute Force plugins →
FAQ
Atlant Security: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 1, 2026
Is Atlant Security free?
Yes. Atlant Security is free to download and use from the official WordPress.org plugin directory.
Is Atlant Security safe to use in 2026?
Yes — Atlant Security is a safe, well-maintained plugin to use in 2026. It runs on 400+ sites, is rated 5/5 and was last updated 2 weeks ago, and scores 86/100 on our health check.
How many websites use Atlant Security?
Atlant Security is active on 400+ WordPress websites and has been downloaded 5,796 times since it launched in March 2026. It was downloaded 2,334 times in the last 30 days.
Does Atlant Security work with WordPress 7.1?
Yes. The developer has tested Atlant Security up to WordPress 7.1.2, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Atlant Security need?
Atlant Security requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Atlant Security last updated?
The latest version, 1.1.32, was released on September 19, 2026 (2 weeks ago).
Who makes Atlant Security?
Atlant Security is developed and maintained by Alex.
What are the best alternatives to Atlant Security?
The most popular alternatives to Atlant Security are Limit Login Attempts Securi… (1M+ installs), CloudSecure WP Security (100K+ installs) and Anti-Malware Security and B… (100K+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
