IPDebrief

102.110.7.34

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

Date: 2026-06-06

---

**1. Core Profile**

---

**2. Network Behavior**

- Route instability detected (1 change in 30 days).

- AS Path: `204092 34019 47160 62000 6204 37693`.

- RPKI state: Unverified.

- Part of 102.110.0.0/16 (Afrinic registry).

- Subnet abuse density: 1/10 (mostly clean).

- Neighbors:

- 102.110.7.41 (Risk: 70), 102.110.7.160 (Risk: 70).

- Both neighbors show elevated risk scores.

---

**3. Historical Observations**

- Minimal risk score (0.2174) over 30 days.

- No persistent malicious activity (threat persistence days: 0).

- Geolocation data consistent (Tunisia).

- No active domains, email auth (SPF/DKIM), or open ports.

---

**4. Threat & Risk Context**

---

**5. Recommendations**

1. Monitor Neighbors: Investigate 102.110.7.41 and 102.110.7.160 for potential lateral movement or shared infrastructure.

2. Check BGP Stability: Verify route consistency and ensure AS Path integrity.

3. Subnet Analysis: Assess the 102.110.0.0/16 subnet for broader abuse patterns.

4. Firewall Rules: Consider allowing traffic only to trusted subnets, given the firewalled nature of this IP.

---

Conclusion: While the IP itself is not malicious, its subnet contains higher-risk neighbors and exhibits BGP instability. Further investigation into the subnet’s activity is advised.

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

🌍 Geolocation

Country🌐 TN
RegionTunis 1053
CityBP n641 1053 - Tunis Cedex
Timezoneβ€”
Latitude34.47
Longitude9.46

🏒 Ownership & Registration

OrganizationBELGAIED Lobna
ASNAS37693
Network Name102.110.0.0 - 102.110.255.255
CIDR Block102.110.0.0/16
RIRAFRINIC
CountryTN
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
27%
23
routing
27%
23
services
13%
11
ownership
30%
33
reputation
22%
13
geolocation
13%
11
Overall22%1014
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-13 06:36:24 UTC
Last Seen2026-06-23 07:02:55 UTC
Profile Built2026-06-06 17:41:55 UTC
Data FreshnessLive
Signal Types18
Total Observations24
πŸ” 18 signal types Β· 24 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.