115.190.220.166📋 Copy

IP Intelligence Briefing: 115.190.220.166

Date: 2026-06-17

---

**1. Core Profile**

• Risk Score: 80 (High Risk)
• Ownership:

- ASN: 137718 (IRT-VOLCANO-ENGINE-CN)

- Network: VOLCANO-ENGINE

- RIR: APNIC

• Geolocation:

- Country: China (CN)

- Latitude/Longitude: Unknown

- Accuracy Radius: 2500 km

• Threat Indicators:

- No direct malicious indicators (no spam, attacks, or known campaigns).

- 5 DNSBL listings (e.g., Spamhaus, OpenBL) with low confidence.

• Network Role:

- Firewalled system with no open ports or services.

- Likely infrastructure or hosting node.

---

**2. Observation History**

• Recent Activity (Last 30 Days):

- 18 total observations, 13 with low confidence.

- DNSBL Listings: 5 entries (e.g., Spamhaus, OpenBL) with "high" severity.

- Threat Confidence: Minimal (0.22–0.30).

- Stability: No route stability (fluctuating BGP state).

• Key Trends:

- Persistent DNSBL flags but no recent scans or threats.

- Geolocation plausibility: False (distance/RTT data missing).

---

**3. Relationships**

• Linked Entities:

- Same network: VOLCANO-ENGINE (ASN 137718).

- No direct links to domains, certificates, or organizations.

• Network Context:

- Part of a /15 CIDR block (115.190.0.0/15).

- No sibling IPs found in the /24 subnet.

---

**4. Neighborhood Analysis**

• Subnet: 115.190.220.166/24
• Abuse Density: 1 (low risk).
• Neighbors:

- 0 active IPs in the subnet (no siblings detected).

- Potential isolation or misconfigured subnet.

---

**5. Control Plane & DNS**

• DNSSEC: Validated (no errors).
• DNSBL Status:

- Listed in 5/8 DNSBLs (e.g., Spamhaus, OpenBL).

• BGP:

- Route stability: Unstable (no RPKI validation).

- AS Path: Not available.

---

**6. Recommendations**

• Monitor DNSBL Listings: Investigate why this IP is flagged by security feeds.
• Verify Network Configuration: Ensure the subnet (115.190.220.0/24) is properly configured and isolated.
• Check for Compromised Neighbors: Despite no siblings, cross-reference with broader network activity.
• Block DNSBL Entries: Add to firewall rules (e.g., Cloudflare WAF, AWS WAF) to mitigate potential spam or abuse.

Next Steps:

• Validate DNSSEC and BGP configurations.
• Correlate with internal logs for unusual traffic patterns.
• Monitor for changes in DNSBL status or network behavior.

---

End of Briefing

*Generated via IPDebrief intelligence tools. Use for defensive posture adjustment and incident response planning.*

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.