AbuseIPDB » 82.64.45.50
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
82.64.45.50 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.64.45.50:
This IP address has been reported a total of 8 times from 5 distinct sources. 82.64.45.50 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇫🇷 esteban cardoso |
Automated report for security analysis
|
Brute-Force SSH | ||
| 🇫🇷 JPPO |
Hit port : 53
|
Port Scan | ||
| 🇫🇷 UM3 |
Exim Auth Failed
|
Brute-Force | ||
| 🇫🇷 JPPO |
Hit port : 25(x2)
|
Port Scan | ||
| 🇫🇷 JPPO |
Hit port : 86
|
Port Scan | ||
| Anonymous |
SURICATA UDPv4 invalid checksum
|
Hacking | ||
| 🇺🇸 Mark R |
|
Brute-Force | ||
| 🇫🇷 JPPO |
Hit port : 89
|
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 🚩