AbuseIPDB » 34.158.217.140
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example previewIP Abuse Reports for 34.158.217.140:
This IP address has been reported a total of 8 times from 8 distinct sources. 34.158.217.140 was first reported on , and the most recent report was . In the last 60 days, the top reporter locations were: United States of America with 4 reports; Germany with 3 reports; Finland with 1 report. The most common categories in these recent reports were: Port Scan 6 times; Hacking 3 times; Web App Attack 2 times; Brute-Force 2 times; DDoS Attack 1 time; Other 1 time.
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇺🇸 TPI-Abuse |
|
Brute-Force Bad Web Bot Web App Attack | ||
| Anonymous |
[TCP/16686] Unsolicited connection attempt on a port with no legitimate public service.
|
Port Scan Hacking | ||
| 🇺🇸 Kurtbaby |
|
Brute-Force Port Scan Hacking | ||
| 🇩🇪 luxuria.cfd |
Honeypot port scan detected. Auto-blocked by XUI Shield.
|
DDoS Attack Port Scan | ||
| 🇩🇪 arc21 |
|
Port Scan | ||
| Anonymous |
*Port Scan* detected from 34.158.217.140 (KR/South Korea/140.217.158.34.bc.googleusercontent.com).
|
Port Scan | ||
| 🇺🇸 azminawwar |
[34.158.217.140] triggered by honeypot on port [5900], Timestamp [2026-09-07T04:50:13Z](no payload)
|
Port Scan Hacking | ||
| 🇺🇸 kosada.com |
|
Web App Attack |
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 🚩