IPDebrief

41.84.225.2

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.

# INTELLIGENCE BRIEFING: 41.84.225.2

Classification: MODERATE RISK | Date: [Current Date] | Analyst: IPDebrief SOC

---

## EXECUTIVE SUMMARY

IP 41.84.225.2 presents a moderate risk profile (score: 55) with no active malicious indicators currently detected. The address is associated with ASN 19711 (Musa Tsela) and located within the 41.84.225.0/24 subnet. While DNSBL listings indicate historical reputation concerns, the IP currently shows no open services, no Tor exit node activity, and no active threat signatures.

---

## OWNERSHIP & INFRASTRUCTURE

---

## THREAT PROFILE

MetricValue
Risk Score55 (Moderate)
Blacklist Count0
DNSBL Listings3 of 8 total lists
Known AttackerNo
Spam SourceNo
Tor Exit NodeNo
Open PortsNone detected
Active ServicesNone

Threat Indicators: No active threat feeds or campaign correlations identified.

---

## NETWORK BEHAVIOR & SIGNALS

Recent Signal History (9 observations):

---

## NETWORK CONTEXT

Same Network Analysis (41.84.225.0/24)

Neighboring IP Analysis

---

## NETWORK TRACEROUTE

---

## RECOMMENDED ACTIONS

Firewall Rules

```bash

# Allow basic connectivity (no active blocking required)

# Monitor for service emergence

```

SOC Monitoring Priorities

1. Service Scanning: IP currently shows no open servicesβ€”monitor for port opening

2. Geolocation Discrepancy: Investigate US vs SZ registration mismatch

3. DNSBL Activity: Review 3 blacklist listings for context

4. Route Stability: Track BGP prefix changes for potential infrastructure shifts

Risk Assessment

---

## CONCLUSION

IP 41.84.225.2 represents a moderate-risk infrastructure address with no active malicious indicators. The network is currently quiet (no open services), but the combination of unstable routing, DNSBL listings, and geolocation inconsistencies warrants continued observation. SOC teams should monitor for service emergence and investigate the US/Swaziland registration discrepancy during routine intelligence cycles.

Classification: DEFENSIVE INTELLIGENCE | Status: MONITOR

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-FL
CityMiami
TimezoneAmerica/New_York
Latitude25.77
Longitude-80.19

🏒 Ownership & Registration

OrganizationMusa Tsela
ASNAS19711
Network Name41.84.225.0 - 41.84.225.255
CIDR Block41.84.225.0/24
RIRAFRINIC
CountrySZ
Abuse Contactβ€”

🌐 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

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
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
0%
00
routing
0%
00
services
0%
00
ownership
25%
11
reputation
0%
00
geolocation
0%
00
Overall4%11
Coverage: 1/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-07-24 08:18:48 UTC
Last Seen2026-07-29 22:43:38 UTC
Profile Built2026-07-29 22:49:35 UTC
Data FreshnessLive
Signal Types11
Total Observations11
πŸ” 11 signal types Β· 11 observations collected
This report is generated from 11+ 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.