85.203.15.162
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 85.203.15.162
Date: 2026-06-03
---
**1. Risk Profile**
- Overall Risk: Moderate (Risk Score: 40)
- Subnet Risk: High Abuse (abuse density: 0.51)
- Network Classification: High abuse subnet (85.203.15.0/24)
- Ownership: Registered to "Jeroen van veen" (ASN 62240, RIPE) in Frankfurt, Germany.
---
**2. Threat Indicators**
- No Direct Threats: No malicious indicators, spam, or known attacker associations.
- Subnet Context: 47 IPs in the /24 subnet, with 24 flagged as threats (risk scores: 25–40).
- DNS/Services: No open ports, TLS certs, or DNS records linked to this IP.
---
**3. Network Behavior**
- Control Plane: BGP prefix 85.203.15.0/24, operator score "Minimal" (0.13).
- Subnet Stability: 8 active IPs, 24 threats detected in the subnet.
- Geolocation: Frankfurt, Germany (51.62°N, 8.04°E).
---
**4. Actionable Insights**
- Monitor Subnet: The 85.203.15.0/24 subnet has a high abuse density. Investigate neighboring IPs (e.g., 85.203.15.19, 85.203.15.72) for potential lateral movement or shared infrastructure.
- Verify Ownership: Confirm "Jeroen van veen" is a legitimate entity, as the IP lacks DNS or service context.
- Baseline Traffic: No active services or TLS certs detected. Ensure no unexpected traffic patterns emerge.
---
**5. Recommendations**
- Network Segmentation: Isolate this subnet if it hosts critical assets.
- Threat Intelligence Feeds: Cross-reference with DNSBL lists (1 listed) and monitor for abuse density changes.
- SOC Alerts: Flag IPs in this subnet for increased scrutiny due to high abuse classification.
---
*Generated by IPDebrief. Data reflects observations up to 2026-06-03.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Jeroen van veen |
| ASN | AS62240 |
| Network Name | — |
| CIDR Block | — |
| RIR | RIPE |
| 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 | 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
No certificate
Issued by —
N/A
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 29% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 17% | 1 | 2 |
| geolocation | 21% | 2 | 2 |
| Overall | 20% | 10 | 13 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:04:38 UTC |
| Last Seen | 2026-06-23 23:13:15 UTC |
| Profile Built | 2026-06-23 23:16:31 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 18 |
🔍 17 signal types · 18 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.
Full dossier details are available via our API.
ℹ️ 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.