Title: Lockouts and security
Last modified: December 22, 2020

---

# Lockouts and security

 *  [yukilna](https://wordpress.org/support/users/yukilna/)
 * (@yukilna)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/lockouts-and-security/)
 * Hi,
    I have been receiving about 10-30 lockout emails per day from iTheme security
   of different people or robots trying to login onto my website.
 * Would you know why I’m getting so many? It’s been happening in the last month
   or so.
 * I don’t understand why my small tiny website would get so many hacking attempts.
 * Thank you for your help in advance,
 * Have a great week !

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

 *  [jetxpert](https://wordpress.org/support/users/jetxpert/)
 * (@jetxpert)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/lockouts-and-security/#post-13976695)
 * Hi [@yukilna](https://wordpress.org/support/users/yukilna/),
 * If you’re seeing a lot of lockouts, well, that means that iThemes Security is
   doing its job.
 * Like you, we also see a lot of 404s and lockouts, so as long as your website 
   has not been compromised or has a virus, you’re good.
 * As you know, many attacks are from malicious bots or hackers. Once they realize
   they can’t access your site, they will look elsewhere. If you have time, you 
   can also report the IPs associated with the lockouts to the “abuse@xxxxxx.com”
   address associated with the IPs. You may not hear back from the Host Administrator,
   but rest assure, I’m quite sure many take action behind the scenes. Don’t expect
   a “Thank You” reply for every report you submit.
 * You may also have a lot of lockouts depending on your plugin settings. We are
   using the following module settings: [Global Settings](https://prnt.sc/xtk8rq)
   and [404 Detection](https://prnt.sc/xtkc0c).
 * Hope the above helps.
 * Cheers!
 *  [jetxpert](https://wordpress.org/support/users/jetxpert/)
 * (@jetxpert)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/lockouts-and-security/#post-13977084)
 * Hi [@yukilna](https://wordpress.org/support/users/yukilna/) (again),
 * Something else to consider: (you may know this already)
 * (1) If the lockout emails are nagging you, you can always deactivate the iThemes
   Security email setting for lockouts.
 * WP Dashboard > Security > Settings > Notification Center > Site Lockouts > [Uncheck “Enabled”](https://prnt.sc/xtoitb)
 * (2) Attackers care less about company or website size. All they care about is
   obtaining information that will benefit their business or coffers. For example,
   we know of websites that get attacked (hit) **THOUSANDS of times per hour**. 
   Usually, those are targeted attacks, but simply gives you an idea on what your
   website could experience from time to time.
 * (3) In lieu of contacting the “abuse@xxxxx.com” address associated with the malicious
   IPs, you can report them [here](https://www.abuseipdb.com). We do. Very important.
   Helps build a community database and establish abuse patterns that can be reviewed
   and eliminated by the authorities.
 * Cheers!

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

The topic ‘Lockouts and security’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=2980272)
 * [Solid Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [jetxpert](https://wordpress.org/support/users/jetxpert/)
 * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/lockouts-and-security/#post-13977084)
 * Status: not resolved