This IP address has been reported a total of
44
times from
35 distinct
sources.
104.197.109.108 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.
Detected by CrowdSec IDS on a self-hosted server. Target: HTTP/HTTPS (ports 80/443). Triggered rules ...
show moreDetected by CrowdSec IDS on a self-hosted server. Target: HTTP/HTTPS (ports 80/443). Triggered rules: http-probing, http-sensitive-files. 16 matching log events at 2026-08-29T01:11:41Z (UTC). Sample requests: GET /.env.dev -> 404; GET /.env.old -> 404; GET /wp-config.php~ -> 404; GET /.env.local -> 404; GET /wp-config.php.swp -> 404; GET /wp-config.php.bak -> 404; GET /.env.production -> 404; GET /.env.backup -> 404; GET /.env.example -> 404; GET /.env.save -> 404; GET /.env.prod -> 404; GET /.env -> 301
show less
K5 Services fail2ban jail nginx-k5-web-probes detected high-confidence web abuse. Local web ban appl ...
show moreK5 Services fail2ban jail nginx-k5-web-probes detected high-confidence web abuse. Local web ban applied. Categories: 19,21.
show less
(mod_security) mod_security triggered on hostname [redacted] 104.197.109.108 (US/United States/108.1 ...
show more(mod_security) mod_security triggered on hostname [redacted] 104.197.109.108 (US/United States/108.109.197.104.bc.googleusercontent.com)
show less