Title: Permanent Block when attempted login using &quot;admin&quot;
Last modified: August 21, 2016

---

# Permanent Block when attempted login using "admin"

 *  Resolved [photaust](https://wordpress.org/support/users/photaust/)
 * (@photaust)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/)
 * Hi All,
 * I am astounded by the number and frequency of attempted unauthorised logins across
   all my WP sites with “ADMIN” being submitted as the username.
 * Is there a way to automatically and permanently block the IP of all visitors 
   who attempt to login using “admin” ?
 * If not, this would be a very handy addition to any future upgrades.
 * Cheers,
 * Anthony
 * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/)

Viewing 7 replies - 1 through 7 (of 7 total)

 *  [RobinInTexas](https://wordpress.org/support/users/robinintexas/)
 * (@robinintexas)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822471)
 * Simply check off “Immediately lock out invalid usernames” under options. Unless
   you have “ADMIN” as a user, they only get one attempt before they are blocked
   for up to 60 days. The important thing is to use strong passwords and use a low
   number or failed login attempts. I have been getting attempts blocked for the
   actual (obfuscated) admin user which is something like “hez3%QFJ35”.
 *  Thread Starter [photaust](https://wordpress.org/support/users/photaust/)
 * (@photaust)
 * [12 years, 1 month ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822505)
 * Hey Robinin Texas,
 * Thank you for your message.
 * I looked at that option. The only problem is that I run a membership site and
   often legitimate mistakes are made be members entering their username incorrectly.
   It would cause even more issues if these guys had their IP permanently blocked
   when this happens.
 * For this reason, it would be great is Wordfence enabled a feature whereby we 
   could nominate the specific common hack usernames such as “admin” to permanently
   block.
 * Cheers,
    Anthony
 *  [DavidBrugge](https://wordpress.org/support/users/davidbrugge/)
 * (@davidbrugge)
 * [12 years ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822585)
 * **Users have been begging for this feature for ages.**
 * In fact, [the long going thread](http://wordpress.org/support/topic/block-ips-of-all-admin-logins?)
   is marked _resolved _although the problem was never addressed. **Mark **(Wordfence
   author) commented early in the thread with the suggestion of blocking everyone
   that makes an attempt that is not recognized as a user.
 * It has been pointed out time and time again that this method penalizes those 
   who make mistakes typing or who momentarily forget their username. This forces
   users, if they are not the only useer, to balance between security and usability.
   There should be no need for this.
 * I have to conclude that for some undisclosed reason, this is difficult to implement(
   I can’t imagine why that would be) or that **Mark **just doesn’t care.
 * I also have a personal correspondence with **Mark**, asking for this feature.
   He responded that he would look to adding it to a future update. That was many,
   many updates ago.
 * I started out as a huge fan of this product, bought multiple site licenses and
   talked it up at WP user’s group meetings. When I saw how many people were clamoring
   for this feature, I assumed that it would be just a release away, then another
   release, then another.
 * Now I’m pissed. I am sick and tired of the dozens and dozens of email alerts 
   telling me that user ‘admin” at such and such IP has been blocked. I routinely
   scan my alerts for any of my client’s having problems accessing their sites. 
   How to I spot an alert with essential information? If I limit the number of alerts,
   how do I know I won’t miss an important one.
 * This is such an easy bone to throw, it seems like **Mark and company** are too
   wrapped up in their success and in their development to concern themselves with
   trifling things like customer service.
 *  [webby1973](https://wordpress.org/support/users/webby1973/)
 * (@webby1973)
 * [12 years ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822624)
 * I agree with the request, it would be really helpful an option to automatically
   block “admin” and other unwanted names (a field where the real admin can enter
   a list would be fine), for a given time.
 *  [black lion](https://wordpress.org/support/users/black-lion/)
 * (@black-lion)
 * [12 years ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822644)
 * This I wha looking fot to. Now I got it. Tnx Robin Texas.
 *  Plugin Author [Mark Maunder](https://wordpress.org/support/users/mmaunder/)
 * (@mmaunder)
 * [12 years ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822645)
 * > For this reason, it would be great is Wordfence enabled a feature whereby we
   > could nominate the specific common hack usernames such as “admin” to permanently
   > block.
 * This will be in the next release. But don’t take my word for it. My co-founder
   Kerry posted this about 20 minutes ago:
 * [http://wordpress.org/support/topic/large-number-of-failed-logins?replies=3#post-5545076](http://wordpress.org/support/topic/large-number-of-failed-logins?replies=3#post-5545076)
 * [@davidbrugge](https://wordpress.org/support/users/davidbrugge/) My humble apologies
   sir. As an advocate for our product I’d like to assure you that we’re not resting
   on our laurels and are taking note of your feedback. There were some core features
   and fixes we needed to get into the product before we could get on to other feature
   requests and these caused a delay in us implementing this feature. I can assure
   you that it will be in the next release and the timeline for this is that we 
   will be releasing a Beta on approximately Friday this week with the production
   version coming out the following Sunday or Monday depending on how many issues
   are reported by our Beta testers.
 * I’m a bit nervous about marking this resolved, but I’m going to go ahead and 
   do that and please trust me that this will be in the next release.
 * Regards,
 * Mark.
 *  Plugin Author [Mark Maunder](https://wordpress.org/support/users/mmaunder/)
 * (@mmaunder)
 * [12 years ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822649)
 * This feature has been implemented and will be released in the Beta release going
   out tomorrow and into production later this weekend or Monday.
 * Regards,
 * Mark.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Permanent Block when attempted login using "admin"’ is closed to new 
replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

## Tags

 * [admin](https://wordpress.org/support/topic-tag/admin/)
 * [block](https://wordpress.org/support/topic-tag/block/)
 * [login](https://wordpress.org/support/topic-tag/login/)
 * [permanent](https://wordpress.org/support/topic-tag/permanent/)
 * [unauthorized](https://wordpress.org/support/topic-tag/unauthorized/)

 * 7 replies
 * 6 participants
 * Last reply from: [Mark Maunder](https://wordpress.org/support/users/mmaunder/)
 * Last activity: [12 years ago](https://wordpress.org/support/topic/permanent-block-when-attempted-login-using-admin/#post-4822649)
 * Status: resolved