This IP address has been reported a total of
44
times from
38 distinct
sources.
165.245.230.111 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 7
reports;
France
with 7
reports;
Netherlands
with 7
reports.
The most common categories in these recent reports were:
Web App Attack
34
times;
Bad Web Bot
18
times;
Brute-Force
13
times;
Hacking
4
times;
Port Scan
3
times;
Other
2
times.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
[ti-14al] Excessive 404 errors (web scanning): 25 suspicious requests detected by fail2ban jail <nam ...
show more[ti-14al] Excessive 404 errors (web scanning): 25 suspicious requests detected by fail2ban jail <name>. Example: 165.245.230.111 - - \[19/Oct/2026:21:04:44 +0200\] "HEAD /press/ HTTP/1.1" 404 317 "http://onderhoudsbedrijfsander.nl/press/" "Mozilla/5.0 \(X11\; Linux x86_64\; rv:127.0\) Gecko/20100101 Firefox/127.0"
165.245.230.111 - - \[19/Oct/2026:21:04:45 +0200\] "HEAD /shop/ HTTP/1.1" 404 317 "http://onderhoudsbedrijfsander.nl/shop/" "Mozilla/5.0 \(Linux\; Android 11\; moto g31\) AppleWebKit/537.36 \(KHTML, like Gecko\) Chrome/122.0.6261.96 Mobile Safari/537.36"
165.245.230.111 - - \[19/Oct/2026:21:04:46 +0200\] "HEAD /old/ HTTP/1.1" 404 317 "http://onderhoudsbedrijfsander.nl/old/" "Mozilla/5.0 \(Windows NT 11.0\; Win64\; x64\) AppleWebKit/537.36 \(KHTML, like Gecko\) Chrome/128.0.6540.18 Safari/537.36"
onderh
...
show less
Bad Web Bot
Web App Attack
Anonymous
Blocked by FortiWeb WAF ML threat detection. ML probability: 99%, Country: CA, Attack patterns: Word ...
show moreBlocked by FortiWeb WAF ML threat detection. ML probability: 99%, Country: CA, Attack patterns: WordPress scanning, Backup file probing
show less
Automated web scanning detected by Wazuh (rule 100180): repeated 400/404 errors from mass probing of ...
show moreAutomated web scanning detected by Wazuh (rule 100180): repeated 400/404 errors from mass probing of admin/backdoor paths (e.g. wp-login.php, known CMS shell filenames) on an Apache web server, on 2026-10-20 03:38 UTC.
show less
