194.32.120.195
IP Intelligence Briefing: 194.32.120.195
*Generated via IPDebrief Analysis*
---
**Key Findings**
1. Risk Profile:
- Overall Risk: Moderate (Score: 40).
- Subnet Abuse Density: High (0.65–0.67), classified as *high_abuse*.
- Neighbors: 26 IPs in the 194.32.120.0/24 subnet, with 25 IPs scoring moderate risk (40) and 1 IP (194.32.120.46) showing low risk (0).
2. Ownership & Geolocation:
- Provider: ASN 42831 ("VPN Consumer London, United Kingdom").
- Geolocation: Confirmed as Netherlands (NL), but regional/city data shows London, England. This discrepancy may indicate misconfigured geolocation or a hybrid network.
3. Threat Indicators:
- No direct malicious indicators (no blacklists, campaigns, or DNS anomalies).
- Subnet Risk: High abuse density suggests potential for lateral movement or shared infrastructure risks.
4. Network Behavior:
- Firewalled: No open ports or services detected.
- Traffic Patterns: Scans detected (ports scanned in May 2026), but no active services or banners.
5. Historical Trends:
- Observed since May 29, 2026.
- Subnet abuse density has remained consistently high, with no decline in risk signals.
---
**Actionable Insights**
- Monitor Subnet: The 194.32.120.0/24 subnet has a high abuse density. Investigate neighbors with elevated risk scores (e.g., 194.32.120.36, 194.32.120.39) for potential correlation with malicious activity.
- Verify Geolocation: Discrepancy between country (NL) and city (London, England) warrants further validation. Could indicate misconfigured routing or a hybrid network.
- Network Segmentation: Consider isolating this subnet if it hosts sensitive assets, given the high abuse density.
- Threat Intelligence: No direct threats to this IP, but subnet-level risks suggest proactive monitoring for anomalies.
---
**Recommended Actions**
- SOC Team: Correlate subnet activity with internal logs for signs of lateral movement or compromised hosts.
- Firewall Rules: Block traffic from high-risk neighbors (e.g., 194.32.120.46) if they are not critical assets.
- Geolocation Verification: Cross-check with other sources (e.g., WHOIS, DNS) to resolve the NL vs. London inconsistency.
---
*Data sourced from IPDebrief. Use with operational security considerations.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | VPN Consumer London, United Kingdom |
| ASN | AS42831 |
| Network Name | LONDON-GB-194-32-120-0 |
| CIDR Block | 194.32.120.0/24 |
| RIR | RIPE |
| Country | GB |
| 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 | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 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 | 38% | 2 | 5 |
| routing | 19% | 1 | 2 |
| services | 19% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 26% | 1 | 4 |
| geolocation | 27% | 2 | 2 |
| Overall | 26% | 10 | 18 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-13 12:12:34 UTC |
| Last Seen | 2026-06-06 20:47:29 UTC |
| Profile Built | 2026-06-06 20:49:58 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 17 |
Full dossier details are available via our API.