Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Bots keep hammering my website's login page with guesses

Short answer

Thousands of failed logins are usually bots guessing passwords. They matter only if one guess works, so the first defences are strong unique passwords and a second sign-in step. Limits on repeated attempts help, but each kind has a downside, so use them in layers.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • A security plugin or host emails me about hundreds of failed logins.
  • The server log shows the same login page requested again and again.
  • The site is slow or the hosting plan hits its limits for no clear reason.
  • I got locked out of my own login after someone else's failed attempts.
  • Failed attempts use names like admin or my domain name.

Why does this happen?

  1. Bots try every site, all day

    They do not choose you. They test common usernames and passwords on any login page they find, so the noise starts as soon as the site is online.

  2. Weak and obvious accounts are the target

    WordPress's hardening guide lists brute-force password guessing as a common attack, and says to avoid obvious usernames like admin and to use strong passwords. It also suggests two-step authentication.

  3. Each defence has a weakness

    OWASP's guide to blocking brute force says account lockout can be used to lock real users out and does not stop slow attacks, IP blocking can hit shared networks while attackers rotate proxies, and weak CAPTCHA can be guessed.

  4. The load alone can hurt the site

    Every attempt makes your server check a password. Thousands of them can slow real visitors even when no guess ever succeeds.

  5. A leaked password turns noise into a break-in

    If a real person's password was reused from another site, a guess can succeed on the first try. See the related page on credential stuffing.

What can I do about it today?

  1. Look at whether any login succeededAsk your host or developer to check whether successful logins follow the failed ones. That is the question that matters.
  2. Turn on a second sign-in step for adminsIt stops a correct password from being enough.
  3. Remove obvious accountsRetire a user named admin, and delete accounts of people who left.
  4. Set strong, unique passwordsUse a password manager for everyone with access.
  5. Ask for rate limits and a bot check on the login pageHave them added in layers and test that real staff can still sign in.
  6. Do not block countries or addresses in a hurryIt can lock out your own staff or customers. Ask for a tested change.

When should I bring someone in?

  • There are successful logins you cannot explain.
  • The site slows down or goes offline during the attempts.
  • The login page is for customers, not just staff.

How do I handle it?

  1. Read the logs for what happened, not how loud it wasI separate failed noise from successful logins and from changes made afterwards.
  2. Fix the sign-in firstA second step, unique accounts and removal of obvious usernames.
  3. Add limits in layersDelays, rate limits and a bot check are added one at a time, so that real users are not blocked with the bots.
  4. Reduce the loadWhere the attempts slow the site, I put limits before the application so the server does not do the work.
  5. Set up an alert for success after failureA burst of failures followed by a success is the pattern worth waking up for.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does this mean I have been hacked?

Not by itself. Failed attempts are normal on any public login. A successful login that you cannot explain is the sign to act on.

Is locking the account after a few failures enough?

No. OWASP notes lockouts can be used to lock real users out and do not stop slow attacks, so use them with other layers.

Should I hide the login page?

It reduces noise but does not replace strong sign-in.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.