IPDebrief

185.106.29.185

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

Date: 2026-06-02

---

**Key Risk Indicators**

- Flagged by 4/8 DNSBLs (low-severity listings).

- No direct malware campaigns or known attacker associations.

---

**Network & Ownership**

- 2 high-risk IPs (70/70 score).

- 1 low-risk IP (0/50 score).

- Registered to Admin RIPE (RIPE NCC).

- No recent ownership changes.

---

**Threat Context**

- No honeypot hits or WAF violations.

- Minimal operator risk score (0.13).

---

**Actionable Insights**

1. Monitor Neighbors: The subnet contains 2 high-risk IPs; investigate potential lateral movement or shared infrastructure.

2. Check DNSBL Listings: Verify if the IP is flagged for spam or abuse (e.g., OpenBLAST, Spamhaus).

3. Network Segmentation: Given the unstable BGP route and mixed subnet risk, consider isolating this IP from critical assets.

4. Geolocation Verification: Confirm if the IP is genuinely hosted in Erbil or if itโ€™s a spoofed geolocation.

---

**Conclusion**

This IP is part of a high-risk subnet managed by a Kurdish ISP. While it lacks direct malicious indicators, its DNSBL listings and unstable routing suggest potential misuse. SOC teams should prioritize monitoring its network context and validate its operational legitimacy.

Recommended Tools: Use IPDebriefโ€™s `ipdebrief_actions` for firewall rules and `ipdebrief_compare` to analyze neighboring IPs.

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

๐ŸŒ Geolocation

Country๐Ÿ‡ฎ๐Ÿ‡ถ IQ
RegionErbil Governorate
CityErbil
Timezoneโ€”
Latitude36.19
Longitude44.02

๐Ÿข Ownership & Registration

OrganizationAdmin RIPE
ASNAS206206
Network Nameโ€”
CIDR Blockโ€”
RIRRIPE
Countryโ€”
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

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
34%
23
routing
25%
11
services
8%
11
ownership
20%
23
reputation
23%
13
geolocation
13%
11
Overall20%812
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Live

First Seen2026-05-07 23:04:00 UTC
Last Seen2026-06-23 00:24:55 UTC
Profile Built2026-06-23 00:35:44 UTC
Data FreshnessLive
Signal Types16
Total Observations21
๐Ÿ” 16 signal types ยท 21 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.