We keep a record of every request made to our own website for something that does not exist, and I read it. Very little of it comes from people. Most is software working through the internet one address at a time, asking every site the same list of questions in the hope that one of them answers, and it is aimed at us only in the sense that we have a website. Thales reports that bots made up 53% of all web traffic in 2025 and that bad bots alone accounted for 40%, and a server log shows what that looks like from the receiving end.
Nobody Chose You
Owners tend to picture an attacker as a person who has decided to go after their company, and conclude that a business of their size is not worth anybody's trouble. The software doing this work has no idea what size you are. It tries every address it can find, yours included, and it will be back tomorrow whether or not it found anything today. Being small or little known offers no protection, because nobody is doing the choosing.
What They Ask For
The requests fall into a small number of groups, and each one is a bet on a common mistake.
| What is requested | What the sender hopes to find |
|---|---|
| Login pages for popular website software | A site running it with a weak or reused password |
| Files with names such as "backup" or "database" | A copy of the data that somebody left on the server |
| Configuration and settings files | Passwords and keys stored in plain text |
| Admin screens and database tools | A management page left open to the internet |
| Addresses belonging to weak plugins and old versions | Software that has not been updated |
| The same login or form, tried again and again | A system with no limit on attempts |
Our site has never run the popular software these requests go looking for, and they arrive all the same, which tells you how little the sender knows or cares about the target.
Why It Works Often Enough
None of these tricks is clever, and they keep being used because they keep working somewhere. A plugin goes without an update, a developer leaves a backup in a public folder for an afternoon, an old admin account keeps the password it was created with. Software that tries a million sites needs only a few of them to have made one of those mistakes on the day, and whatever it finds is put to use at once, whether for sending spam, holding data to ransom or reaching the customers whose details are stored there.
What We Do With Our Own Logs
Reading a log is only useful if something changes as a result. We export ours regularly, group the requests by what they were looking for and update the rules at the front of the server so that the same requests are refused before they reach the site at all. Then we look again, because the list of questions changes as new weaknesses are published. It is routine work that is never finished, and it is the habit behind the security work we do for clients.
What the Log Cannot Tell You
A log of failed requests shows the attempts that bounced off. The request that should worry you is the one that succeeded, and it looks like any other visit. That is why reading logs has to be paired with testing your own systems the way an attacker would, by scanning everything that faces the internet for the weaknesses in that table and, at intervals, having somebody make a proper attempt to break in. You want to find the open door yourself, on a day of your choosing.
What I'd Want Every Owner to Know
You are already being tested
Every system on the internet is probed daily. The only choice left to you is whether you test it yourself as well.
Most attempts fail for dull reasons
Software kept up to date, limits on login attempts and nothing left lying on the server stop most of what arrives.
Somebody has to be reading
A log that nobody reads protects nothing. Make it one person's job, or pay for it to be somebody else's.
BY BANKS tests systems the way attackers test them and closes the gaps it finds, through the security scans, penetration testing, updates and defence testing in our cyber security service. If you have never seen what your own logs contain, get in touch and I will show you what to look for.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation