34.14.74.12📋 Copy

# IP Threat Intelligence Briefing

Target: 34.14.74.12/32 | Date: 2026-08-13

## Executive Summary

IP address 34.14.74.12 is a Google Cloud infrastructure endpoint operating on Google's 34.14.0.0/17 BGP prefix. Current risk assessment indicates moderate risk (score: 50) with no active threat indicators or blacklist matches. The IP is associated with legitimate cloud services but shows minimal abuse density within its subnet.

## Infrastructure Profile

## Risk Assessment

• Overall Risk Score: 50 (Moderate)
• Abuse Confidence: Not explicitly flagged
• Known Attacker: No
• Spam Source: No
• Tor Exit Node: No
• DNSBL Listings: 2 of 8 total lists

## Network Context

• Subnet: 34.14.74.12/24
• Neighbor IPs: 0 siblings in /24
• Abuse Density: 0 (clean)
• Threat Siblings: 0
• Route Stability: Unstable (route changes observed in 30-day window)

## Observation History

Recent signal observations (2026-08-13) indicate:

• Subnet classified as "clean" with 0 abuse density
• HTTP responses returning 302 redirects
• Pulsedive threat feeds show 4 pulses associated with the IP
• No evidence of persistent malicious activity or campaign correlation

## Related Entities

• DNS Hostname: 12.74.14.34.bc.googleusercontent.com
• Network Association: GOOGL-2 (Google network)
• Control Plane: BGP origin AS396982, RPKI state not validated

## Recommended Actions

Despite moderate risk scoring, the IP is part of Google Cloud infrastructure with no active threat indicators. The following defensive measures are available if blocking is required:

Firewall Rules:

```bash

iptables -A INPUT -s 34.14.74.12 -j DROP

nft add rule inet filter input ip saddr 34.14.74.12 drop

```

Cloud Platform Blocks:

• Cloudflare WAF: Block IP 34.14.74.12
• AWS WAF: Add address 34.14.74.12/32

Note: Action recommendations are probabilistic and should be combined with additional threat intelligence signals before implementation.

## Intelligence Summary

This IP represents a legitimate Google Cloud endpoint with moderate risk scoring primarily due to DNSBL presence. No active malicious indicators, campaigns, or threat actor associations were identified. The subnet shows no abuse density. SOC analysts may monitor but routine blocking is not recommended absent corroborating threat evidence.

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