176.103.5.143
176.103.5.143 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of October 6, 2026, IPDebrief rates it High Risk (70/100); no anonymizing service was detected.
# IP Intelligence Briefing: 176.103.5.143/32
Date: Current
Classification: Moderate Risk (55/100)
Jurisdiction: Ukraine (UA)
---
## Executive Summary
IP address 176.103.5.143 is classified as Moderate Risk with a risk score of 55. The address is associated with DIALOGKOM-MNT organization within the 176.103.0.0/19 block (ASN 56812). Current analysis indicates no open services and no active threat indicators, though the IP appears on 3 DNS blacklists. Recommended action is to block at perimeter with enhanced logging.
---
## Network Ownership & Geolocation
| Field | Value |
|---|---|
| **Organization** | DIALOGKOM-MNT |
| **Network Name** | DIALOG-NET |
| **ASN** | 56812 |
| **CIDR Block** | 176.103.0.0/19 |
| **Country** | Ukraine (UA) |
| **Region** | Kharkivs'ka Oblast' |
| **City** | Balakliya |
| **RIR** | RIPE |
---
## Threat Assessment
- Risk Score: 55/100 (Moderate)
- Blacklist Count: 3
- Tor Exit: No
- Known Attacker: No
- Spam Source: No
- Open Ports: None (Firewalled / No Services)
- Certificate Status: No TLS certificates observed
---
## Neighborhood Context (176.103.5.0/24)
- Subnet Classification: Mostly Clean
- Abuse Density: 11.48%
- Total Siblings: 61
- Active Siblings: 25
- Threat Siblings: 7
- Risk Distribution: 2 High, 38 Medium, 19 Low
The /24 subnet shows moderate abuse concentration with 7 threat-identified siblings and 38 medium-risk neighbors.
---
## Control Plane Analysis
- Route Stability: Unstable (isRouteStable: false)
- RPKI State: Not verified
- DNSSEC: Valid
- BGP Prefix: 176.103.0.0/20
- IRR Consistency: Not verified
---
## Historical Observation Summary
Analysis of 15 signal observations indicates:
- Geolocation: Consistent Ukraine (UA) reporting
- Ownership: No changes detected
- Threat Persistence: Not persistently malicious
- Last Updated: July 23, 2026
---
## Recommended Actions
Immediate
```bash
# iptables
iptables -A INPUT -s 176.103.5.143 -j DROP
# nftables
nft add rule inet filter input ip saddr 176.103.5.143 drop
```
Platform-Specific
| Platform | Rule |
|---|---|
| **nginx** | `deny 176.103.5.143;` |
| **pfSense** | `176.103.5.143/32` |
| **Cloudflare WAF** | Block with expression: `ip.src eq 176.103.5.143` |
| **AWS WAF** | Add 176.103.5.143/32 to whitelist block |
Operational
- Increase logging verbosity for this IP address
- Review recent connection attempts and traffic patterns
- Monitor for lateral movement attempts from related subnet IPs
---
## Intelligence Notes
- No active exploitation campaigns correlated
- No honeypot strikes or enumeration activity observed
- Subnet abuse density (11.48%) suggests some malicious actors may operate from adjacent addresses
- No services detected; IP appears to be firewalled or passive
Assessment: Block with monitoring. Related subnet IPs (176.103.5.0/24) show 7 known threats; consider broader subnet restrictions if threat activity escalates.
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 | 20% | 2 | 2 |
| routing | 8% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 17% | 2 | 3 |
| reputation | 8% | 1 | 2 |
| geolocation | 12% | 2 | 2 |
| Overall | 12% | 9 | 11 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-03 23:05:13 UTC |
| Last Seen | 2026-10-06 04:05:18 UTC |
| Profile Built | 2026-10-06 04:05:23 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 18 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.5.143
Who owns the IP address 176.103.5.143?
176.103.5.143 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.5.143 located?
Geolocation data places 176.103.5.143 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.5.143 malicious or safe?
176.103.5.143 currently carries a high risk assessment, meaning indicators associated with malicious or abusive activity have been observed. This assessment is generated from continuously collected signals and can change over time.