IPDebrief

176.103.7.232

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

Date: 2026-06-05

---

**1. Risk Profile**

---

**2. Ownership & Geolocation**

---

**3. Subnet & Neighborhood Analysis**

- High Risk: 5 IPs (e.g., 176.103.7.9, 176.103.7.141, 176.103.7.247).

- Medium Risk: 23 IPs.

- Low Risk: 11 IPs.

- 176.103.7.9 (risk score 80), 176.103.7.141 (80), and 176.103.7.247 (80) show elevated risk.

---

**4. Historical Observations**

---

**5. Relationships & Network Context**

- Subnet: 176.103.0.0/19 (DIALOG-NET).

- No direct links to known malicious organizations or domains.

---

**6. Recommendations**

1. Monitor Subnet: Focus on high-risk neighbors (e.g., 176.103.7.9, 176.103.7.141) for potential lateral movement or network compromise.

2. Verify Ownership: Confirm DIALOGKOM-MNT’s legitimacy and check for recent ASN changes.

3. Enable Subnet Filtering: Consider blocking the 176.103.7.0/24 subnet if traffic is suspicious, given the moderate abuse density.

4. Check for Anomalies: Investigate if the IP’s stability score (0) correlates with routing instability or misconfigurations.

---

Conclusion: While the IP itself shows no direct malicious activity, its subnet contains high-risk neighbors. SOC teams should prioritize monitoring the subnet for potential indirect threats.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡¦ Ukraine
RegionKharkivs’ka Oblast’
CityBalakliya
TimezoneEurope/Kyiv
Latitude49.46
Longitude36.87

🏒 Ownership & Registration

OrganizationDIALOGKOM-MNT
ASNAS56812
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
35%
23
routing
19%
12
services
13%
11
ownership
30%
23
reputation
13%
12
geolocation
23%
22
Overall22%913
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-12 15:47:05 UTC
Last Seen2026-06-09 20:26:53 UTC
Profile Built2026-06-06 12:30:18 UTC
Data FreshnessLive
Signal Types15
Total Observations15
πŸ” 15 signal types Β· 15 observations collected
This report is generated from 15+ 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.