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.
This IP address has been reported a total of
39
times from
16 distinct
sources.
172.64.192.4 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 6
reports;
Belgium
with 2
reports;
United Kingdom of Great Britain and Northern Ireland
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
9
times;
Bad Web Bot
4
times;
Port Scan
3
times;
Brute-Force
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
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
(caddyscan) Scanner path probe from 172.64.192.4 (GB/United Kingdom/-): 5 in the last 3600 secs; Por ...
show more(caddyscan) Scanner path probe from 172.64.192.4 (GB/United Kingdom/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_CUSTOMTRIGGER; Logs: [REDACTED] 200 2627 172.64.192.4 - - [12/Sep/2026:21:29:36 +0000] "GET /.env.remote HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [12/Sep/2026:21:29:37 +0000] "GET /.env.save HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [12/Sep/2026:21:29:37 +0000] "GET /.env.old HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [12/Sep/2026:21:29:37 +0000] "GET /.env.sample HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [12/Sep/2026:21:29:38 +0000] "GET /.env.example HTTP/1.1"
show less
Port Scan
Anonymous
(caddyscan) Scanner path probe from 172.64.192.4 (GB/United Kingdom/-): 5 in the last 3600 secs; Por ...
show more(caddyscan) Scanner path probe from 172.64.192.4 (GB/United Kingdom/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_CUSTOMTRIGGER; Logs: [REDACTED] 200 2627 172.64.192.4 - - [11/Sep/2026:03:32:30 +0000] "GET /.env.sample HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [11/Sep/2026:03:32:36 +0000] "GET /admin/.env HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [11/Sep/2026:03:32:37 +0000] "GET /backend/.env HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [11/Sep/2026:03:32:37 +0000] "GET /server/.env HTTP/1.1"
[REDACTED] 200 2627 172.64.192.4 - - [11/Sep/2026:03:32:37 +0000] "GET /frontend/.env HTTP/1.1"
show less
Automated attack traffic against a WordPress site: login brute-force blocked by WordPress security p ...
show moreAutomated attack traffic against a WordPress site: login brute-force blocked by WordPress security plugin (1x). Blocked by CDN/WAF/application security layers. Total 1 hits in last 30 days.
show less
