This IP address has been reported a total of
29
times from
26 distinct
sources.
34.22.224.197 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.
[probe-44-49] 2026-10-17 11:41:18, Client: 34.22.224.197, Protocol: 6, Unauthorized activity to HTTP ...
show more[probe-44-49] 2026-10-17 11:41:18, Client: 34.22.224.197, Protocol: 6, Unauthorized activity to HTTP: GET /
show less
Connection to IP instead of Domain-Name, HTTP request to HTTPS port [17/Oct/2026:13:36:34 +0200] 400 ...
show moreConnection to IP instead of Domain-Name, HTTP request to HTTPS port [17/Oct/2026:13:36:34 +0200] 400 - GET http "/" [Client 34.22.224.197] [Length 252] [Gzip -] "Mozilla/5.0 (compatible; nmap-http-info)" "-"
...
show less
Date: Oct 17 13:14:27 2026 EAT | Reported IP: 34.22.224.197 mod_security | id: 911100 913100 920350 ...
show moreDate: Oct 17 13:14:27 2026 EAT | Reported IP: 34.22.224.197 mod_security | id: 911100 913100 920350 949110 | BE/usernameab.my_domain/- | Connections: 1 | Blocked: Permanent Block: [LF_MODSEC] | Logs: ; Method is not allowed by policy; Found User-Agent associated with security scanner; Host header is a numeric IP address; Host header is a numeric IP address; Host header is a numeric IP address; Host header is a numeric IP address; Host header is a numeric IP address; Inbound Anomaly Score Exceeded (Total Score: 8); Inbound Anomaly Score Exceeded (Total Score: 8); Host header is a numeric IP address; Host header is a numeric IP address
show less
[arem1] 2026-10-17 09:21:08, Client: 34.22.224.197, Protocol: 6, Unauthorized activity to HTTP: GET ...
show more[arem1] 2026-10-17 09:21:08, Client: 34.22.224.197, Protocol: 6, Unauthorized activity to HTTP: GET /
show less
Connection to port 443 with data transfer.
Data preview: ๏ฟฝ
Port Scan
Hacking
Anonymous
2026-10-17 04:34:32 34.22.224.197:5460 WARNING: Bad encapsulated packet length from peer (5635), whi ...
show more2026-10-17 04:34:32 34.22.224.197:5460 WARNING: Bad encapsulated packet length from peer (5635), which must be > 0 and <= 1768 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]
2026-10-17 04:34:32 34.22.224.197:5474 WARNING: Bad encapsulated packet length from peer (15104), which must be > 0 and <= 1768 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]
2026-10-17 04:34:32 34.22.224.197:5484 WARNING: Bad encapsulated packet length from peer (18245), which must be > 0 and <= 1768 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- this condition could also indicate a possible active attack on the TCP link -- [Attempting restart...]
...
show less