IP Intelligence Briefing: 35.253.148.96
*Generated via IPDebrief tools (profile, history, relationships, neighbors)*
---
**1. Core Profile**
- Risk Rating: Low Risk (25/100) | Provider/Authority/Threat Scores: 0/0/0
- Ownership: Owned by Google LLC (ASN 396982) | ARIN-registered | Geolocation: Council Bluffs, IA, US
- Network Role: Google Cloud Compute instance (infrastructure type: CloudCompute) | No open services | Firewalled
- Geolocation:
- Inferred via multi-signal inference (latitude 40.8248, longitude -96.6878)
- RTT anomaly: 78ms (expected ~144ms for 7219km distance)
- GeoPlausible: False (likely residential/ISP routing)
---
**2. Threat & Behavior**
- Threat Indicators: No malicious indicators, spam, or known attacker associations.
- DNS:
- PTR hostname: `96.148.253.35.bc.googleusercontent.com`
- SPF/DMArc: Validated (SPF: True, DMARC: True)
- Services: No open ports or TLS certificates detected.
- Network Activity:
- BGP prefix: `35.252.0.0/14` (Google Cloud)
- Route stability: Unstable (14-day route changes: 0)
---
**3. Historical Observations**
- Last 30 Days:
- 19 observations (19 signals) | 12 unique data sources
- Primary signal: Google Cloud ownership (confidence: 0.85)
- Geolocation consistency: 830km accuracy radius (Council Bluffs, IA)
- No spikes in threat scores or abnormal activity.
---
**4. Relationships**
- DNS Associations:
- Linked to `googleusercontent.com` subdomains (e.g., `96.148.253.35.bc.googleusercontent.com`)
- Network:
- Same subnet as `GOOGL-2` (Google Cloud network)
- No malicious peer IPs detected in /24 subnet.
---
**5. Neighborhood Analysis**
- Subnet: `35.253.148.96/24`
- Abuse Density: 0% (clean) | No active siblings or threat-related IPs in the subnet.
---
**6. Recommendations**
- SOC Action: No immediate mitigation required.
- Monitoring: Track for unexpected geolocation changes or service exposure.
- Context: Legitimate Google Cloud instance with no malicious behavior detected.
---
Conclusion: This IP is a low-risk, legitimate Google Cloud Compute instance with no malicious indicators. The geolocation anomaly suggests potential routing quirks but no evidence of compromise. No action required unless behavior changes.
*Data sourced from IPDebrief (https://ipdebrief.com)*.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Google LLC |
| ASN | AS396982 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| Country | β |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | 96.148.253.35.bc.googleusercontent.com |
| Forward Confirmed | Yes β FCrDNS verified |
| Forward Hostnames | 96.148.253.35.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 | Firewalled / No Services |
| Network Tier | Hosting β Infrastructure provider without advanced routing |
π 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 | 54% | 1 | 13 |
| services | 15% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 30% | 2 | 3 |
| Overall | 30% | 10 | 28 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-19 21:40:10 UTC |
| Last Seen | 2026-06-28 10:04:40 UTC |
| Profile Built | 2026-06-29 04:10:01 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 37 |
Full dossier details are available via our API.