# IP Intelligence Briefing: 161.35.13.174/32
## Executive Summary
IP address 161.35.13.174 is a DigitalOcean cloud computing host with a risk score of 25 (Low Risk). The IP shows minimal threat indicators, no open services, and is classified as infrastructure with a stable operational profile.
## Profile Overview
| Attribute | Value |
|---|---|
| **Risk Score** | 25 / 100 |
| **Reputation** | Low Risk |
| **Provider** | DigitalOcean, LLC (ASN 14061) |
| **Location** | North Bergen, NJ, US |
| **Infrastructure Type** | CloudCompute |
| **Network Role** | Cloud Infrastructure |
| **Open Ports** | None |
| **DNS Resolution** | No PTR/Forward Records |
## Threat Assessment
- Threat Indicators: None detected
- Known Attacker: No
- Spam Source: No
- Tor Exit Node: No
- Blacklist Count: 0
- DNSBL Listed: 1 of 8 lists
- Operator Score: 0.1304 (Minimal)
- Campaign Matches: 0
## Network Intelligence
- CIDR Block: 161.35.0.0/20
- BGP Prefix: 161.35.0.0/20
- Route Stability: Not stable
- Geolocation Consensus: Valid (2500km accuracy radius)
- Service Purpose: Firewalled / No Services
## Neighborhood Analysis
- Subnet: 161.35.13.174/24
- Abuse Density: 1 (Low)
- Classification: mostly_clean
- Active Siblings: 1
- Threat Siblings: 1
- Inherited Risk: 2
## Observation History
- Total Observations: 19
- Most Recent: 2026-06-14
- Infrastructure Detection: Consistent cloud provider identification
- Geolocation Signals: Multiple US location inferences (North Bergen NJ)
- Threat Persistence: 0 days observed
- Is Persistently Malicious: No
## Relationships
- Network Relationships: 15 entries all referencing DigitalOcean network (DIGITALOCEAN-161-35-0-0)
- External Links: None detected
- Associated Hostnames: None
- Certificates: None
## Recommended Actions
No specific security actions required based on current risk profile. The IP demonstrates standard cloud infrastructure behavior with no active threat indicators.
---
Assessment: This IP address represents legitimate cloud infrastructure with a clean security posture. The absence of open services, combined with low abuse density and minimal operator scoring, indicates normal operational behavior. No immediate defensive measures are warranted beyond standard monitoring practices.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| Country | β |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
π DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ 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 | 22% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 24% | 1 | 3 |
| geolocation | 31% | 2 | 3 |
| Overall | 20% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-12 03:42:54 UTC |
| Last Seen | 2026-06-27 20:52:48 UTC |
| Profile Built | 2026-06-28 14:58:13 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 24 |
Full dossier details are available via our API.