# IP Intelligence Briefing: 136.114.246.34/32
## Executive Summary
IP address 136.114.246.34 is a Google Cloud infrastructure endpoint with a moderate risk classification (Score: 50). The IP shows no active threat indicators, operates within a clean subnet, and resolves to legitimate Google services. No blocking action is recommended at this time.
## Ownership & Infrastructure
- Organization: Google LLC (ASN 396982)
- Network Name: GOOGL-46
- CIDR Block: 136.112.0.0/12
- RIR: ARIN
- Geolocation: Council Bluffs, Iowa, US (Geo validation plausible)
## Network Classification
- Infrastructure Type: Cloud provider (Google Cloud)
- Services Status: Firewalled / No open ports detected
- Anycast: No
- Tor Exit: No
- Known Attacker: No
- Spam Source: No
## DNS Resolution
- PTR Hostname: 34.246.114.136.bc.googleusercontent.com
- Forward Resolution: Confirmed
- Domain: googleusercontent.com
- DNSSEC: Valid
- CAA Records: Present
## Threat Intelligence
- Abuse Confidence Score: Not available
- Blacklist Count: 0
- Known Campaigns: None
- Threat Persistence: 0 days (not persistently malicious)
- Threat Observation Count: 0
## Control Plane Analysis
- BGP Prefix: 136.114.0.0/16
- Route Stability: Not stable
- MOAS: No
- DNSBL Listed: 2 of 8 total lists
- Operator Score: 0.3478 (Basic)
## Neighborhood Assessment
- Subnet: 136.114.246.34/24
- Abuse Density: 0 (Clean)
- Threat Siblings: 0
- Active Siblings: 1
- Classification: Clean
## Observation History
19 observations recorded as of July 31, 2026:
- Geolocation: US (confidence 0.35), coordinates 39.83, -98.58
- ICMP: Blocked (unable to validate)
- Services: No open ports detected
- Ownership: Stable (0 ownership changes)
- Threat Activity: None observed
## Relationships
- DNS Associations: 34.246.114.136.bc.googleusercontent.com
- Network Affiliations: GOOGL-46
- No malicious entity links detected
## Recommended Actions
NO BLOCKING RECOMMENDED. The IP is legitimate Google Cloud infrastructure with no active threat indicators. The moderate risk classification appears to be due to DNSBL listings rather than malicious activity. Standard cloud infrastructure handling applies.
---
*Intel generated via IPDebrief automated analysis*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Google LLC |
| ASN | AS396982 |
| Network Name | GOOGL-46 |
| CIDR Block | 136.112.0.0/12 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | 34.246.114.136.bc.googleusercontent.com |
| Forward Confirmed | Yes β FCrDNS verified |
| Forward Hostnames | 34.246.114.136.bc.googleusercontent.com |
π DNS Hygiene
| Hygiene Score | 100% (Excellent) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Present |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Single-Service Host |
| Network Tier | Tier 3 β Basic operator with some routing infrastructure |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 22 | ssh | tcp | |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | β |
| HTTP Title | β |
| SSH Version | SSH-2.0-OpenSSH_10.0 |
π TLS Certificate
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 33% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 35% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 15% | 1 | 2 |
| geolocation | 27% | 2 | 3 |
| Overall | 25% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-07-30 04:58:20 UTC |
| Last Seen | 2026-08-13 00:21:42 UTC |
| Profile Built | 2026-08-13 00:29:12 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 21 |
Full dossier details are available via our API.