176.103.6.146 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of October 6, 2026, IPDebrief rates it Moderate Risk (55/100); no anonymizing service was detected.
# IP INTELLIGENCE BRIEFING
IP Address: 176.103.6.146/32
Date: Current
Classification: Moderate Risk
---
## Executive Summary
IP 176.103.6.146 presents a moderate risk profile (risk score: 45) with no active threat indicators detected. The address belongs to Ukrainian hosting provider DIALOGKOM-MNT (ASN: 56812, RIR: RIPE). The subnet shows low-to-moderate abuse density (0.06), with 4 high-risk siblings out of 68 total neighbors. No services are actively running on this IP; it is classified as firewalled with no open ports.
---
## Infrastructure Profile
| Attribute | Value |
|---|---|
| **ASN** | 56812 |
| **Organization** | DIALOGKOM-MNT |
| **Network** | 176.103.0.0/19 |
| **Country** | Ukraine (UA) |
| **City** | Balakliya, Kharkivs'ka Oblast' |
| **Geolocation Confidence** | Consensus verified (1 source) |
| **DNS Resolution** | No PTR records, no forward resolution |
---
## Risk Assessment
Overall Risk Score: 45/100 (Moderate)
Key Indicators:
- No open services detected (firewalled/no services)
- Zero blacklist hits
- Not a known attacker, spam source, or Tor exit node
- No associated threat campaigns or certificates
- Not persistently malicious (threat persistence: 0 days)
Network Context:
- Subnet abuse density: 6% (0.0588)
- Subnet classification: mostly_clean
- 27 active sibling IPs out of 68 total
- 4 high-risk siblings identified in neighborhood
High-Risk Neighborhood IPs:
- 176.103.6.14 (risk score: 80)
- 176.103.6.3 (risk score: 70)
- 176.103.6.8 (risk score: 70)
- 176.103.6.12 (risk score: 40)
---
## Observation History
Fifteen signal observations recorded. Recent data (2026-07-28) shows:
- Stable ownership and geolocation
- No significant changes in threat posture
- Consistent ASN and organization registration
- No ownership or threat persistence changes detected
---
## Network Behavior
- Honeypot Hits: 0
- Enumeration Strikes: 0
- Traceroute: 20 hops (1 timed out), transit via Comcast and Cogent
- RTT: 180.2ms (last hop)
- RPKI/IRR: No validation data available
- Route Stability: Flagged as unstable (isRouteStable: false)
---
## Recommended Actions
Based on risk profile and neighborhood analysis, the following controls are recommended:
Firewall Blocking Rules:
```bash
# iptables
iptables -A INPUT -s 176.103.6.146 -j DROP
# nftables
nft add rule inet filter input ip saddr 176.103.6.146 drop
# Cloudflare WAF
{"description":"Block 176.103.6.146 — IPDebrief risk score 45","action":"block","filter":{"expression":"ip.src eq 176.103.6.146"}}
```
Contextual Considerations:
- Block recommended if IP observed in malicious traffic
- Consider blocking entire /24 subnet (176.103.6.0/24) if threat intelligence indicates coordinated abuse
- Monitor high-risk siblings (176.103.6.14, 176.103.6.3, 176.103.6.8) for additional indicators
---
Analyst Notes: This IP shows no active exploitation indicators but carries moderate risk due to its network context. The subnet contains multiple high-risk addresses, suggesting potential for coordinated or opportunistic abuse. Recommend blocking at perimeter if observed in threat traffic, with continued monitoring of related subnet addresses.
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 | 0% (None) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| 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 | 34% | 2 | 6 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 23% | 1 | 4 |
| geolocation | 32% | 2 | 3 |
| Overall | 21% | 10 | 19 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-17 17:12:16 UTC |
| Last Seen | 2026-10-06 02:48:39 UTC |
| Profile Built | 2026-10-06 02:50:44 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 23 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.6.146
Who owns the IP address 176.103.6.146?
176.103.6.146 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.6.146 located?
Geolocation data places 176.103.6.146 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.6.146 malicious or safe?
176.103.6.146 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.