AbuseIPDB » 14.192.213.146
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 14.192.213.146:
This IP address has been reported a total of 24 times from 19 distinct sources. 14.192.213.146 was first reported on , and the most recent report was . In the last 60 days, the top reporter locations were: Germany with 5 reports; Italy with 1 report; Netherlands with 1 report. The most common categories in these recent reports were: Port Scan 5 times; Hacking 2 times; Exploited Host 1 time; Bad Web Bot 1 time.
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=36190 dstport=44712
|
Port Scan | ||
| 🇩🇪 iNetWorker |
firewall-block, port(s): 3227/udp
|
Port Scan | ||
| 🇩🇪 Admins@FBN |
FW-PortScan: Traffic Blocked srcport=36184 dstport=61978
|
Port Scan | ||
| Anonymous |
denied traffic to a non-approved destination port. destination port 18772.
|
Port Scan | ||
| 🇮🇹 CoreTech srl |
[DC: IP:151.1.252.27] ntopng alert: blacklisted_client_contact,ndpi_unsafe_protocol
|
Hacking | ||
| 🇳🇱 DrLex0 |
|
Bad Web Bot Exploited Host | ||
| Anonymous |
denied traffic to a honeypot network. destination port 23.
|
Port Scan Hacking | ||
| 🇳🇱 DrLex0 |
|
Bad Web Bot Exploited Host | ||
| 🇳🇱 DrLex0 |
|
Bad Web Bot Exploited Host | ||
| Anonymous |
Blocked: Reason='Possible SQL injection activity (15/60 min)'; Requests=15
|
SQL Injection | ||
| 🇺🇸 TPI-Abuse |
|
Brute-Force Bad Web Bot Web App Attack | ||
| 🇮🇹 VHosting |
Detected attack and reported by a human
|
DDoS Attack Brute-Force Bad Web Bot Exploited Host Web App Attack SSH | ||
| 🇹🇼 090410-1830 |
Honeypot hit: Unauthorized traffic (470 bytes of payload); 9010 [3] TCP
|
Port Scan | ||
| Anonymous |
Web app attack and vulnerability scan detected from IIS logs
|
Brute-Force Bad Web Bot Web App Attack | ||
| 🇨🇦 polycoda |
🥶 Part of massive botnet scraping campaign that nearly caused turned into a DDoS on 2025-11-27
|
DDoS Attack |
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩