# 176.103.6.146 — IP Intelligence Summary

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.

- Canonical page: https://ipdebrief.com/176.103.6.146
- Last updated: 2026-10-06

## Ownership

- Organization: DIALOGKOM-MNT
- Network name: DIALOG-NET
- Allocated block: 176.103.0.0/19
- ASN: AS56812 (https://ipdebrief.com/asn/56812)
- Regional registry: RIPE

## Location

- City: Balakliya
- Region: Kharkivs’ka Oblast’
- Country: Ukraine
- Time zone: Europe/Kyiv

## Network classification

- Infrastructure type: —
- Datacenter / hosting: no
- Residential: no
- Mobile: no
- Anycast: no
- Tor exit node: no
- VPN: no
- Proxy: no

## Risk assessment

- Assessment: Moderate Risk (55/100)
- Blocklist listings: 0
- Suspicious activity indicators: no
- Spam source: no

## Analyst narrative

\# 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.

## Nearby addresses

- 176.103.6.3 (https://ipdebrief.com/176.103.6.3)
- 176.103.6.5 (https://ipdebrief.com/176.103.6.5)
- 176.103.6.7 (https://ipdebrief.com/176.103.6.7)
- 176.103.6.8 (https://ipdebrief.com/176.103.6.8)
- 176.103.6.11 (https://ipdebrief.com/176.103.6.11)
- 176.103.6.12 (https://ipdebrief.com/176.103.6.12)
- 176.103.6.14 (https://ipdebrief.com/176.103.6.14)
- 176.103.6.15 (https://ipdebrief.com/176.103.6.15)
- 176.103.6.16 (https://ipdebrief.com/176.103.6.16)
- 176.103.6.17 (https://ipdebrief.com/176.103.6.17)
- 176.103.6.18 (https://ipdebrief.com/176.103.6.18)
- 176.103.6.19 (https://ipdebrief.com/176.103.6.19)

---

Source: IPDebrief, "176.103.6.146 IP intelligence", https://ipdebrief.com/176.103.6.146, updated 2026-10-06. Assessments are probabilistic.