173.230.140.10📋 Copy

IP Intelligence Briefing: 173.230.140.10

*Generated via IPDebrief Threat Intelligence Platform*

---

**1. IP Profile**

• Risk Assessment:

- Overall Risk Score: 0 (Low Risk)

- Provider Score: 0 (No malicious activity detected)

- Authority Score: 0 (No authoritative threat indicators)

- Stability Score: 0 (No observed instability)

• Ownership:

- ISP: Linode (ASN: AS63949)

- Geolocation: Atlanta, GA, US (latitude: 33.7485, longitude: -84.3871)

- Network Role: Cloud compute infrastructure (hosted by Linode)

• Threat Indicators:

- No malware, phishing, or exploit activity detected.

- No DNS-based threats or blacklisted domains.

• Network Services:

- No open ports, TLS certificates, or HTTP services identified.

---

**2. Observation History**

• Recent Activity (2026-06-12):

- Geolocation confirmed via 2 sources (2500km accuracy radius).

- Network operator score: 0.26 (Basic risk rating).

- No persistent threats or malicious campaigns linked.

• Geo-Validation:

- ICMP blocked, preventing full validation.

- Minimum possible RTT: 143.3ms (consistent with U.S. origin).

---

**3. Network Relationships**

• DNS Associations:

- Resolves to `173-230-140-10.ip.linodeusercontent.com` (Linode-managed).

• Subnet Relationships:

- Part of `173.230.128.0/19` (Linode infrastructure).

- No malicious subnets or correlated IPs detected.

---

**4. Neighborhood Analysis**

• Subnet: `173.230.140.10/24`
• Neighbor Risk:

- Total Siblings: 2 IPs

- Threat Siblings: 0

- Abuse Density: 0 (clean subnet)

- High-Risk Neighbor: `173.230.140.212` (risk score: 25/100).

---

**5. Actionable Insights**

• No Immediate Threat: The IP is part of Linode’s cloud infrastructure and shows no malicious activity.
• Monitor Subnet: While the subnet is clean, the single high-risk neighbor (`173.230.140.212`) warrants closer scrutiny.
• Geolocation Verification: ICMP blocking may obscure true location; consider alternative validation methods.
• Cloud Provider Context: Linode’s infrastructure is generally reputable, but isolate cloud instances if sensitive workloads are involved.

Recommendation: No firewall rules or blocking actions required. Continue monitoring for changes in subnet risk or new threat indicators.

---

*Generated by IPDebrief | © 2026 Jason Alberino*

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