Admin Safety Guard — Login Security, Limit Logins, 2FA & Brute Force Protection icon
Maintained Tested up to 7.0.8 #8 in brute force protection

Admin Safety Guard — Login Security, Limit Logins, 2FA & Brute Force Protection

Stop brute force attacks for free. Limit login attempts, add 2FA and reCAPTCHA, hide wp-login.php, block IPs and see every login on your site.

Active installs20+10+ tier
Downloads · 30d150▲ +11.1% vs prev. 30d
Rating5/54 reviews
Health score59/100Fair
All-time downloads3.1KSince Aug 2025
Support resolved—No recent threads
RequiresWP 5.8PHP 8.0+
Downloads · 7d33▼ -10.8% week over week
Our verdict

Use with caution

Admin Safety Guard works, but test it on a staging site before relying on it in 2026. It runs on 20+ sites, is rated 5/5 and was last updated 3 months ago, and scores 59/100 on our health check.

  • Small user base (20+ active installs)
  • Very few reviews so far

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

51015Aug 18Oct 1Nov 15
Yesterday3
Daily average (1y)7
Peak day49Apr 7, 2026
Last 12 months2.7K

Download spikes usually follow a new release — each site that auto-updates counts as a download.

Rankings

Where Admin Safety Guard stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
brute force protection #33 539 Best brute force protection plugins →
custom login url >100 3,467 Best custom login url plugins →
limit login attempts #75 872 Best limit login attempts plugins →
login security >100 4,878 Best login security plugins →
two factor authentication >100 524 Best two factor authentication plugins →

Version adoption

Share of active sites per release.

  • 1.4100.0%

Rating breakdown

★★★★★★★★★★ 5 from 4 reviews

  • 5★100.0%
  • 4★0.00%
  • 3★0.00%
  • 2★0.00%
  • 1★0.00%

About Admin Safety Guard

From the official readme · v1.4.1

Description

Admin Safety Guard locks down the two places WordPress sites actually get broken into: the login form and the admin area.

You don’t need to know what a firewall rule is to use it. Turn on a switch, pick a number, save. The plugin handles the rest and shows you, in plain words, what it blocked and what still needs your attention.

If you have ever looked at your login log and seen hundreds of failed attempts for a user called “admin” that you never created, this plugin is for you.

How WordPress sites get broken into

Almost every automated attack follows the same three steps:

  1. A bot loads yoursite.com/wp-login.php, because that address is the same on every WordPress site in the world.
  2. It guesses usernames and passwords, thousands of times an hour, until one works.
  3. Once it’s in, it installs a backdoor, injects spam links, or quietly adds itself as an administrator.

Admin Safety Guard breaks that chain at every step, and every feature below is free.

Free features

Limit login attempts (on by default)
Lock out an IP address after a set number of failed sign-ins. You choose how many attempts are allowed, how long the lockout lasts, and what the person sees. Keep failing and the address is blocked for a full 24 hours. This is the one feature that switches itself on when you activate the plugin, so your site is covered before you configure anything.

It doesn’t only watch wp-login.php. XML-RPC, application passwords and custom theme login forms all count towards the same limit, which is how most bots get around simpler login limiters.

Add your own IP to the trusted list so you can never lock yourself out. Single addresses, CIDR ranges (203.0.113.0/24), wildcards (203.0.113.*) and IPv6 all work.

Custom login URL
Move your sign-in page to an address only you know, like yoursite.com/office-door. After that, wp-login.php and wp-register.php return a 404 for everyone, so scanners find nothing to attack. It works on root installs, WordPress in a subfolder, and multisite. Reserved slugs that would break your site are rejected before you can save them.

Two-factor authentication by email
After the password comes a one-time code, sent to the user’s inbox. A stolen password on its own becomes useless. You decide which roles need it (administrators and editors only, for example), how many digits the code has, how long it stays valid, and how many wrong guesses are allowed before it’s destroyed. The email is styled by default, and you can write your own subject and body if you’d rather.

Google reCAPTCHA (v2 and v3)
Add reCAPTCHA to your login form to stop bots before they ever submit a password. Both the “I’m not a robot” checkbox and the invisible v3 score check are supported. Paste in your site key and secret key, pick a version, done.

Session security
Everything above protects the sign-in. This protects what happens after it. WordPress keeps a session alive for two days, or fourteen if someone ticked “Remember Me” – however long the laptop sits open in a coffee shop.

Sign people out after a period of inactivity, shorten the maximum session length, end every other session when someone changes their password, and optionally tie a session to the IP address it started from so a copied cookie stops working elsewhere.

IP blocking
Some addresses don’t deserve a second chance. Add them to the permanent block list and they never reach your login page again. You can also block an address in one click straight from the login log.

Login logs and activity tracking
A real audit trail: every successful sign-in and every failed attempt, with username, IP address, browser, and timestamp. Search it, sort it, page through it, export it to CSV for a client report, or clear out old entries by date range.

You can also get an email the first time an administrator signs in from an address that account has never used before. That’s often the earliest sign that a password has leaked.

Threats blocked
Every block the plugin performs is recorded in one place: lockouts, blocked addresses, failed reCAPTCHA checks, wrong two-factor codes, blocked XML-RPC requests, username-discovery attempts. The dashboard shows what was stopped and when, so “is anything actually happening?” has a real answer.

Security score
The score grades your site, not the plugin. It checks the things that matter – HTTPS, whether core and PHP are current, whether an account is literally called “admin”, whether your usernames are public, whether file editing is still enabled – and weighs them against the protections you have switched on. Anything critical gets flagged at the top of your admin screen until it’s dealt with.

Privacy hardening
Nine one-click switches that close the small leaks attackers use for reconnaissance:

  • Disable XML-RPC
  • Block username discovery through ?author=1 and the REST users endpoint
  • Show one generic error instead of telling people which half of the login was wrong
  • Hide your WordPress version from page source, feeds and asset URLs
  • Remove the RSD, Windows Live Writer and shortlink meta tags
  • Disable pingbacks so your site can’t be used to flood someone else’s
  • Disable the theme and plugin file editors
  • Send browser security headers (clickjacking, MIME sniffing, referrer leaks, camera and microphone access)
  • Disable application passwords

Password protect the whole site
Put a password in front of everything. Handy for staging sites, client previews and coming-soon pages. Choose how long access lasts and which roles skip it.

Hide the admin bar by role
Decide which roles see the toolbar on the front end. Hide it from subscribers and customers, keep it for editors and administrators.

Brand your login page
Swap the WordPress logo for yours, set its size, where it links to, and its alt text. Change the page background (colour or image), the form background, text, link and button colours, round off the corners, hide the links you don’t want, tick “Remember Me” by default, or write your own CSS. Ready-made templates are included if you’d rather not fiddle.

Firewall and malware overview
One screen showing your firewall status, with a link to our free Deep Malware Cleaner plugin for scanning and cleanup. If it’s already installed, the screen takes you straight to it.

Pro features

Admin Safety Guard Pro adds the tools agencies and busier sites tend to ask for.

Passwordless login (magic links)
Users click a one-time link in their email instead of typing a password. The link works once and then expires.

2FA with an authenticator app
Google Authenticator, Authy and anything else that speaks TOTP. Users scan a QR code once and generate codes on their phone from then on – no email delivery to wait for.

Social login
Let people sign in with Google, Facebook or other accounts they already have, while you keep control of which providers are allowed.

Database prefix check
The default wp_ prefix is known to every attacker and makes SQL injection easier to write. This finds your current prefix and walks you through changing it safely.

Strong password enforcement
Set a minimum password strength. Weak passwords get rejected at the point they’re created, not after an incident.

Advanced web application firewall
Inspect incoming requests and block SQL injection and cross-site scripting payloads before WordPress ever sees them. Run it in monitor-only mode first, whitelist trusted addresses, block user agents, and cap request size.

Malware scanning and cleanup
Handled by our separate free plugin, Deep Malware Cleaner, rather than a second half-built scanner in here.

Upgrade to Pro to unlock all Pro features.

Who uses it

Bloggers and content creators – protection that runs in the background with nothing to maintain.

Small business owners – your site is your shopfront. A hack costs you customers and takes days to clean up.

WooCommerce stores – customer records, addresses and order history sit behind that login form. Lock it properly.

Freelancers and web designers – hand over a site that’s already hardened and branded, without a security bill attached.

Agencies – the same repeatable setup across every client site, with logs you can export when someone asks what happened.

Developers – every limit, message and redirect is configurable, and the features are built on standard hooks and filters you can extend.

What’s different about it

  • Light. Admin assets only load on the plugin’s own screens, and only the code for the screen you’re actually looking at. Nothing is added to your front end.
  • Useful straight away. Limit login attempts switches itself on at activation. You’re protected before you open the settings.
  • Honest about free vs Pro. Pro features are visible and clearly labelled. Nothing pretends to be free and then asks for a card.
  • Written to WordPress standards. Inputs sanitised, output escaped, nonces on every request, prepared statements on every query, and a real uninstall routine that removes its own data when you delete it.

Support

Free support is on the WordPress.org forum. For anything Pro-related or urgent, use our contact form.

External Services

This plugin uses the following third-party and external services:

1) Google reCAPTCHA (Google LLC)

Purpose:
Used to protect forms from spam and automated abuse.

When it is used:
– When reCAPTCHA is enabled in plugin settings
– On login forms and support forms protected by reCAPTCHA

What data is sent:
– User IP address
– reCAPTCHA response token generated by Google
– Browser information as required by Google reCAPTCHA

Service provider:
Google LLC

Terms of Service:
https://policies.google.com/terms

Privacy Policy:
https://policies.google.com/privacy

2) ThemePaste API (Plugin Author Service)

Purpose:
Used for:
– Collecting optional admin email addresses for plugin updates and notifications
– Sending support requests from the plugin support form
– Collecting optional feedback when a user attempts to deactivate the plugin
– Managing plugin-related notifications (only if the user provides contact details)

When it is used:
– When a user submits the built-in support form
– When a user opts to send diagnostic information
– Submitting the optional deactivation feedback form

What data is sent:
– Name
– Email address
– Phone number (if provided)
– Message content
– Site URL
– Plugin name
– Feedback text (if provided)
– Support message content
– Deactivation reason (if provided)

No data is sent without user action.

Service provider:
ThemePaste.com

Terms of Service:
https://themepaste.com/terms-condition

Privacy Policy:
https://themepaste.com/privacy-policy

Development / Source Code

This plugin ships compiled JavaScript bundles in:
– assets/admin/build/*.bundle.js

The original, human-readable source files are included in this plugin under:
– spa/admin/

They are also available at https://github.com/themepaste/admin-safety-guard

Build Tools
– Node.js (LTS recommended)
– npm
– Webpack + Babel

Source Entry Points
The admin SPA bundles are built from the following entry points:

  • spa/admin/login-template/Main.jsx -> assets/admin/build/loginTemplate.bundle.js
  • spa/admin/login-logs-activity/Main.jsx -> assets/admin/build/loginLogActivity.bundle.js
  • spa/admin/analytics/Main.jsx -> assets/admin/build/analytics.bundle.js
  • spa/admin/security-core/Main.jsx -> assets/admin/build/securityCore.bundle.js
  • spa/admin/firewall-malware/Main.jsx -> assets/admin/build/firewallMalware.bundle.js
  • spa/admin/privacy-hardening/Main.jsx -> assets/admin/build/privacyHardening.bundle.js
  • spa/admin/2fa-using-mobile-app/Main.jsx -> assets/admin/build/twoFAUsingMobileApp.bundle.js

React and the webpack runtime are extracted into shared chunks
(framework.bundle.js and runtime.bundle.js) so they are downloaded once
rather than being inlined into every bundle.

Install Dependencies
From the plugin root directory (where package.json lives):

1) Install dependencies:
npm install

Build (Production)
To generate the production bundles:

npm run build

Output Location
Webpack outputs the compiled bundles to:

  • assets/admin/build/[name].bundle.js

Important Notes
– Do not edit files in assets/admin/build/ directly. They are generated files.
– Edit the source files under spa/admin/ and re-run the build command.
– For WordPress.org distribution, production builds should be used (mode=production).

Links

Website
Documentation
Pro Version
Facebook
Pinterest
LinkedIn
Instagram

Installation

From your dashboard (easiest)

  1. Go to Plugins → Add New.
  2. Search for Admin Safety Guard.
  3. Click Install Now, then Activate.

Uploading the zip

  1. Download the plugin zip from WordPress.org.
  2. Go to Plugins → Add New → Upload Plugin.
  3. Pick the zip, click Install Now, then Activate Plugin.

Then what?

Limit login attempts turns itself on with sensible defaults (3 attempts, 15 minute lockout), so there’s nothing you have to do immediately. When you’re ready, open Admin Safety Guard in the menu, check your security score, and work down the list of suggestions.

If you plan to use a custom login URL, add your own IP to the trusted list first and bookmark the new address before you save.

Changelog

Important fix: addresses on the permanent block list could still sign in over XML-RPC, application passwords or a theme login form. Also stops the idle timeout signing out people working in the block editor. Recommended for everyone.

1.4.1 – Blocked IP Enforcement & Session Fixes

Fixes

  • [security] The permanent block list only applied to the login page. An address you had blocked by hand could still sign in over XML-RPC, with an application password, or through a theme’s own login form, as long as it had valid credentials. Blocked addresses are now refused on every authentication path, and the attempt is recorded in the threat log.
  • [fix] Idle timeout signed out people who were still working. Time spent in the block editor, the media library or the Customizer was not counted as activity, because those screens talk to the site in the background rather than loading a new page. Background activity now keeps the session alive, while automatic traffic – Heartbeat polling, autosaves, cron and application passwords – still does not, so an unattended screen is signed out as before.
  • [fix] The login screen said nothing after an automatic sign-out. It now explains whether the session ended through inactivity or an IP address change.
  • [fix] IPv6 entries on the trusted and blocked lists never matched when written with a wildcard (2001:db8:*). Matching is no longer dot-only, and is case-insensitive.
  • [fix] The security audit passed sites running PHP 8.1, which stopped receiving security fixes on 31 December 2025. The check now expects PHP 8.2 or newer.
  • [fix] Usernames could still be read from the WordPress sitemap at /wp-sitemap-users-1.xml while “block username discovery” was on. Authors are now left out of the sitemap too.
  • [fix] A security check added by other code through the tpsa_security_audit_checks filter could raise a PHP notice while the issue list was being sorted.

1.4.0 – Session Security, Threat Log & Site-Wide Security Audit

New

  • [feature] Session Security. A new feature covering what happens after sign-in: automatic sign-out after inactivity, shorter maximum session and “Remember Me” lengths, ending every other session when a password changes, and optionally tying a session to the IP address it started from.
  • [feature] Threats Blocked log. Every block the plugin performs – lockouts, blocked IPs, failed reCAPTCHA, wrong two-factor codes, blocked XML-RPC, username discovery attempts – is now recorded and shown on the dashboard, with 30 days of history.
  • [feature] Rewritten security score. The score now audits the site itself (HTTPS, WordPress and PHP versions, an account named “admin”, publicly listed usernames, file editing, and more) alongside your plugin coverage, each check weighted by real-world impact. Critical findings raise a dismissible admin notice.
  • [feature] Eight new privacy hardening switches: block username discovery via ?author=1 and the REST users endpoint, generic login errors, hide the WordPress version, remove RSD/Windows Live Writer/shortlink meta, disable pingbacks, disable the theme and plugin editors, send browser security headers, and disable application passwords.
  • [feature] Trusted IP list and permanent block list for Limit Login Attempts, accepting single addresses, CIDR ranges, wildcards and IPv6.
  • [feature] Limit Login Attempts now also covers XML-RPC, application passwords and custom theme login forms, can show remaining attempts to genuine users, and can email you on each lockout (throttled to one message per address per hour).
  • [feature] Two-factor email codes can now be limited to chosen roles, with configurable code length, validity window and attempts per code, plus a styled default email.
  • [feature] New admin location alerts. Optional email when an administrator signs in from an IP address that account has never used, limited to one alert per account and address per day.
  • [feature] CSV export and purge for the login logs, plus search, sorting, pagination, summary cards, and one-click block or unblock straight from the table.
  • [feature] Full login page branding: background colour and image, form background, text, link and button colours, rounded corners, hide the logo, lost password, register, back-to-site and language links, tick “Remember Me” by default, logo link and alt text, and custom CSS.
  • [feature] The Firewall & Malware screen now detects the free Deep Malware Cleaner plugin and links to install, activate or open it.
  • [feature] Deleting the plugin now removes everything it created – options, tables, transients and user meta – across every site of a network.
  • [feature] Multisite support for table creation, including sites added to the network after activation.

Improvements

  • [improve] Admin assets are code-split: React and the webpack runtime load once as shared chunks, and only the bundle for the screen you’re viewing is downloaded. The media library scripts now load on the branding screen only.
  • [improve] Indexes added to the login, failed login and threat tables, so lockout checks and cleanup stay fast on a site under sustained attack.
  • [improve] Daily cleanup with proper retention: 30 days for failed logins and threats, 90 days for successful logins, with cut-offs calculated in the site’s own timezone.
  • [improve] Every setting has been relabelled in plain English, with recommended values and a clear warning where a setting can lock people out.
  • [improve] Custom Login URL now rejects reserved slugs that would break the site, and returns a proper 404 on the old login and registration URLs.
  • [improve] reCAPTCHA v3 tokens are refreshed before submission, so a form left open no longer fails with an expired token.
  • [improve] The user count on the dashboard is cached for an hour instead of running an uncached query on every page load.

Fixes

  • [fix] 24-hour IP blocks never expired. The cleanup job was never registered, so an address that tripped the lockout threshold stayed blocked permanently. It now runs daily as intended.
  • [fix] The successful login log overwrote a single row per username, so it only ever showed the most recent sign-in. It now records one row per event, making it a genuine audit trail.
  • [fix] Corrected the License URI in the plugin header, which pointed at GPL-2.0 while the plugin is licensed GPLv3.
  • [fix] Replaced remaining json_encode() calls with wp_json_encode(), and removed unused development constants and dead Pro placeholder classes.
  • [fix] Resolved PHP notices from missing array keys on fresh installs.

1.3.0 – Security & Performance Update

  • [security] Two-Factor Authentication (Email OTP) now expires codes after 5 minutes and invalidates them after 5 failed attempts to prevent code reuse and brute-forcing.
  • [security] Removed legacy storage of OTP credentials in user meta; a one-time cleanup automatically scrubs any plaintext data left behind by older versions on upgrade.
  • [security] Added a clear “code expired, please log in again” notice on the login screen when an OTP session times out.
  • [security] Password Protection now uses a signed, site-secret-keyed access token with constant-time comparison instead of a plain password hash, so the access cookie cannot be forged or precomputed.
  • [improve] Reworked client IP detection with proxy and Cloudflare support, validation of forwarded headers, and IPv6 loopback normalization for more accurate logging and IP blocking.
  • [improve] Database schema changes now apply automatically on plugin update, not just on activation, so updates stay reliable across versions.
  • [improve] Cached table-existence checks to remove redundant database queries on every REST API request.
  • [improve] More accurate Security Score calculation that only counts features with a real on/off control.
  • [fix] Resolved minor PHP warnings and general stability improvements.

1.2.9 – Maintenance Update

  • [update] Refreshed the plugin short description in readme for better clarity on WordPress.org.
  • [improve] Minor readme content polish and consistency tweaks.
  • [maintenance] General housekeeping and version bump for ongoing compatibility.

1.2.8 – Bug Fixes & Default Feature Activation

  • [fix] Fixed PHP warnings on fresh install: “Undefined array key sub” and “Trying to access array offset on value of type null” in layout.php.
  • [fix] All features (free and pro) now correctly default to Inactive on fresh install, giving users full control over what is enabled.
  • [feature] Limit Login Attempts is now automatically enabled with sensible defaults on first install to provide immediate brute-force protection out of the box.
  • [improve] Feature status detection now correctly handles features without a master enable switch (Two-Factor Auth, Privacy Hardening) by checking their individual toggle fields.

1.2.7 – UI & Content Update

  • [improve] Updated plugin layout to be more user-friendly and easier to use.
  • [improve] Optimized code for better performance and smoother experience.
  • [update] Updated readme content for better clarity and documentation.
  • [update] Changed plugin banner and refreshed screenshots with a new layout.
  • [feature] Added visibility of all Pro features in free version (requires Pro plugin to use).
  • [fix] Minor UI improvements and general stability fixes.

Full changelog on WordPress.org →

Screenshots

The dashboard leads with anything critical, like a site still running without HTTPS, then threats blocked, active users and failed sign-ins over the last 24 hours.
The dashboard leads with anything critical, like a site still running without HTTPS, then…
Sign-in activity for the last 24 hours, next to a breakdown of how many of the plugin's features you actually have switched on.
Sign-in activity for the last 24 hours, next to a breakdown of how many of the plugin's…
Security Core puts every protection in one grid, each marked Free or Pro and Active or Inactive. Limit Login Attempts is already on the moment you activate the plugin.
Security Core puts every protection in one grid, each marked Free or Pro and Active or…
Further down the same grid: Password Protection, Session Security, reCAPTCHA and Hide Admin Bar are free, while Passwordless Login and app-based 2FA come with Pro. Your score stays in view in the sidebar.
Further down the same grid: Password Protection, Session Security, reCAPTCHA and Hide…
Pro features are visible in the free version too, so you can see exactly what you would get before spending anything.
Pro features are visible in the free version too, so you can see exactly what you would…
Firewall & Malware shows the Pro web application firewall alongside Deep Malware Cleaner, our separate free plugin for scanning and cleanup, clearly labelled as a separate download rather than a bundled upsell.
Firewall & Malware shows the Pro web application firewall alongside Deep Malware Cleaner…
Monitoring & Analytics: failed sign-ins, current lockouts, blocked addresses and successful sign-ins at a glance, plus an optional email alert when an administrator signs in from a new location.
Monitoring & Analytics: failed sign-ins, current lockouts, blocked addresses and…
Search any log, filter by date, page through it, export it to CSV, or delete old records when the tables get long.
Search any log, filter by date, page through it, export it to CSV, or delete old records…
Privacy & Hardening: switch off XML-RPC, block username discovery through ?author=1, hide which login detail was wrong, and remove your WordPress version. Each switch explains what it does and when to leave it alone.
Privacy & Hardening: switch off XML-RPC, block username discovery through ?author=1, hide…

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.

Active installs badge Rating badge Health score badge

Best Admin Safety Guard alternatives

All brute force protection plugins →
Alternatives
Rank Plugin Active installs Rating Updated Health
1 Kadence Security – Password, Two Factor Authentication, and Brute Force Protection Kadence Security Harden your site security with Login Security, Two-Factor Authentication (2FA)… by Nexcess 700K+ ★★★★★★★★★★ 4.6 (4K) 1 month ago 83
2 Titan Anti-spam & Security – Brute Force Protection, 2FA & Spam Filter Titan Anti-spam & Security Block spam comments, defend against login attacks, strengthen site security. Anti-spam… by Themeisle 50K+ ★★★★★★★★★★ 4.5 (370) 3 days ago 89
3 Quttera ThreatSign – Web Malware Scanner for WordPress Quttera ThreatSign – Web Malware Scanner for WordPress WordPress multi-level security scanner detecting malware, 0-day threats, brute-force… by quttera 10K+ ★★★★★★★★★★ 3.9 (47) 12 hours ago 89
4 Kaya Login Captcha Kaya Login Captcha Protects the WordPress login, registration and lost-password forms with a simple captcha… by Kaya Studio 400+ ★★★★★★★★★★ 5 (1) 2 months ago 73
5 Honeypot Toolkit Honeypot Toolkit Automatically insert Project Honeypot links into your pages and block IP addresses that are… by Jeff Sterup 400+ ★★★★★★★★★★ 4.3 (9) 9 months ago 40
6 WPHH SECURE – AIO WordPress Security With File Locking & WP Hide Login WPHH SECURE Secure your WordPress site with one-click file locking, login path hiding, role-based… by WPHackedHelp 100+ ★★★★★★★★★★ 5 (7) 5 months ago 58
7 Anti-Brute Force, Login Fraud Detector WordPress plugin Anti-Brute Force, Login Fraud Detector WordPress plugin Anti-Brute Force, Login Fraud Detector Wordpress plugin is a security plugin that detects… by aispera31 30+ ★★★★★★★★★★ No reviews 3 years ago 24
9 Project Force Field Project Force Field Save your WordPress sites and servers from certain death during brute force attacks with… by Faison 20+ ★★★★★★★★★★ 4.6 (16) 13 years ago 34
10 VMP Security – The All-In-One Security and Firewall Plugin VMP Security – The All-In-One Security and Firewall Plugin Firewall, 9 malware scanners, 2FA, country blocking, audit log preview — all free. 750+ WAF… by VMP™ 10+ ★★★★★★★★★★ 4.5 (2) 2 weeks ago 72
11 Simple Login Guard – Monitor & Block Attempts Simple Login Guard – Monitor & Block Attempts Monitor failed login attempts and automatically block IPs after multiple failures… by Aman Brar 10+ ★★★★★★★★★★ No reviews 12 months ago 38

FAQ

Admin Safety Guard: quick answers

Straight answers, pulled from live WordPress.org data.

Live data from WordPress.org · checked Nov 16, 2026

Is Admin Safety Guard free?

Yes. Admin Safety Guard is free to download and use from the official WordPress.org plugin directory.

Is Admin Safety Guard safe to use in 2026?

Admin Safety Guard works, but test it on a staging site before relying on it in 2026. It runs on 20+ sites, is rated 5/5 and was last updated 3 months ago, and scores 59/100 on our health check.

How many websites use Admin Safety Guard?

Admin Safety Guard is active on 20+ WordPress websites and has been downloaded 3,136 times since it launched in August 2025. It was downloaded 150 times in the last 30 days.

Does Admin Safety Guard work with WordPress 7.1?

Admin Safety Guard is officially tested up to WordPress 7.0.8, while the latest release is 7.1.4. It may still work, but try it on a staging site first.

What PHP version does Admin Safety Guard need?

Admin Safety Guard requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was Admin Safety Guard last updated?

The latest version, 1.4.1, was released on August 13, 2026 (3 months ago).

Who makes Admin Safety Guard?

Admin Safety Guard is developed and maintained by wordpressdirect.

What are the best alternatives to Admin Safety Guard?

The most popular alternatives to Admin Safety Guard are Kadence Security (700K+ installs), Titan Anti-spam & Security (50K+ installs) and Quttera ThreatSign (10K+ 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
Sarah is here to help!
Hi there! 👋 Need help finding what you're looking for?
Sarah
Sarah
Online & Ready to Help
Hi there! 👋 Need help finding what you're looking for?

We'll use this to continue our conversation

Just now ✓ Verified

Join 500+ SEO Pros Scaling Their Strategy

Get exclusive programmatic SEO tactics, AI content workflows, and the latest PageForge updates delivered straight to your inbox. Stay ahead of the algorithm.

We care about your data in our privacy policy.