Log in to view charts and search reports for this IP.
Log In
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 34.53.159.125:
This IP address has been reported a total of
26
times from
26 distinct
sources.
34.53.159.125 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 3
reports;
United States of America
with 2
reports;
Belgium
with 1
report.
The most common categories in these recent reports were:
Web App Attack
5
times;
Bad Web Bot
4
times;
Brute-Force
3
times;
Web Spam
1
time;
Hacking
1
time;
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.
1.715 requests with url.path //xmlrpc.php
1.464 requests with url.path */wp-includes/wlwmanifest.x ...
show more1.715 requests with url.path //xmlrpc.php
1.464 requests with url.path */wp-includes/wlwmanifest.xml
show less
Triggered Cloudflare WAF (firewallManaged) from BE.
Action taken: LOG
Protocol: HTTP/1.1 (GET method ...
show moreTriggered Cloudflare WAF (firewallManaged) from BE.
Action taken: LOG
Protocol: HTTP/1.1 (GET method)
Endpoint: //test/wp-includes/wlwmanifest.xml
UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36
This report was generated by:
https://github.com/sefinek/Cloudflare-WAF-To-AbuseIPDB
show less
Web application attack / vulnerability scanning against our public nginx web server (TCP 80/443). So ...
show moreWeb application attack / vulnerability scanning against our public nginx web server (TCP 80/443). Source matched a blocked-path security rule (jail nginx-444); server returned HTTP 444 (connection closed without response). TCP three-way handshake completed (full HTTP request received).
show less
36 attack(s) detected, such as these: {"event":"web_block","ip":"34.53.159.125","host":"api.marche-b ...
show more36 attack(s) detected, such as these: {"event":"web_block","ip":"34.53.159.125","host":"api.marche-be.com","request":"","user_agent":"","reason":"Status-0","timestamp":"2026-09-10T04:44:26 00:00","logentry":"api.marche-be.com 34.53.159.125 - - [10/Sep/2026:06:44:26 0200] \"\" 400 0 \"-\" \"-\" \"-\""} * Report Details *: https://p4u.xyz/FI2T6WDNSGB/1* IP Details *: https://p4u.xyz/FI2T6WDNSGB/2
show less
ActiveDefense automated detection: malicious HTTP scanning / exploit attempts. Signatures: tls_probe ...
show moreActiveDefense automated detection: malicious HTTP scanning / exploit attempts. Signatures: tls_probe. Observed by 1 sensor(s); 6 hits.
show less
Port Scan
Bad Web Bot
Anonymous
Probing for known exploit paths (.env, .git, wp-admin, shell files, etc.). Single-strike ban policy ...
show moreProbing for known exploit paths (.env, .git, wp-admin, shell files, etc.). Single-strike ban policy — zero tolerance for exploit scanning. Banned Jul 11, 07:41 UTC. Origin: Belgium, Brussels.
show less