IPDebrief

193.32.162.146

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: 193.32.162.146

Date: 2026-06-17

---

**1. Core Profile**

---

**2. Observation History**

- Risk Trends: Mixed signals (0–80 risk scores). Most observations (60%) show low/moderate risk.

- Geolocation Consistency: Stable Netherlands location inferred via DNSSEC and RTT data.

- Subnet Abuse Density: 0.47 (47% of subnet IPs flagged as abusive).

- Threat Persistence: No persistent malicious activity detected.

---

**3. Network Relationships**

- DMZHOST (repeated in relationships, likely a shared network segment).

- Subnet: 193.32.162.0/24, classified as "mixed" (abuse density 47%).

- High-Risk Neighbors: 4 IPs in subnet with >80 risk scores (e.g., 193.32.162.71, 193.32.162.197).

- Inherited Risk: 18% of subnet flagged for abuse.

---

**4. Neighborhood Analysis**

- Total IPs: 256 (24-bit subnet).

- Active IPs: 22 (8.5% of subnet).

- Risk Distribution:

- High Risk (40–80): 4 IPs.

- Medium Risk (25–39): 13 IPs.

- Low Risk (0–24): 5 IPs.

- 193.32.162.71 (80 risk score) and 193.32.162.197 (80 risk score): High-risk peers.

- 193.32.162.200 (0 risk score): Low-risk, potentially benign.

---

**5. Recommendations**

1. Monitor Subnet Activity: High-risk neighbors in the same subnet may indicate a compromised network segment.

2. Investigate DMZHOST Relationships: Confirm if DMZHOST is a legitimate internal network or linked to malicious infrastructure.

3. Enhance Subnet Security: Consider isolating or segmenting the 193.32.162.0/24 subnet to mitigate inherited risk.

4. Check for BGP Anomalies: The unstable BGP route (193.32.162.0/24) could indicate route hijacking or misconfiguration.

---

Note: The IP itself shows no direct malicious activity, but its subnet’s abuse density and high-risk neighbors warrant further investigation.

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

🌍 Geolocation

CountryπŸ‡³πŸ‡± Netherlands
Regionβ€”
Cityβ€”
TimezoneEurope/Amsterdam
Latitude52.13
Longitude5.29

🏒 Ownership & Registration

OrganizationABUSE DEP
ASNAS47890
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
45%
23
routing
13%
11
services
18%
22
ownership
20%
23
reputation
17%
12
geolocation
21%
22
Overall22%1013
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:04 UTC
Last Seen2026-06-23 03:01:00 UTC
Profile Built2026-06-23 03:10:07 UTC
Data FreshnessLive
Signal Types16
Total Observations19
πŸ” 16 signal types Β· 19 observations collected
This report is generated from 16+ 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.