AbuseIPDB » 82.94.20.13
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
82.94.20.13 has been reported 8 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 82.94.20.13:
This IP address has been reported a total of 8 times from 8 distinct sources. 82.94.20.13 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 82.94.20.13 to port 22 [J]
|
Port Scan Hacking | ||
| 🇺🇸 atomv |
|
Brute-Force SSH | ||
| 🇹🇷 GHS |
SSH brute-force attempt from 82.94.20.13 on port 22
|
Port Scan Hacking Brute-Force SSH | ||
| 🇯🇵 MU-star.net |
Invalid user pi from 82.94.20.13 port 56436
|
Port Scan Brute-Force SSH | ||
| 🇺🇸 etu brutus |
21/11/26@00:40:28: FAIL: Alarm-SSH address from=82.94.20.13
...
|
Hacking Brute-Force SSH | ||
| 🇺🇸 BiggA94 |
|
Brute-Force SSH | ||
| 🇷🇸 Smel |
SSH/22 MH Probe, BF, Hack -
|
Hacking Brute-Force SSH | ||
| Anonymous |
port scan and connect, tcp 22 (ssh)
|
Port Scan |
Showing 1 to 8 of 8 reports
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩