IP Threat Report
104.28.219.190
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 23/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/2s | Abnormally fast request rate — automated scanning | +35 | |
| DDoS / Flood | Behavioral anomaly detected by automated analysis | +0 | |
| Danger strong hits: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Recommendations
Actions taken & recommended
- IP 104.28.219.190 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 104.28.219.0/24
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 104.28.219.190 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 104.28.219.190.
🤖 User-Agent Anomaly Defense
IP 104.28.219.190 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Neighbors in 104.28.219.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
104.28.219.190 has been assigned a threat score of 220/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 104.28.219.190, located in Kansas City, United States, operating on the network of Cloudflare, Inc., has been classified as malicious by our automated threat scoring engine. Over a period of 53 days, this IP generated 479 malicious requests, averaging approximately 9 requests per day. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. United States currently accounts for 138 blocked IPs in our database, making it a significant source of malicious traffic. A score of 220/100 places this address in the top tier of severity. Block and investigate any historical connections.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 Tor Exit Node Detection
Tor exit nodes are publicly listed but constantly rotating. While Tor serves essential privacy functions for journalists and activists, it is also used to anonymize attacks. Effective security policies differentiate between blocking and monitoring Tor traffic.