34.75.118.13📋 Copy

INTELLIGENCE BRIEFING: 34.75.118.13/32

Classification: Moderate Risk Infrastructure Host

Risk Score: 65/100

---

Ownership & Infrastructure

IP 34.75.118.13 is registered to Google LLC (ASN 396982, netname GOOGL-2) within the 34.64.0.0/10 block. The IP operates as a single-service host with DNS resolution to `13.118.75.34.bc.googleusercontent.com`. Open services include SSH (port 22/TCP).

Geolocation Discrepancies

Geolocation data indicates Moncks Corner, SC, US, however validation shows significant inconsistencies:

• GeoPlausible: False
• RTT Violation: Observed 35ms vs minimum possible 139.2ms for 6958km distance
• 5 probe attempts confirmed validation failure
• IP appears to be hosted on infrastructure with location spoofing

Threat Intelligence

• Blacklist count: 0
• No known campaigns or attacker indicators
• Not a Tor exit node, proxy, or CDN
• Listed on 3 of 8 DNSBLs
• Abuse confidence score: Not applicable (infrastructure-based)

Network Environment

• Neighborhood (34.75.118.0/24): Mostly clean classification
• Abuse density: 0
• Active siblings: 0
• Threat siblings: 1 (potential correlated activity within subnet)

Temporal Analysis

• 21 historical observations recorded
• Recent activity observed: August 2026
• Ownership stability: No changes detected
• Not persistently malicious per historical pattern

Recommended Actions

1. Monitor: Increase logging verbosity and review recent activity from this IP

2. Block: Consider blocking at perimeter if activity aligns with threat indicators

- iptables: `iptables -A INPUT -s 34.75.118.13 -j DROP`

- Cloudflare WAF: Block with expression `ip.src eq 34.75.118.13`

3. Correlate: Investigate the 1 threat sibling within the /24 subnet for related activity

Assessment

This IP represents Google Cloud infrastructure with elevated risk scoring primarily driven by geolocation inconsistencies and DNSBL listings. The infrastructure type suggests legitimate hosting services, but the RTT violations indicate potential spoofing or misconfiguration. SOC teams should monitor for anomalous activity patterns while noting the infrastructure nature of the endpoint.

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