This IP address has been reported a total of
73
times from
55 distinct
sources.
35.193.152.68 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 19
reports;
United Kingdom of Great Britain and Northern Ireland
with 10
reports;
Netherlands
with 10
reports.
The most common categories in these recent reports were:
Web App Attack
46
times;
Bad Web Bot
24
times;
Brute-Force
21
times;
Port Scan
15
times;
Hacking
13
times;
Other
10
times.
Old Reports
The most recent abuse report for this IP address is from
. It is possible that this IP is no
longer involved in abusive activities.
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
2026-09-27 05:47:29,071 fail2ban.actions [594716]: NOTICE [ipblocklist] Ban 35.193.152.68
.. ...
show more2026-09-27 05:47:29,071 fail2ban.actions [594716]: NOTICE [ipblocklist] Ban 35.193.152.68
...
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
malicious bot detected: violations="hit-honeypot"; user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; ...
show moremalicious bot detected: violations="hit-honeypot"; user_agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36"
show less
Fail2Ban - [RECIDIVE]Repeat offender across multiple jails on recidive ... [ice01,ice02,mx01,mx02,mx ...
show moreFail2Ban - [RECIDIVE]Repeat offender across multiple jails on recidive ... [ice01,ice02,mx01,mx02,mx03,wa01,wa02]
show less
Brute-Force
Bad Web Bot
Exploited Host
Web App Attack
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
CrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban tri ...
show moreCrowdSec detected Web application reconnaissance. Scenario: local/framework-recon. Automatic ban triggered. Detection time (UTC): 2026-09-27T04:24:29.899105235Z. Context: http_status=404
show less
