This IP address has been reported a total of
48
times from
22 distinct
sources.
8.229.227.130 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 21
reports;
Germany
with 10
reports;
United Kingdom of Great Britain and Northern Ireland
with 7
reports.
The most common categories in these recent reports were:
Web App Attack
34
times;
Bad Web Bot
33
times;
Brute-Force
21
times;
Port Scan
7
times;
Hacking
4
times;
Other
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.
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
(mod_security) mod_security (id:210730) triggered by 8.229.227.130 (130.227.229.8.bc.googleuserconte ...
show more(mod_security) mod_security (id:210730) triggered by 8.229.227.130 (130.227.229.8.bc.googleusercontent.com): 1 in the last 300 secs; Ports: *; Direction: 1; Trigger: LF_MODSEC; Logs: [Fri Oct 02 22:27:18.993705 2026] [security2:error] [pid 30021:tid 30021] [client 8.229.227.130:49150] ModSecurity: Access denied with code 403 (phase 2). Match of "pmFromFile userdata_wl_extensions" against "TX:extension" required. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/10_HTTP_HTTP.conf"] [line "27"] [id "210730"] [rev "5"] [msg "COMODO WAF: URL file extension is restricted by policy||www.theurbanlogger.com|F|2"] [data ".theurbanlogger.com"] [severity "CRITICAL"] [tag "CWAF"] [tag "HTTP"] [hostname "www.theurbanlogger.com"] [uri "/z9x8c7v6b5-debug-trigger-www.theurbanlogger.com"] [unique_id "asBoBm5oo2dGzgZz_qgVvAAAAAA"]
show less
Brute-Force
Bad Web Bot
Web App Attack
Anonymous
[Sat Oct 03 03:25:56.660429 2026] [php:error] [pid 2865238] [client 8.229.227.130:56254] script '/va ...
show more[Sat Oct 03 03:25:56.660429 2026] [php:error] [pid 2865238] [client 8.229.227.130:56254] script '/var/www/11spielerinnen.de/public_html/document.php' not found or unable to stat
...
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
