This IP address has been reported a total of
71
times from
42 distinct
sources.
200.138.46.158 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 24
reports;
United States of America
with 19
reports;
France
with 6
reports.
The most common categories in these recent reports were:
Port Scan
57
times;
Web App Attack
12
times;
Hacking
7
times;
Brute-Force
6
times;
SSH
3
times;
Other
6
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.
Blocked by UFW (TCP on 4097)
Source port: 51804
TTL: 49
Packet length: 40
TOS: 0x08
This report (fo ...
show moreBlocked by UFW (TCP on 4097)
Source port: 51804
TTL: 49
Packet length: 40
TOS: 0x08
This report (for 200.138.46.158) was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T21:07:01+0200. Last: 2026-10-11T21:07:01+0200.
Samples:
- 2026-10-11 00:34:15,320 fail2ban.actions [858]: NOTICE [abuseipdb] Ban 200.138.46.158
show less
Blocked by UFW (TCP on 6027)
Source port: 39243
TTL: 50
Packet length: 40
TOS: 0x08
This report (fo ...
show moreBlocked by UFW (TCP on 6027)
Source port: 39243
TTL: 50
Packet length: 40
TOS: 0x08
This report (for 200.138.46.158) was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
UFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly as ...
show moreUFW blocked a suspicious connection attempt to a closed or denied port. This activity is commonly associated with port scanning, service discovery, or automated internet probing. Technical: source_ip=200.138.46.158; proto=TCP; source_port=62433; target_port=9160
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T16:07:02+0200. Last: 2026-10-11T16:07:02+0200.
Samples:
- 2026-10-11 00:34:15,320 fail2ban.actions [858]: NOTICE [abuseipdb] Ban 200.138.46.158
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T11:07:01+0200. Last: 2026-10-11T11:07:01+0200.
Samples:
- 2026-10-11 00:34:15,320 fail2ban.actions [858]: NOTICE [abuseipdb] Ban 200.138.46.158
show less
Auto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T ...
show moreAuto-report via Fail2Ban aggregation. IP observed in jails: abuseipdb.
Events: 1. First: 2026-10-11T06:07:02+0200. Last: 2026-10-11T06:07:02+0200.
Samples:
- 2026-10-11 00:34:15,320 fail2ban.actions [858]: NOTICE [abuseipdb] Ban 200.138.46.158
show less