IPDebrief

84.54.71.38

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

Date: 2026-06-13

---

**Core Profile**

---

**Observation History**

- Detected in Tashkent, Uzbekistan (Alienvault-OTX) with a threat pulse (score 1).

- Geolocated to Boston, MA, US (MaxMind).

- DNSSEC validity confirmed, but operator risk score is 0.13 (Minimal).

---

**Network Relationships**

- Subnet 84.54.71.0/24 (UZTELECOM).

- No direct connections to known malicious organizations or domains.

---

**Subnet Neighborhood**

- 84.54.71.34, 84.54.71.69, 84.54.71.142, 84.54.71.145, 84.54.71.149 (all risk score 80).

---

**Key Findings**

1. Geolocation Discrepancy: IP is registered to Uzbektelecom but geolocated in the US. Possible routing anomalies or spoofing.

2. High-Risk Subnet: 71.4% of neighboring IPs in 84.54.71.0/24 are high risk, suggesting potential for coordinated malicious activity.

3. Residential Endpoint: Likely a regular user IP, but residential networks can be exploited for botnets or C2.

---

**Recommended Actions**

---

Tools Used: ipdebrief_profile, ipdebrief_history, ipdebrief_relationships, ipdebrief_neighbors.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-MA
CityBoston
TimezoneAmerica/New_York
Latitude41.26
Longitude69.22

🏒 Ownership & Registration

OrganizationRole of Uzbektelecom JSC
ASNAS8193
Network NameUZTELECOM
CIDR Block84.54.71.0/24
RIRRIPE
CountryUZ
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

InfrastructureResidential
Service PurposeResidential Endpoint
Network TierEnd-User β€” Residential ISP endpoint
Residential

πŸ”Œ 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
25%
11
routing
25%
11
services
25%
11
ownership
25%
12
reputation
0%
00
geolocation
0%
00
Overall16%45
Coverage: 4/6 dimensions Β· Data sufficiency: partial
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: UZ, US

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-06-06 13:36:36 UTC
Last Seen2026-06-13 14:34:51 UTC
Profile Built2026-06-13 14:47:49 UTC
Data FreshnessLive
Signal Types18
Total Observations18
πŸ” 18 signal types Β· 18 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.