176.103.2.130 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of August 29, 2026, IPDebrief rates it Low Risk (15/100); no anonymizing service was detected.
# IPDEBRIEF INTELLIGENCE BRIEFING
Target IP: 176.103.2.130/32
Report Date: 2026-07-23
Classification: MODERATE RISK
---
## EXECUTIVE SUMMARY
IP 176.103.2.130 presents a moderate risk profile (score: 65/100) with no active threat indicators. The address is associated with DIALOG-NET infrastructure in Ukraine and operates with minimal service exposure. While currently classified as clean, the IP is listed on 3 DNS blacklist entries and should be monitored due to elevated risk scoring.
---
## OWNERSHIP & INFRASTRUCTURE
| Attribute | Value |
|---|---|
| **ASN** | 56812 |
| **Organization** | DIALOGKOM-MNT (DIALOG-NET) |
| **CIDR Block** | 176.103.0.0/19 |
| **RIR** | RIPE |
| **Registration** | Not available |
Network Classification: The IP is assigned to a firewalled network with no open services detected. No TLS certificates, HTTP titles, or server banners were observed during probing.
---
## GEOLOCATION
| Attribute | Value |
|---|---|
| **Country** | Ukraine (UA) |
| **Region** | Kharkivs'ka Oblast' |
| **City** | Balakliya |
| **Timezone** | Europe/Kyiv |
| **Geo Confidence** | Low (geoPlausible: false) |
*Note: Geolocation data shows low confidence with 500km accuracy radius and only one geo-source consensus.*
---
## THREAT ASSESSMENT
Risk Profile
- Overall Risk Score: 65/100 (Moderate)
- Abuse Confidence Score: Not available
- Known Attacker: No
- Tor Exit Node: No
- Spam Source: No
Blacklist Status
- DNSBL Listed: 3 of 8 total lists
- Threat Feeds: None detected
- Campaign Correlations: 0
Network Behavior
- Honeypot Hits: 0
- Enumeration Strikes: 0
- WAF Violations: Not detected
- Is Persistently Malicious: No
---
## NEIGHBORHOOD ANALYSIS
Subnet: 176.103.2.130/24
- Total Siblings: 65
- Active Siblings: 36
- Threat Siblings: 2
- Abuse Density: 0.0308 (Low-Moderate)
- Subnet Classification: Clean
Risk Distribution:
- High Risk: 1 IP
- Medium Risk: 47 IPs
- Low Risk: 15 IPs
The subnet shows minimal inherited risk (score: 1). One high-risk neighbor was observed at 176.103.2.4 (risk: 40), and 176.103.2.23 showed elevated scoring (55).
---
## SIGNAL HISTORY (16 Observations)
Recent observations (July 23, 2026) show:
- Subnet Classification: Consistent "clean" rating across multiple signals
- Port Scanning: Multiple ports probed with no open services confirmed
- Operator Scoring: Minimal (0.1304)
- Data Sufficiency: 83% coverage across threat, routing, services, ownership, reputation, and geolocation dimensions
No significant temporal escalation in threat behavior observed.
---
## CONTROL PLANE DATA
| Metric | Value |
|---|---|
| **Origin ASN** | 56812 |
| **BGP Prefix** | 176.103.0.0/20 |
| **Route Stability** | False |
| **Route Changes (30d)** | 0 |
| **RPKI State** | Not available |
| **IRR Consistency** | Not available |
| **DNSSEC Valid** | True |
| **DNSBL Total Lists** | 8 |
---
## RELATIONSHIP MAPPING
The IP is associated with DIALOG-NET network entity. No additional relationships to hostnames, organizations, or certificates were detected.
---
## SECURITY RECOMMENDATIONS
Immediate Actions
1. Increase logging verbosity for traffic from this IP address
2. Review recent activity to confirm benign patterns
3. Implement firewall rules based on risk profile
Recommended Firewall Rules
```bash
# iptables
iptables -A INPUT -s 176.103.2.130 -j DROP
# nftables
nft add rule inet filter input ip saddr 176.103.2.130 drop
# nginx
deny 176.103.2.130;
```
Platform-Specific Actions
- Cloudflare WAF: Block with expression `ip.src eq 176.103.2.130`
- AWS WAF: Add to blocklist with CIDR 176.103.2.130/32
- pfSense: Add 176.103.2.130/32 to block list
---
## ANALYST NOTES
- Risk Level: Monitor rather than block immediately. The moderate risk score (65) with no active threat indicators suggests this IP may be misconfigured or in transition.
- Geographic Context: IP is located in Ukraine; consider threat context for your operational environment.
- Infrastructure Type: Firewalled network with no public services suggests this may be internal infrastructure or a protected endpoint.
- Action Priority: Low-Medium. Implement logging and monitoring, but block only if additional threat indicators emerge.
---
END OF BRIEFING
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 | 22% | 1 | 1 |
| routing | 22% | 1 | 1 |
| services | 22% | 1 | 1 |
| ownership | 50% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 35% | 2 | 2 |
| Overall | 25% | 7 | 8 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-05 11:42:43 UTC |
| Last Seen | 2026-10-06 08:47:52 UTC |
| Profile Built | 2026-08-29 05:20:37 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 20 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.2.130
Who owns the IP address 176.103.2.130?
176.103.2.130 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.2.130 located?
Geolocation data places 176.103.2.130 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.2.130 malicious or safe?
176.103.2.130 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.