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
34.34.229.69
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 34.34.229.69:
This IP address has been reported a total of
26
times from
22 distinct
sources.
34.34.229.69 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 7
reports;
Germany
with 5
reports;
New Zealand
with 3
reports.
The most common categories in these recent reports were:
Web App Attack
19
times;
Bad Web Bot
13
times;
Brute-Force
4
times;
Hacking
3
times;
Port Scan
2
times;
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.
Automated Wazuh local observation. Wazuh rule 31151 lvl=10 detected repeated HTTP web application pr ...
show moreAutomated Wazuh local observation. Wazuh rule 31151 lvl=10 detected repeated HTTP web application probing from this source IP. Observed 1 matching blocked event(s) between 2026-09-06T22:22:05+02:00 and 2026-09-06T22:22:05+02:00. Sample requested paths: /src.
show less
Web vulnerability scanning against ad-serving endpoint: 207 probe requests between 31/Aug/2026:01:39 ...
show moreWeb vulnerability scanning against ad-serving endpoint: 207 probe requests between 31/Aug/2026:01:39:07 +0000 and 31/Aug/2026:01:39:08 +0000 for non-existent sensitive paths (/application/.env, /config/.git/config, /site/.git/config, /core/.env, /app/.git/config), all returned 404. Detected via nginx ingress access log.
show less
LF_MODSEC: (mod_security) mod_security (id:1000001) triggered by 34.34.229.69 (US/United States/-): ...
show moreLF_MODSEC: (mod_security) mod_security (id:1000001) triggered by 34.34.229.69 (US/United States/-): 1 in the last 3600 secs
show less
Web App Attack
Anonymous
[Sun Aug 30 20:35:21.375235 2026] [authz_core:error] [pid 12939] [client 34.34.229.69:38016] AH01630 ...
show more[Sun Aug 30 20:35:21.375235 2026] [authz_core:error] [pid 12939] [client 34.34.229.69:38016] AH01630: client denied by server configuration: /var/www/frapi/src/frapi/admin/public/.htaccess88192983f3ee490cb2a7fa71f12f08d5
[Sun Aug 30 20:35:21.376850 2026] [authz_core:error] [pid 12086] [client 34.34.229.69:1838] AH01630: client denied by server configuration: /var/www/frapi/src/frapi/admin/public/.htaccess66b9c6d23bc946cdb813dd227af0b3d9148bbbd82c454c0bbc51471cd55dc0462409fb53e4da4c648dbbe2bab2b7f01c
[Sun Aug 30 20:35:22.374815 2026] [authz_core:error] [pid 13080] [client 34.34.229.69:61312] AH01630: client denied by server configuration: /var/www/frapi/src/frapi/admin/public/scripts/.htaccessb7398847b6d642b1ae4c21e974bab063c299cd770f684263801db50a0298c16f5a2b7692e0284189b9d18cf123a593ff
[Sun Aug 30 20:35:22.378315 2026] [authz_core:error] [pid 12939] [client 34.34.229.69:38016] AH01630: client denied by server configuration: /var/www/frapi/src/frapi/admin/public/scripts/.htaccessab2cb60fb6824b308582e81e73c571
show less
