172.235.192.35📋 Copy

IP Intelligence Briefing: 172.235.192.35

Date: June 7, 2026

---

**1. Core Profile**

• Risk Score: Moderate (60/100)
• Provider: Linode (Cloud Hosting)
• Geolocation:

- Country: United States (US)

- Region: Osaka (possibly misattributed; verify)

- Coordinates: Latitude 39.83, Longitude -98.58 (approx. central US)

• Network Role: CloudCompute (Virtual Machine/Server)
• Services:

- Open ports: 443 (HTTPS), 22 (SSH), 8080 (HTTP-alt), 3389 (RDP)

- No TLS certificate detected

- No email security records (SPF/DKIM)

---

**2. Threat & Security Indicators**

• Threat Risk: Low

- No known malicious indicators (no malware, phishing, or exploit activity)

- DNSBL (DNS-based Blacklist) listing detected (1/8 total)

• Configuration Weaknesses:

- Missing DNSSEC validation

- No HTTP security headers (HSTS, CSP)

- SSH banner indicates OpenSSH 7.6p1 (patched, but no additional context)

---

**3. Network & Subnet Analysis**

• Subnet: 172.235.192.0/24 (Linode-managed)
• Neighbor Risk:

- Abuse Density: 0 (no malicious neighbors detected)

- Subnet Activity: No sibling IPs reported (may indicate sparse usage or data limitations)

• Routing:

- BGP ASN: 63949 (Linode)

- Route stability: Stable (no recent changes)

---

**4. Historical Observations**

• First Seen: May 31, 2026
• Consistency:

- Stable network role (CloudCompute)

- Geolocation data inconsistent (Osaka vs. US)

- No persistent malicious behavior (threat persistence: 0 days)

---

**5. Recommendations**

• Monitor:

- Open ports (SSH, RDP) for unauthorized access attempts.

- SSL/TLS configuration for 443 (HTTPS) to ensure encryption.

• Verify:

- Geolocation accuracy (Osaka, Japan vs. US). Potential misattribution.

- DNSSEC and email security records (SPF/DKIM) for domain validation.

• Action:

- Consider restricting non-essential ports (e.g., 8080, 3389) if not required.

- Validate Linode IP ownership to ensure no unauthorized use.

---

Conclusion:

This IP is associated with a Linode cloud server with moderate risk due to configuration gaps and inconsistent geolocation data. No direct malicious activity detected, but security best practices (e.g., TLS, DNSSEC) should be implemented to mitigate potential exploitation vectors. Monitor for anomalies in network behavior or new threat indicators.

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