176.103.7.107 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of September 2, 2026, IPDebrief rates it Moderate Risk (55/100); no anonymizing service was detected.
INTELLIGENCE BRIEFING: IP Address 176.103.7.107/32
Classification: MODERATE RISK – ACTIONABLE MONITORING RECOMMENDED
Date: Current Analysis Cycle
---
EXECUTIVE SUMMARY
IP 176.103.7.107 is assigned to DIALOG-NET (AS56812) with a current risk score of 55/100. The address exhibits moderate risk characteristics with DNSBL listings and conflicting geolocation data. While no active threat indicators are currently present, the subnet neighborhood shows elevated medium-risk activity. Security operations teams should implement monitoring controls and evaluate connection patterns.
---
OWNERSHIP AND NETWORK ATTRIBUTES
- ASN: 56812 (DIALOGKOM-MNT / DIALOG-NET)
- CIDR Block: 176.103.0.0/19
- RIR Registry: RIPE
- Network Classification: Firewalled / No Services
- Cloud/CDN/Proxy Status: None detected
GEOLOCATION INTELLIGENCE
Geolocation data presents conflicting signals across sources:
- Primary consensus: London, United Kingdom (GB)
- Secondary signals indicate Kharkivs'ka Oblast', Ukraine (UA)
- Distance analysis: 2,128.6 km from primary geo source with average RTT 136ms
- Geographic validation: Plausible but with consensus flags indicating potential inconsistency
- This discrepancy warrants correlation with historical traffic patterns
THREAT PROFILE
Current Risk Indicators:
- Risk Score: 55/100 (Moderate)
- DNSBL Listings: 3 of 8 total lists
- Threat Feed Status: No active campaigns or known attacker flags
- Tor Exit Node: No
- Known Spam Source: No
Historical Signals (13 observations):
- Recent observations indicate threat feed presence with maximum severity "high"
- One historical source flagged "has_threats: true" for Balakliya region
- DNSSEC validation: Valid
- Route stability: Flagged as unstable (false)
SUBNET NEIGHBORHOOD ANALYSIS
Subnet: 176.103.7.0/24
Total Neighbor Count: 74 IPs
Risk Distribution:
- High Risk: 0
- Medium Risk: 55 IPs
- Low Risk: 18 IPs
Notable Neighbor Risk Scores:
- 176.103.7.9: 70 (Elevated)
- 176.103.7.17: 55 (Moderate)
- 176.103.7.6: 40 (Lower-Moderate)
- 176.103.7.13, 176.103.7.18: 15-0 (Low)
Neighborhood abuse density: 0 (low baseline activity)
RELATIONSHIP MAPPING
Single relationship identified:
- Network: DIALOG-NET (Same Network classification)
- No hostname, certificate, or organizational relationships detected
RECOMMENDED ACTIONS
Immediate:
1. Implement enhanced logging for traffic from 176.103.7.107
2. Monitor connection patterns and payload analysis
Firewall Recommendations:
- iptables: `iptables -A INPUT -s 176.103.7.107 -j DROP`
- nftables: `nft add rule inet filter input ip saddr 176.103.7.107 drop`
- nginx: `deny 176.103.7.107;`
Cloud Platform Actions:
- Cloudflare WAF: Block with expression `ip.src eq 176.103.7.107`
- AWS WAF: Add 176.103.7.107/32 to block list
SOC ANALYST NOTES
The moderate risk classification (55/100) with DNSBL presence suggests this IP has been flagged by threat intelligence feeds. The geolocation inconsistency between UK and Ukraine signals requires correlation with traffic metadata. The subnet's 55/74 medium-risk neighbors indicates this network block has elevated activity levels.
Priority: Monitor with enhanced logging; block only if additional threat indicators emerge during observation period.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DIALOGKOM-MNT |
| ASN | AS56812 |
| Network Name | DIALOG-NET |
| CIDR Block | 176.103.0.0/19 |
| RIR | RIPE |
| Country | UA |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS56812 |
| Network Prefix | 176.103.0.0/20 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 4% | 1 | 1 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-19 12:02:03 UTC |
| Last Seen | 2026-10-06 10:03:47 UTC |
| Profile Built | 2026-09-02 13:45:26 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.7.107
Who owns the IP address 176.103.7.107?
176.103.7.107 is registered to DIALOGKOM-MNT. The address falls within the 176.103.0.0/19 network block. Registration is held at RIPE.
Where is 176.103.7.107 located?
Geolocation data places 176.103.7.107 in Balakliya, Kharkivs’ka Oblast’, Ukraine. The local time zone is Europe/Kyiv. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 176.103.7.107 malicious or safe?
176.103.7.107 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.