Welcome to the new IP check page! We're rolling it out gradually and would love your input. Spot a bug, or have a suggestion?
Share feedback
172.70.47.129
Neutral Activity
There is no recent abuse activity, or the IP address is whitelisted.
Whitelisted Subnet
Whitelisted netblocks are typically owned by trusted entities, such as Google or Microsoft who
may use them for search engine spiders. However, these same entities sometimes also provide cloud
servers and mail services which are easily abused. Pay special attention when trusting or
distrusting these IPs.
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 172.70.47.129:
This IP address has been reported a total of
95
times from
28 distinct
sources.
172.70.47.129 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Ukraine
with 4
reports;
United States of America
with 2
reports;
Germany
with 1
report.
The most common categories in these recent reports were:
Web App Attack
6
times;
Bad Web Bot
4
times;
DDoS Attack
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.
Automated honeypot detection. honeypot against a Next.js application. Paths: /wp-admin/install.php. ...
show moreAutomated honeypot detection. honeypot against a Next.js application. Paths: /wp-admin/install.php. Blocked at the edge.
show less
Automated honeypot detection. honeypot against a Next.js application. Paths: /wp-admin/install.php. ...
show moreAutomated honeypot detection. honeypot against a Next.js application. Paths: /wp-admin/install.php. Blocked at the edge.
show less
Web App Attack
Bad Web Bot
Anonymous
[Tue Aug 18 06:42:46.994428 2026] [authz_core:error] [pid 25494] [client 172.70.47.129:12150] AH0163 ...
show more[Tue Aug 18 06:42:46.994428 2026] [authz_core:error] [pid 25494] [client 172.70.47.129:12150] AH01630: client denied by server configuration: /etc/httpd/htdocs
[Tue Aug 18 06:42:55.477474 2026] [authz_core:error] [pid 25496] [client 172.70.47.129:11613] AH01630: client denied by server configuration: /etc/httpd/htdocs
[Tue Aug 18 06:42:55.509883 2026] [authz_core:error] [pid 25518] [client 172.70.47.129:11614] AH01630: client denied by server configuration: /etc/httpd/htdocs
...
show less
Triggered Cloudflare WAF (firewallManaged) from NL.
Action taken: LOG
Protocol: HTTP/2 (GET method)
...
show moreTriggered Cloudflare WAF (firewallManaged) from NL.
Action taken: LOG
Protocol: HTTP/2 (GET method)
Endpoint: /.git/HEAD
UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36
This report was generated by:
https://github.com/sefinek/Cloudflare-WAF-To-AbuseIPDB
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-05-28.
show less
