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 172.104.31.42:
This IP address has been reported a total of
116
times from
57 distinct
sources.
172.104.31.42 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 18
reports;
United States of America
with 8
reports;
Finland
with 6
reports.
The most common categories in these recent reports were:
Web App Attack
34
times;
Brute-Force
13
times;
Bad Web Bot
11
times;
Hacking
5
times;
SQL Injection
2
times;
Other
7
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.
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T21:07:01+0200. Last: 2026-09-06T21:07:01+0200.
Samples:
- 2026-09-06 00:33:52,434 fail2ban.actions [4095059]: NOTICE [abuseipdb] Ban 172.104.31.42
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T16:07:01+0200. Last: 2026-09-06T16:07:01+0200.
Samples:
- 2026-09-06 00:33:52,434 fail2ban.actions [4095059]: NOTICE [abuseipdb] Ban 172.104.31.42
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T11:07:01+0200. Last: 2026-09-06T11:07:01+0200.
Samples:
- 2026-09-06 00:33:52,434 fail2ban.actions [4095059]: NOTICE [abuseipdb] Ban 172.104.31.42
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T06:07:01+0200. Last: 2026-09-06T06:07:01+0200.
Samples:
- 2026-09-06 00:33:52,434 fail2ban.actions [4095059]: NOTICE [abuseipdb] Ban 172.104.31.42
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-09-06T01:07:01+0200. Last: 2026-09-06T01:07:01+0200.
Samples:
- 2026-09-06 00:33:52,434 fail2ban.actions [4095059]: NOTICE [abuseipdb] Ban 172.104.31.42
show less
Fail2Ban offender in jail [recidive] — 1 total attempts — tracked by mercurius-guide.com security sy ...
show moreFail2Ban offender in jail [recidive] — 1 total attempts — tracked by mercurius-guide.com security system.
show less
Malware host (X-Forwarded-For) detected by rbl.malware.expert. RBL lookup of 42.31.104.172.rbl.malwa ...
show moreMalware host (X-Forwarded-For) detected by rbl.malware.expert. RBL lookup of 42.31.104.172.rbl.malware.expert succeeded at REQUEST_HEADERS:x-forwarded-for. (1001000-mnz6-3)
show less
Blocked by nakordoni.eu automated security: nakordoni-probe-gate. Jail: nakordoni-probe-gate, 1 matc ...
show moreBlocked by nakordoni.eu automated security: nakordoni-probe-gate. Jail: nakordoni-probe-gate, 1 matches. ISP: Linode (US), Usage: Data Center/Web Hosting/Transit. Prior AbuseIPDB score at ban time: 100/100.
show less
[2026-09-05 11:59:44 UTC] Vulnerability/exploit scanning detected from 172.104.31.42 (172-104-31-42. ...
show more[2026-09-05 11:59:44 UTC] Vulnerability/exploit scanning detected from 172.104.31.42 (172-104-31-42.ip.linodeusercontent.com) PATHS: HEAD /wp-admin/ HTTP/1.1|HEAD /wp-admin/ HTTP/1.1
show less
