IPDebrief

213.230.92.42

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

Date: June 10, 2026

---

**1. Risk Profile**

---

**2. Observations (Last 30 Days)**

- High-risk listings (5/8) detected on June 10, 2026.

- No significant changes in geolocation or network behavior.

---

**3. Relationships**

- Subnet: 213.230.92.0/24 (UZTELECOM).

- Linked to hostname 42.64.uzpak.uz (DNS PTR record).

- 4 high-risk IPs (80/100) and 11 low-risk IPs.

- Notable high-risk neighbors: 213.230.92.22, 213.230.92.49, 213.230.92.92, 213.230.92.116.

---

**4. Recommended Actions**

- `iptables -A INPUT -s 213.230.92.42 -j DROP`

- `nft add rule inet filter input ip saddr 213.230.92.42 drop`

- Increase logging verbosity for traffic from this IP.

- Investigate DNS associations with 42.64.uzpak.uz.

- Monitor high-risk neighbors in 213.230.92.0/24 for lateral movement.

---

**5. Summary**

This IP is part of a UZTELECOM subnet with no direct malicious activity but exhibits moderate risk via DNSBL listings and high-risk neighbors. While not a confirmed attacker, its high risk score and network context warrant closer monitoring. Block the IP in defensive systems and validate DNS relationships for potential indirect threats.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Ώ UZ
RegionTashkent
CityTashkent
Timezoneβ€”
Latitude41.26
Longitude69.22

🏒 Ownership & Registration

OrganizationAS8193-MNT
ASNAS8193
Network NameUZTELECOM
CIDR Block213.230.92.0/24
RIRRIPE
CountryUZ
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR42.64.uzpak.uz
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnames42.64.uzpak.uz

πŸ” 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
13%
11
routing
13%
11
services
13%
11
ownership
30%
23
reputation
0%
00
geolocation
13%
11
Overall14%67
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-25 06:42:03 UTC
Last Seen2026-06-10 21:03:26 UTC
Profile Built2026-06-10 21:55:09 UTC
Data FreshnessLive
Signal Types18
Total Observations22
πŸ” 18 signal types Β· 22 observations collected
This report is generated from 18+ 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.