34.39.140.140
# IP Intelligence Briefing: 34.39.140.140
## Executive Summary
IP address 34.39.140.140 is a Google Cloud infrastructure endpoint with low risk profile (risk score: 25). The IP operates as a web server in São Paulo, Brazil, and shows no active threat indicators. Monitoring recommendation: standard traffic observation.
## Infrastructure Profile
- Ownership: Google LLC (ASN 396982, netname: GOOGL-2)
- Classification: CloudCompute/Web Server infrastructure
- Geolocation: São Paulo, Brazil (BR)
- Network Block: 34.4.5.0/24 (ARIN)
- BGP Prefix: 34.39.128.0/17
- Infrastructure Type: Google Cloud Platform
## Network Services
- Open Ports: TCP/443 (HTTPS)
- DNS: 140.140.39.34.bc.googleusercontent.com (googleusercontent.com)
- TLS Configuration: TLS 1.3 with TLS_AES_128_GCM_SHA256 cipher
- Certificate: Valid certificate with subject CN=34.39.135.183
## Risk Assessment
- Overall Risk Score: 25 (Low Risk)
- Abuse Confidence: Not flagged as known attacker, spam source, or Tor exit node
- Blacklist Status: Listed on 1 of 8 DNSBLs
- Threat Indicators: None detected
- Campaign Activity: No associated campaigns observed
## Neighborhood Analysis
- Subnet: 34.39.140.140/24
- Abuse Density: 0 (mostly clean classification)
- Sibling IPs: No active neighbors identified
- Risk Distribution: Low risk environment
## Historical Observations
- Observation Count: 25 signals tracked
- Geolocation Consistency: São Paulo, Brazil (consistent across observations)
- Response Pattern: HTTP 401 status code observed
- Route Stability: Minor BGP changes (1 change in 30 days)
- Ownership Stability: No ownership changes recorded
## SOC Action Items
- Traffic Classification: Allow with standard logging for Google Cloud traffic
- Monitoring Level: Standard (no elevated monitoring required)
- Block Recommendation: Not required
- Additional Context: IP serves legitimate web hosting functions on Google infrastructure
## Intelligence Notes
This IP represents typical Google Cloud infrastructure with no malicious activity observed. The single DNSBL listing appears to be a routine operational flag rather than an abuse indicator. No immediate threat response actions recommended.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Google LLC |
| ASN | AS396982 |
| Network Name | GOOGL-2 |
| CIDR Block | 34.4.5.0/24 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | 140.140.39.34.bc.googleusercontent.com |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | 140.140.39.34.bc.googleusercontent.com |
🔐 DNS Hygiene
| Hygiene Score | 100% (Excellent) |
| SPF | 1/4 domains |
| DMARC | 1/4 domains |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Present |
| Domains Checked | 4 domains |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Tier 3 — Basic operator with some routing infrastructure |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 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 | 31% | 2 | 4 |
| routing | 32% | 2 | 3 |
| services | 32% | 2 | 3 |
| ownership | 34% | 3 | 4 |
| reputation | 28% | 1 | 3 |
| geolocation | 27% | 2 | 2 |
| Overall | 30% | 12 | 19 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-25 14:53:11 UTC |
| Last Seen | 2026-08-12 19:46:14 UTC |
| Profile Built | 2026-08-12 19:58:45 UTC |
| Data Freshness | Live |
| Signal Types | 27 |
| Total Observations | 35 |
Full dossier details are available via our API.