IP Threat Report
106.200.248.218
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
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 106.200.248.218 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ Defensive Recommendations
Block 106.200.248.218 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
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
106.200.248.218 has been assigned a threat score of 130/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
📊 Threat Analysis
IP address 106.200.248.218 has been traced to Lucknow, India, operating on the network of Bharti Airtel. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 5 days, this IP generated 812 malicious requests, averaging approximately 162.4 requests per day. With 101 flagged addresses, India represents a significant presence in our threat database. With a threat score of 130/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
Related Threats
Security Intelligence
💡 Server-Side Request Forgery (SSRF)
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
💡 Submarine Cable and Internet Exchange Points
Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.