# IP Intelligence Briefing: 213.230.92.230/32
Target: 213.230.92.230
Risk Assessment: Moderate Risk (Score: 55/100)
Classification: Infrastructure / No Active Services
Report Date: 2026-06-23
---
## Executive Summary
IP 213.230.92.230 is assigned to Uzbekistan's UZTELECOM (AS8193) infrastructure in Tashkent. The address exhibits moderate risk characteristics with no active services detected, but exists within a subnet showing elevated abuse density (30%). The IP was listed on three blacklists with high severity on 2026-06-18, suggesting historical abuse activity.
---
## Network Attribution
- ASN: 8193 (UZTELECOM - Uzbekistan)
- Registry: RIPE NCC (allocated 1997-02-03, stable 10,727 days)
- Location: Tashkent, Uzbekistan (41.26°N, 69.22°E)
- BGP Path: 6939 β 12389 β 28910 β 8193
- Route Stability: Stable (no changes in last 30 days)
- DNS Resolution: 230.64.uzpak.uz (forward confirmation not verified)
---
## Threat Profile
Current Status: Moderate Risk
- Risk Score: 55
- Abuse Confidence: Not quantified
- Known Attacker: No
- Tor Exit/Proxy: No
- Spam Source: No
Blacklist Status: Listed on 3 of 8 threat feeds (max severity: high)
- Observed on 2026-06-18 with high-severity listings
- No current active threat indicators
- No known campaigns or C2 associations
Service Activity: None detected
- No open ports, TLS certificates, or HTTP services
- Classified as "Firewalled / No Services"
- No honeypot hits or behavioral anomalies
---
## Neighborhood Analysis
Subnet: 213.230.92.0/24
Abuse Density: 30% (0.3)
Classification: Clean (but contextually elevated)
Risk Distribution Among Neighbors:
- High Risk: 6 IPs
- Medium Risk: 8 IPs
- Low Risk: 6 IPs
Notable High-Risk Neighbors:
- 213.230.92.22 (Risk: 80)
- 213.230.92.42 (Risk: 80)
- 213.230.92.49 (Risk: 80)
- 213.230.92.92 (Risk: 80)
- 213.230.92.115 (Risk: 80)
- 213.230.92.116 (Risk: 80)
Observation: The target IP's subnet shows mixed risk levels with 6 high-risk siblings, suggesting potential shared infrastructure abuse. Target IP 213.230.92.230 has 1 threat sibling identified within the /24.
---
## Historical Trends
Observation Count: 23 signals over monitoring period
- Consistent ASN: UZTELECOM (AS8193) across all observations
- Route Stability: No BGP prefix changes in 30-day window
- Ownership: No ownership changes detected
- Blacklist Activity: Significant listing activity on 2026-06-18
Trend Assessment: IP shows stable network infrastructure characteristics with no escalation or de-escalation of threat signals. Blacklist activity is the primary concern indicator.
---
## Recommendations for SOC
Monitor:
1. Neighborhood IPs: Consider blocking or monitoring 213.230.92.22, 213.230.92.42, 213.230.92.49, 213.230.92.92, 213.230.92.115, 213.230.92.116 due to high-risk scores
2. Blacklist Updates: Review current blacklist status (3/8 lists) and monitor for changes
3. Traffic Patterns: Investigate any traffic from subnet 213.230.92.0/24 if not already blocked
Actions:
- Implement firewall rules for subnet 213.230.92.0/24 if threat level warrants
- Monitor for lateral movement attempts from related high-risk neighbors
- Update threat intel feeds with current blacklist information
Risk Level: Monitor / Low-Medium Priority
Confidence: High (based on 23 historical observations)
---
Source: IPDebrief Threat Intelligence Platform
Data Freshness: Current as of 2026-06-23
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | AS8193-MNT |
| ASN | AS8193 |
| Network Name | β |
| CIDR Block | 213.230.92.0/24 |
| RIR | RIPE |
| Country | β |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | 230.64.uzpak.uz |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 230.64.uzpak.uz |
π 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
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 36% | 2 | 4 |
| routing | 40% | 2 | 3 |
| services | 15% | 2 | 2 |
| ownership | 29% | 3 | 4 |
| reputation | 32% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 29% | 12 | 18 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-07 23:04:11 UTC |
| Last Seen | 2026-06-23 07:29:09 UTC |
| Profile Built | 2026-06-23 07:47:15 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 31 |
Full dossier details are available via our API.