AbuseIPDB » 2.61.101.30
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
2.61.101.30 has been reported 10 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 2.61.101.30:
This IP address has been reported a total of 10 times from 6 distinct sources. 2.61.101.30 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇩🇪 KPS |
PortscanT
|
Port Scan | ||
| 🇩🇪 KPS |
PortscanM
|
Port Scan | ||
| 🇵🇱 ChillScanner |
1 probe(s) @ TCP(22)
|
Port Scan | ||
| 🇩🇪 ps-center |
DIS-W: TCP-Scanner. Port: 22
|
Port Scan | ||
| 🇺🇸 boenyc |
|
Port Scan Hacking Brute-Force SSH | ||
| 🇫🇷 NXO WAN |
Jun 24 06:43:40 : SSH login attempts with invalid user
|
Brute-Force SSH | ||
| 🇩🇪 ps-center |
C2-W: TCP-Scanner. Port: 22
|
Port Scan | ||
| 🇩🇪 ps-center |
SS4-W: TCP-Scanner. Port: 22
|
Port Scan | ||
| 🇩🇪 ps-center |
ENG-W: TCP-Scanner. Port: 22
|
Port Scan | ||
| 🇫🇷 sbocquet |
Port 22 scanned.
|
Port Scan |
Showing 1 to 10 of 10 reports
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩