AbuseIPDB » 1.164.116.126
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
1.164.116.126 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 1.164.116.126:
This IP address has been reported a total of 8 times from 7 distinct sources. 1.164.116.126 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇺🇸 MPL |
tcp/22
|
Port Scan | ||
| 🇩🇪 rico-j.de |
|
Brute-Force SSH | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 1.164.116.126 to port 22 [J]
|
Port Scan Hacking | ||
| 🇨🇦 Largnet SOC |
1.164.116.126 triggered Icarus honeypot on port 22. Check us out on github.
|
Port Scan Hacking | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 1.164.116.126 to port 22 [J]
|
Port Scan Hacking | ||
| Anonymous |
|
Brute-Force | ||
| 🇵🇱 HBF |
|
Brute-Force SSH | ||
| 🇩🇪 www.blocklist.de |
|
FTP Brute-Force Hacking |
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 🚩