IP Threat Report
106.202.40.18
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.202.40.18 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
⚙️ General Security
Add 106.202.40.18 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
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.202.40.18 has been assigned a threat score of 68/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
📊 Threat Analysis
Network traffic from 106.202.40.18, located in Dimāpur, India, operating on the network of Bharti Airtel, has been classified as malicious by our automated threat scoring engine. During its 5-day observation window, we recorded 146 hostile requests from this IP — roughly 29.2 per day on average. India currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 68/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
Related Threats
Security Intelligence
💡 Rate Limiting and Throttling Strategies
Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.
💡 IP Geolocation Accuracy Limitations
IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.