IPDebrief

84.54.73.4

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing: 84.54.73.4

## Executive Summary

IP address 84.54.73.4 is classified as High Risk (Risk Score: 80/100) with elevated threat indicators requiring immediate attention. The IP belongs to UZTELECOM (ASN 8193, Role of Uzbektelecom JSC) and is geolocated to Tashkent, Uzbekistan. Despite showing no open services, the IP demonstrates significant abuse indicators and should be blocked at perimeter infrastructure.

## Risk Assessment

Risk Score: 80/100 (High Risk)

Threat Indicators:

Ownership & Registration:

## Network Context

Neighborhood Analysis (84.54.73.0/24):

The subnet shows concentrated risk with multiple high-scoring neighbors. This IP shares network infrastructure with 6 other high-risk addresses in the /24 block.

DNS Relationships:

## Behavioral Observations

Observation History: 12 signals recorded

Services: No open ports or HTTP services detected. The IP appears firewalled or configured for non-public-facing services.

## Recommended Actions

Immediate Actions Required:

1. Block at Perimeter: Implement firewall rules to drop traffic from 84.54.73.4/32

2. Increase Logging: Enable enhanced logging verbosity for this IP to capture any attempted connections

3. Monitor Related IPs: Review activity from 6 other high-risk neighbors in the same /24 subnet

Firewall Rules:

## Intelligence Narrative

This IP address presents elevated risk despite lacking active service exposure. The high-risk classification stems primarily from DNSBL listings (5 of 8 feeds) and neighborhood context within a subnet showing 35.3% abuse density. The UZTELECOM network has a reputation for hosting legitimate infrastructure, but this specific /24 block contains multiple high-risk addresses. The DNS association with intal.uz and PTR record 4.73.intal.uz suggests the IP may have been used for email services or similar applications at some point.

Recommendation: Treat as malicious traffic source. Block at perimeter firewall and implement enhanced logging. Given the subnet-wide risk concentration, consider evaluating the entire 84.54.73.0/24 block for traffic filtering based on organizational policy.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-MA
CityBoston
TimezoneAmerica/New_York
Latitude42.36
Longitude-71.06

🏒 Ownership & Registration

OrganizationRole of Uzbektelecom JSC
ASNAS8193
Network NameUZTELECOM
CIDR Block84.54.73.0/24
RIRRIPE
CountryUZ
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR4.73.intal.uz
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnames4.73.intal.uz

πŸ” 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
45%
23
routing
22%
11
services
31%
22
ownership
45%
23
reputation
22%
12
geolocation
0%
00
Overall27%811
Coverage: 3/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-07-29 22:50:53 UTC
Last Seen2026-07-31 19:33:26 UTC
Profile Built2026-07-31 13:33:10 UTC
Data FreshnessLive
Signal Types19
Total Observations21
πŸ” 19 signal types Β· 21 observations collected
This report is generated from 19+ 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.