This IP address has been reported a total of
423
times from
309 distinct
sources.
4.228.97.66 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.
Coordinated Azure webshell scanning campaign against 84.46.253.134. Active May-Jun 2026. ZAC Bayern ...
show moreCoordinated Azure webshell scanning campaign against 84.46.253.134. Active May-Jun 2026. ZAC Bayern ref BY0257-500359-26/8.
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-31T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-31T01:07:02+0200. Last: 2026-05-31T01:07:02+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T21:07:01+0200. Last: 2026-05-30T21:07:01+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T16:07:01+0200. Last: 2026-05-30T16:07:01+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T11:07:02+0200. Last: 2026-05-30T11:07:02+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T06:07:02+0200. Last: 2026-05-30T06:07:02+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-30T01:07:01+0200. Last: 2026-05-30T01:07:01+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-29T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-29T21:07:01+0200. Last: 2026-05-29T21:07:01+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-29T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-05-29T16:07:01+0200. Last: 2026-05-29T16:07:01+0200.
Samples:
- 2026-05-24 00:35:27,115 fail2ban.actions [1405153]: NOTICE [abuseipdb] Ban 4.228.97.66
show less