Log in to view charts and search reports for this IP.
Log In
Reports Activity
Example preview
Report Categories (Last 60 Days)
Example preview
Top Reporter Countries (Last 60 Days)
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 104.28.239.218
This IP address has been reported a total of
499
times from
225 distinct
sources.
104.28.239.218 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 12
reports;
United States of America
with 12
reports;
Spain
with 6
reports.
The most common categories in these recent reports were:
Web App Attack
31
times;
Brute-Force
15
times;
Bad Web Bot
11
times;
Hacking
8
times;
DDoS Attack
6
times;
Other
12
times.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
Blocked by UFW (TCP on 54809)
Source port: 29876
TTL: 51
Packet length: 60
TOS: 0x00
This report (f ...
show moreBlocked by UFW (TCP on 54809)
Source port: 29876
TTL: 51
Packet length: 60
TOS: 0x00
This report (for 104.28.239.218) was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less
Reported by Akarguard DDoS protection: this IP exceeded the per-IP rate limit at our reverse-proxy e ...
show moreReported by Akarguard DDoS protection: this IP exceeded the per-IP rate limit at our reverse-proxy edge (repeated HTTP 444), consistent with an automated Layer 7 flood.
show less
Reported by Akarguard DDoS protection: this IP exceeded the per-IP rate limit at our reverse-proxy e ...
show moreReported by Akarguard DDoS protection: this IP exceeded the per-IP rate limit at our reverse-proxy edge (repeated HTTP 444), consistent with an automated Layer 7 flood.
show less
Reported by Akarguard DDoS protection: this IP exceeded the per-IP rate limit at our reverse-proxy e ...
show moreReported by Akarguard DDoS protection: this IP exceeded the per-IP rate limit at our reverse-proxy edge (repeated HTTP 444), consistent with an automated Layer 7 flood.
show less