35.190.134.179📋 Copy

IP INTELLIGENCE BRIEFING: 35.190.134.179/32

---

Executive Summary

IP 35.190.134.179 was classified as Moderate Risk (Risk Score: 50) with no active threat indicators. The address is hosted on Google Cloud infrastructure in North Charleston, South Carolina, USA, and demonstrates typical cloud compute behavior with HTTPS termination.

Infrastructure Profile

• Organization: Google LLC (GOOGLE-CLOUD)
• ASN: 396982
• CIDR Block: 35.184.0.0/13
• Infrastructure Type: Cloud Compute / Hosting
• Geolocation: United States, South Carolina, North Charleston

Observed Services

• Open Ports: TCP/443 (HTTPS)
• TLS Certificate: Issued to 35.190.134.179 with Kubernetes-related SANs (kubernetes, kubernetes.default, kubernetes.default.svc)
• HTTP Status: 403 Forbidden (observed in historical scans)
• DNS: PTR resolves to 179.134.190.35.bc.googleusercontent.com (googleusercontent.com)
• HTTP/2: Enabled

Threat Assessment

• Abuse Confidence: Not reported
• Known Campaigns: None
• Blacklist Count: 0
• Threat Feeds: Empty
• Control Plane: Listed on 2 DNSBLs out of 8 total checks
• Temporal: No persistent malicious activity detected (threat persistence: 0 days)

Neighborhood Context

The /24 subnet (35.190.134.0/24) shows zero active siblings and 0% abuse density. The neighborhood was classified as clean, with no high or medium-risk neighboring addresses.

Observation History

Twenty-three observations were recorded between August 6 and August 13, 2026. Signals included control plane metrics (operator score: 0.3478), HTTP fingerprinting, and TLS scanning. No correlation to known campaigns or correlated IPs was established.

Intelligence Notes

• Geo-validation flagged RTT anomaly (36ms observed vs 139.2ms minimum for 6958km distance)
• DNSSEC validated
• CAA records present
• HSTS and CSP headers not detected

Recommended Actions

The risk profile (Score: 50) generated standard firewall rules for iptables, nftables, nginx, pfSense, Cloudflare WAF, and AWS WAF. Given the Google Cloud hosting context and moderate risk score without active threat indicators, defensive blocking may be considered only in conjunction with additional context-specific signals.

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