Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
188.212.135.164 has been reported 157
times. The most recent report is from
.
The full history is preserved below and remains searchable. A
0% score reflects the absence of recent activity, but
this is not a guarantee that earlier reports were invalid. Abuse confidence score decays,
naturally, over time, when the abusive activity stops.
IP Abuse Reports for 188.212.135.164:
This IP address has been reported a total of
157
times from
69 distinct
sources.
188.212.135.164 was first reported on
, and the most recent report was
.
Triggered Cloudflare WAF (firewallCustom) from PL.
Action taken: MANAGED_CHALLENGE
Protocol: HTTP/1. ...
show moreTriggered Cloudflare WAF (firewallCustom) from PL.
Action taken: MANAGED_CHALLENGE
Protocol: HTTP/1.1 (GET method)
Endpoint: /wp-admin/css/colors/midnight/
UA: Mozilla/5.0 (Windows NT 10.0; WOW64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36 OPR/70.0.3728.95
This report was generated by:
https://github.com/sefinek/Cloudflare-WAF-To-AbuseIPDB
show less
Triggered Cloudflare WAF (firewallManaged) from PL.
Action taken: LOG
Protocol: HTTP/2 (HEAD method) ...
show moreTriggered Cloudflare WAF (firewallManaged) from PL.
Action taken: LOG
Protocol: HTTP/2 (HEAD method)
Endpoint: /old/wallet.dat
UA: Empty string
This report was generated by:
https://github.com/sefinek/Cloudflare-WAF-To-AbuseIPDB
show less
ban-reviewer auto report; ip=188.212.135.164; scenario=http:scan; verdict=valid_ban; confidence=0.85 ...
show moreban-reviewer auto report; ip=188.212.135.164; scenario=http:scan; verdict=valid_ban; confidence=0.85; categories=14,15,18; active_decisions=1; lookback_decisions=1; nginx_requests=0; appsec_matches=0; auth_events=0; kernel_events=0; signals=IP flagged for HTTP scanning activity (scenario: http:scan); Decision is part of a sustained abuse pattern (ip_active_decisions_total: 1); No evidence of legitimate use or user activity in the summary
show less