92.118.39.95
IP Intelligence Briefing: 92.118.39.95
Date: 2026-06-12
---
**1. Core Profile**
- Risk Rating: Low Risk (Risk Score: 0 / Provider Score: 0 / Authority Score: 0)
- Ownership:
- ASN: Unassigned
- Organization: "Abuse contact role object" (netname: DMZHOST)
- RIR: RIPE NCC
- Geolocation: Netherlands (NL), but DNS records suggest Dallas, Texas (potential data inconsistency).
- Threat Indicators: Clean (no malicious indicators, blacklists, or campaigns linked).
- Network Role: Firewalled / No Services (no open ports, TLS, or HTTP activity detected).
---
**2. Observation History**
- Recent Activity (Last 30 Days):
- 12 observations, primarily DNS-related (PTR lookups, geolocation).
- 8 distinct threat feeds listed, but no confirmed malicious activity.
- Geolocation data shows mixed results: Netherlands (NL) vs. Dallas, Texas.
- No persistent threats or honeypot activity detected.
---
**3. Network Relationships**
- Linked Entities:
- Same network: "DMZHOST" (repeated in relationships).
- Subnet: 92.118.39.0/24 (40 total IPs, 17 high-risk neighbors).
- Key neighbors with elevated risk:
- 92.118.39.62 (Risk: 80), 92.118.39.72 (Risk: 80), 92.118.39.194 (Risk: 40).
- Subnet abuse density: 42.5% (17 high-risk IPs).
---
**4. Threat Context**
- No Direct Threats: 92.118.39.95 itself shows no malicious activity.
- Subnet Risk: While the IP is clean, its subnet contains high-risk IPs (e.g., 92.118.39.62).
- Geolocation Anomalies: Conflicting location data (Netherlands vs. Dallas) may indicate misconfigured DNS or spoofing.
---
**5. Recommendations**
- Monitor Subnet: Investigate high-risk neighbors (e.g., 92.118.39.62, 92.118.39.72) for potential lateral movement or shared infrastructure risks.
- Verify Geolocation: Cross-check DNS records and geolocation data for inconsistencies.
- Firewall Rules: Ensure strict access controls for the subnet, given its mixed risk profile.
- Threat Feeds: Continuously monitor the 8 listed threat feeds for updates.
Conclusion: 92.118.39.95 is a low-risk host, but its subnet contains notable threats. SOC teams should prioritize subnet-level monitoring and validate geolocation anomalies.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Abuse contact role object |
| ASN | AS47890 |
| Network Name | DMZHOST |
| CIDR Block | 92.118.39.0/24 |
| RIR | RIPE |
| Country | NL |
| 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 | |||
| 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 | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 6% | 3 | 4 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-30 11:00:01 UTC |
| Last Seen | 2026-06-13 03:46:13 UTC |
| Profile Built | 2026-06-12 03:52:19 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 16 |
Full dossier details are available via our API.