AbuseIPDB » 36.68.13.148
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
36.68.13.148 has been reported 7 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 36.68.13.148:
This IP address has been reported a total of 7 times from 2 distinct sources. 36.68.13.148 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 36.68.13.148 to port 80 [J]
|
Port Scan Hacking | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 36.68.13.148 to port 80 [J]
|
Port Scan Hacking | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 36.68.13.148 to port 80 [J]
|
Port Scan Hacking | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 36.68.13.148 to port 8080 [J]
|
Port Scan Hacking | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 36.68.13.148 to port 23 [J]
|
Port Scan Hacking | ||
| 🇿🇦 IrisFlower |
Unauthorized connection attempt detected from IP address 36.68.13.148 to port 23 [J]
|
Port Scan Hacking | ||
| 🇩🇪 seller_service |
php WP PHPmyadamin ABUSE blocked for 12h
|
Web App Attack |
Showing 1 to 7 of 7 reports
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩