ABUSE.MOM
THREAT REPORT

IP Threat Report
216.24.210.220

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 01:11:00
First seen: 2026-05-22 23:34:45
Last seen: 2026-05-24 09:44:02
100

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 100/100. Total malicious requests observed: 92.

DANGER_PATHRATIO_404UA_CHANGED
01

Geolocation & Classification

IP Address
216.24.210.220
Type
Hosting
Country
🇺🇸 United States
City
Los Angeles
ISP
Ipxo LLC
Organization
Unknown
Autonomous System
AS62240 Clouvider
Hit Count
92
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 100
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-05-22 23:34:45
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 1 (+10), Danger strong hits: 2 (+50)
2026-05-24 09:44:02
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Ipxo LLC
AS62240 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 216.24.210.220 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 216.24.210.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 216.24.210.220 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

Address UA spoofing from 216.24.210.220: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 216.24.210.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

216.24.210.220 has been assigned a threat score of 100/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 216.24.210.220 to malicious activity originating from Los Angeles, United States, operating on the network of Ipxo LLC. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 92 hostile requests from this IP — roughly 92 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 217 blocked IPs in our database, making it a significant source of malicious traffic. At 100/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS62240

92.119.36.49 (330)45.147.244.27 (313)45.131.195.77 (305)98.159.37.212 (305)45.131.195.91 (305)View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 GDPR and Threat Intelligence

Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.

🔍 Check Any IP Address

Share this report: