This IP address has been reported a total of
11
times from
11 distinct
sources.
34.53.134.60 was first reported on
, and the most recent report was
.
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.
(wpscan) WordPress probe detected from 34.53.134.60 (BE/Belgium/60.134.53.34.bc.googleusercontent.co ...
show more(wpscan) WordPress probe detected from 34.53.134.60 (BE/Belgium/60.134.53.34.bc.googleusercontent.com)
show less
Multiple web server 400 error codes from same source ip.
34.53.134.60 - - [22/Oct/2026:15:13:29 +020 ...
show moreMultiple web server 400 error codes from same source ip.
34.53.134.60 - - [22/Oct/2026:15:13:29 +0200] "GET //media/wp-includes/wlwmanifest.xml HTTP/1.1" 404 1517 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36"
show less
Triggered Cloudflare WAF (firewallCustom) from BE.
Action taken: BLOCK
Protocol: HTTP/1.1 (GET metho ...
show moreTriggered Cloudflare WAF (firewallCustom) from BE.
Action taken: BLOCK
Protocol: HTTP/1.1 (GET method)
Endpoint: //site/wp-includes/wlwmanifest.xml
UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
This report was generated by:
https://github.com/sefinek/Cloudflare-WAF-To-AbuseIPDB
show less