34.26.123.45📋 Copy

## Intelligence Briefing: IP 34.26.123.45

Classification: Moderate Risk – Google Cloud Infrastructure

Overview

IP 34.26.123.45 is registered to Google LLC (ASN 396982, netname GOOGL-2) within the 34.4.5.0/24 block. The IP resolves to North Charleston, SC (US) and is associated with Google Cloud infrastructure. Current risk score is 50 (Moderate Risk).

Network Characteristics

• Infrastructure Type: Google Cloud Platform
• Service Status: Firewalled / No Services Detected
• DNS Resolution: 45.123.26.34.bc.googleusercontent.com (googleusercontent.com)
• Email Authentication: SPF and DMARC records present
• Anycast: No
• Tor Exit Node: No

Threat Assessment

• Blacklist Status: Not listed (0 blacklists)
• Threat Indicators: None detected
• Known Attacker: No
• Spam Source: No
• Abuse Confidence Score: Not applicable
• Risk Breakdown: Provider and authority scores are 0; stability data unavailable

Behavioral History

Observation history contains 14 signals as of August 2026. Key findings:

• Organization registration (Google LLC) consistently confirmed with 90-95% confidence
• Geolocation data shows US registration with varying confidence levels
• Operator score: 0.3478 (Basic classification)
• No persistent malicious behavior observed
• No campaign correlations identified

Neighborhood Analysis

Subnet 34.26.123.0/24 analysis:

• Neighbor count: 0
• Abuse density: 0
• No sibling IPs detected in the neighborhood
• Risk distribution: No high, medium, or low-risk neighbors identified

Security Recommendations

Based on the IP's profile (Google Cloud infrastructure with no active services and no threat indicators):

• Block: Not recommended
• Rate Limit: Not required
• Allow: Acceptable with standard monitoring

Intelligence Summary

This IP represents legitimate Google Cloud infrastructure with no active services exposed and no threat indicators. The moderate risk score (50) reflects the Google Cloud classification rather than malicious activity. No firewall blocking is recommended, but standard traffic monitoring should apply. The absence of open ports, threat indicators, and blacklist entries supports benign operational classification.

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