AbuseIPDB » 58.48.42.202
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
58.48.42.202 has been reported 771 times. The most recent report is from .
The full history is preserved below and remains searchable. A 0% score reflects the absence of recent activity, but this is not a guarantee that earlier reports were invalid. Abuse confidence score decays, naturally, over time, when the abusive activity stops.
IP Abuse Reports for 58.48.42.202:
This IP address has been reported a total of 771 times from 49 distinct sources. 58.48.42.202 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇳🇱 Linuxmalwarehuntingnl |
Unauthorized connection attempt
|
Brute-Force | ||
| 🇩🇪 iNetWorker |
firewall-block, port(s): 8090/tcp
|
Port Scan | ||
| 🇧🇷 diego |
Events: TCP SYN Discovery or Flooding, Seen 6 times in the last 10800 seconds
|
DDoS Attack | ||
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=52051 dstport=6379
|
Port Scan | ||
| 🇺🇸 MPL |
tcp/8090 (10 or more attempts)
|
Port Scan | ||
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=23903 dstport=6379
|
Port Scan | ||
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=51711 dstport=6379
|
Port Scan | ||
| 🇺🇸 deangelys |
Honeypot activity: Unauthorized portscan activity of port(s):8088
|
Port Scan | ||
| 🇧🇷 diego |
Events: TCP SYN Discovery or Flooding, Seen 8 times in the last 10800 seconds
|
DDoS Attack | ||
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=51919 dstport=8090
|
Port Scan | ||
| 🇧🇷 diego |
|
Hacking | ||
| 🇧🇷 diego |
Events: TCP SYN Discovery or Flooding, Seen 4 times in the last 10800 seconds
|
DDoS Attack | ||
| 🇩🇪 iNetWorker |
firewall-block, port(s): 8088/tcp
|
Port Scan | ||
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=10180 dstport=8088
|
Port Scan | ||
| 🇧🇷 diego |
Events: TCP SYN Discovery or Flooding, Seen 4 times in the last 10800 seconds
|
DDoS Attack |
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩