193.233.246.108
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: 193.233.246.108
Date: 2026-06-11
1. Core Profile
- Risk Score: 25 (Low Risk)
- Ownership: Registered to Aeza-Network-Moscow (ASN 216246) under RIPE.
- Geolocation: Initially reported in Moscow, Russia (55.7487°N, 37.6187°E) but recently resolved to Amsterdam, Netherlands (NL).
- Threat Indicators: No malicious activity detected (no malware, phishing, or exploit campaigns).
- Network Role: Firewalled / No Services; no open ports or TLS services identified.
- Control Plane: DNSSEC validated, but listed in 1/8 DNSBLs (moderate spam risk).
2. Observation History
- Geolocation Shift: Moved from Moscow, Russia to Amsterdam, Netherlands.
- DNSBL Listing: Detected in one of eight DNSBLs (high severity).
- Operator Score: Minimal risk (0.1304).
- Stability: No recent route changes; BGP stability score indicates route instability.
3. Relationships
- Linked to Aeza-Network-Moscow (same network).
- No connections to known malicious entities, campaigns, or subnets.
4. Neighborhood Analysis
- Subnet: 193.233.246.0/24.
- Abuse Density: 0% (clean subnet).
- Neighbors: No active or threat-related sibling IPs identified.
5. Recommendations
- Monitor DNSBL Status: Verify the IP’s listing in DNSBLs and investigate potential spam activity.
- Geolocation Discrepancy: Investigate the shift from Russia to Netherlands; confirm if this reflects legitimate network reconfiguration or potential spoofing.
- Route Stability: Monitor BGP updates for this subnet due to reported route instability.
- No Immediate Action Required: No active threats detected, but ongoing surveillance is advised.
Conclusion:
This IP is currently low risk with no direct malicious indicators. However, its DNSBL listing and geolocation anomalies warrant further investigation to rule out spoofing or misconfigured infrastructure. SOC teams should prioritize monitoring DNSBL status and BGP stability for this subnet.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | mnt-ru-am-1 |
| ASN | AS216246 |
| Network Name | Aeza-Network-Moscow |
| CIDR Block | 193.233.246.0/24 |
| RIR | RIPE |
| Country | RU |
| 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
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 | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 13% | 6 | 7 |
Coverage: 5/6 dimensions · Data sufficiency: partial
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-27 13:17:16 UTC |
| Last Seen | 2026-06-11 10:13:55 UTC |
| Profile Built | 2026-06-11 10:20:59 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 17 |
🔍 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.
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.