AbuseIPDB » 200.162.134.180
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
No reports in the last 60 days
200.162.134.180 has been reported 9 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 200.162.134.180:
This IP address has been reported a total of 9 times from 5 distinct sources. 200.162.134.180 was first reported on , and the most recent report was .
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇧🇷 Sipo Chutão |
Massive DDOS Attack
|
Hacking | ||
| 🇧🇷 Sipo Chutão |
Massive DDOS Attack
|
Hacking | ||
| 🇧🇷 SZ |
Participating in DDoS Amplification Attack! BLOCK
|
DNS Poisoning | ||
| 🇷🇴 abuse_IP_reporter |
Jan 7 04:17:34 server UFW BLOCK SRC=200.162.134.180
|
Port Scan | ||
| 🇧🇷 SOC-BR |
|
DDoS Attack | ||
| 🇩🇪 Pingger Shikkoken |
|
DNS Poisoning DDoS Attack Hacking Brute-Force Exploited Host | ||
| 🇩🇪 Pingger Shikkoken |
|
DNS Poisoning DDoS Attack Hacking Brute-Force Exploited Host | ||
| 🇩🇪 Pingger Shikkoken |
|
DNS Poisoning DDoS Attack Hacking Brute-Force Exploited Host | ||
| 🇩🇪 Pingger Shikkoken |
Participating in DDoS Amplification Attack
|
DNS Poisoning DDoS Attack Hacking Brute-Force Exploited Host |
Showing 1 to 9 of 9 reports
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩