IPDebrief

178.239.198.119

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 178.239.198.119

*Generated via IPDebrief tools: Profile, History, Relationships, Neighbors*

---

**1. Risk Profile**

---

**2. Observation History (Last 30 Days)**

---

**3. Network Relationships**

- 178.239.198.58 (Risk: 40/100)

- 178.239.198.65 (Risk: 55/100)

- 178.239.198.91 (Risk: 0/100)

- 178.239.198.126 (Risk: 25/100)

---

**4. Security Actions**

- Block 178.239.198.0/24 if high-risk neighbors are confirmed malicious.

- Monitor traffic to/from the subnet for unusual patterns.

- Investigate higher-risk neighbors (e.g., 178.239.198.58, 178.239.198.65) for potential关联.

- Ensure network segmentation to limit exposure from shared subnets.

---

**5. Summary**

The IP 178.239.198.119 is low risk and appears to be a legitimate VPN endpoint. However, its subnet has a moderate abuse density, with several neighbors showing elevated risk. SOC teams should monitor the subnet for suspicious activity and consider isolating high-risk neighbors to mitigate potential lateral movement or shared infrastructure threats.

*Tools: IPDebrief Profile, History, Relationships, Neighbors.*

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡¬πŸ‡§ United Kingdom
RegionEngland
CityLondon
TimezoneEurope/London
Latitude53.86
Longitude0.63

🏒 Ownership & Registration

OrganizationVPN Consumer London, United Kingdom
ASNAS42831
Network Nameβ€”
CIDR Blockβ€”
RIRRIPE
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
27%
23
routing
13%
11
services
19%
22
ownership
27%
23
reputation
22%
13
geolocation
27%
23
Overall22%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-14 19:28:22 UTC
Last Seen2026-06-07 08:09:18 UTC
Profile Built2026-06-07 08:11:53 UTC
Data FreshnessLive
Signal Types17
Total Observations17
πŸ” 17 signal types Β· 17 observations collected
This report is generated from 17+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API πŸ”§ Actions API πŸ“§ Enterprise Access

ℹ️ About This Report

All data shown is publicly available network metadata β€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.