This IP address has been reported a total of
15
times from
11 distinct
sources.
34.1.165.196 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Czechia
with 3
reports;
Netherlands
with 3
reports;
Germany
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
15
times;
Bad Web Bot
6
times;
Brute-Force
5
times;
Hacking
2
times;
Port Scan
1
time;
Other
1
time.
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.
3 incidents: web scanning/attack. First: 2026-10-06 13:15, Last: 2026-10-11 09:53 UTC. Triggers: ngi ...
show more3 incidents: web scanning/attack. First: 2026-10-06 13:15, Last: 2026-10-11 09:53 UTC. Triggers: nginx-noscript,nginx-botsearch,unknown.
show less
Auto-ban: single probe for restricted files (.env / backups / admin endpoints). Likely mass-scan on ...
show moreAuto-ban: single probe for restricted files (.env / backups / admin endpoints). Likely mass-scan on 2026-10-06.
show less
[cb-06al] Web exploit scanning: 1 suspicious requests detected by fail2ban jail apache-scanner. Exam ...
show more[cb-06al] Web exploit scanning: 1 suspicious requests detected by fail2ban jail apache-scanner. Example: 34.1.165.196 - - [06/Oct/2026:19:27:12 +0200] "GET /.env.txt HTTP/2.0" 404 1338 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"
...
show less
