IPDebrief

41.139.9.9

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

Date: 2026-06-10

---

**1. Core Profile**

- Primary Location: Miami, US (per geolocation data).

- Network Provider: Teledata-AS (Ghana, IL), conflicting with US geolocation.

---

**2. Observation History**

- DNSBL Listings: Identified in 3/8 DNSBLs (high-severity lists).

- Geolocation Shifts: Conflicting data (Ghanaian provider vs. US city).

- BGP Stability: Unstable route (routeChanges30d = 0, but route stability flagged as "false").

---

**3. Relationships**

- Linked to 41.139.8.0/21 (same subnet).

- No direct ties to known campaigns, organizations, or certificates.

---

**4. Neighborhood Analysis**

- 41.139.9.5: Risk Score 70 (High Risk).

- 41.139.9.208: Risk Score 55 (Moderate Risk).

---

**5. Recommended Actions**

1. Monitor Neighbors: Investigate 41.139.9.5 (high-risk neighbor) for potential关联.

2. Verify Geolocation Discrepancy: Confirm if the IP is legitimately in the US or if there is a misconfiguration.

3. Check DNSBL Listings: Validate why the IP is listed in 3 DNSBLs and assess if it’s a false positive.

4. Block High-Risk Neighbors: Consider firewall rules to restrict traffic from 41.139.9.5.

5. Review BGP Stability: Monitor route stability for 41.139.8.0/21 to detect potential network manipulation.

---

Conclusion: The IP exhibits moderate risk due to DNSBL listings and a high-risk neighbor. While no direct malicious activity is observed, the conflicting geolocation and network provider details warrant further investigation. SOC teams should prioritize monitoring the subnet and validating the IP’s legitimacy.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionUS-FL
CityMiami
TimezoneAmerica/New_York
Latitude5.55
Longitude-0.19

🏒 Ownership & Registration

OrganizationGregory Eid
ASNAS35091
Network Name41.139.8.0 - 41.139.15.255
CIDR Block41.139.8.0/21
RIRAFRINIC
CountryGH
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 PurposeWeb Server
Network TierUnknown β€” Insufficient routing data to classify
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
443httpstcpβ€”
Closed Ports22, 25, 80, 3389, 8080, 8443 (1 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
21%
22
reputation
0%
00
geolocation
13%
11
Overall12%66
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: GH, US

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-23 12:23:40 UTC
Last Seen2026-06-25 07:55:13 UTC
Profile Built2026-06-23 20:19:38 UTC
Data FreshnessLive
Signal Types16
Total Observations16
πŸ” 16 signal types Β· 16 observations collected
This report is generated from 16+ 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.