# IP Intelligence Briefing: 176.103.1.52/32
Classification: Moderate Risk (55/100) | Location: Balakliya, Kharkivs'ka Oblast, Ukraine (UA) | ASN: AS56812 (DIALOGKOM-MNT) | Network: DIALOG-NET (176.103.0.0/19)
---
## Executive Summary
IP address 176.103.1.52 is a moderately risky address associated with Ukrainian network operator DIALOGKOM-MNT. The IP is currently firewalled with no active services, presenting limited immediate threat. However, elevated risk scoring warrants monitoring and defensive blocking considerations.
---
## Risk Assessment
- Overall Risk Score: 55/100 (Moderate)
- Abuse Confidence Score: Not available
- Blacklist Status: Listed on 3 of 8 DNSBL feeds
- Threat Classification: Not a known attacker, not a spam source, not a Tor exit node
---
## Network Infrastructure
| Attribute | Value |
|---|---|
| **ASN** | AS56812 (DIALOGKOM-MNT) |
| **Network** | DIALOG-NET |
| **CIDR Block** | 176.103.0.0/19 |
| **RIR** | RIPE |
| **Registration Date** | Not available |
| **Abuse Contact** | Available via RDAP |
Network Role: Firewalled / No Services detected | Infrastructure Type: Not provider, CDN, VPN, proxy, hosting, or mobile carrier
---
## Geolocation Intelligence
- Country: Ukraine (UA)
- Region: Kharkivs'ka Oblast
- City: Balakliya
- Geolocation Confidence: 500km radius accuracy
- Validation Status: ICMP blocked - unable to validate geolocation
- Minimum Possible RTT: 42.6ms
---
## Threat Indicators
- Active Threats: None detected
- Campaign Correlations: 0
- Certificate Matches: 0
- Honeypot Hits: 0
- Enumeration Strikes: 0
- WAF Violations: Not detected
---
## Neighborhood Analysis (176.103.1.0/24)
- Total Subnet Size: 60 siblings
- Abuse Density: 1.7% (0.017)
- Risk Distribution:
- High Risk: 1 IP
- Medium Risk: 38 IPs
- Low Risk: 18 IPs
Notable Neighbor: 176.103.1.4 (Risk Score: 55, Authority Score: 50)
---
## Historical Observations (Last 15 Signals)
Recent observations from 2026-07-28 indicate:
- Consistent geolocation signals pointing to Ukraine
- Stable ownership attribution to DIALOGKOM-MNT
- No evidence of persistent malicious activity
- No ownership changes detected
---
## Defensive Recommendations
Monitoring Actions
- Increase logging verbosity for traffic from this IP
- Review recent activity patterns for anomalous behavior
- Monitor for service changes (currently firewalled)
Firewall Rules
iptables:
```
iptables -A INPUT -s 176.103.1.52 -j DROP
```
nftables:
```
nft add rule inet filter input ip saddr 176.103.1.52 drop
```
nginx:
```
deny 176.103.1.52;
```
Cloudflare WAF:
```
ip.src eq 176.103.1.52 → Block
```
AWS WAF:
```
Addresses: 176.103.1.52/32
```
---
## Intelligence Notes
- The IP is part of a subnet with mixed risk characteristics (1.7% abuse density)
- Control plane shows route instability (isRouteStable: false)
- No email reputation data available
- No DNS-based email authentication (SPF/DMARC) detected
- Control plane DNSSEC validation: Valid
---
Report Generated: Current | Data Sources: IPDebrief Intelligence Platform | Classification: SOC Intelligence
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-08-31 13:13:42 UTC |
| Profile Built | 2026-08-31 13:19:11 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 25 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.1.52
Who owns the IP address 176.103.1.52?
176.103.1.52 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.1.52 located?
Geolocation data places 176.103.1.52 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.1.52 malicious or safe?
176.103.1.52 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.