INTELLIGENCE BRIEFING: IP 176.103.7.139
Classification: HIGH RISK (Score: 70/100)
Executive Summary
IP 176.103.7.139 is classified as high-risk with a reputation score of 70. The address is registered to DIALOGKOM-MNT within the DIALOG-NET network (176.103.0.0/19, ASN 56812) in Ukraine. No active services or open ports were detected; the IP appears firewalled with no web services responding.
Technical Profile
- Network: 176.103.0.0/19, ASN 56812 (DIALOGKOM-MNT)
- Geolocation: Ukraine, Kharkivs'ka Oblast', Balakliya (validation inconclusive)
- Network Role: Firewalled infrastructure, no public services detected
- Control Plane: Listed on 4 of 8 DNSBLs; route instability detected
- DNS: No reverse PTR records; no forward resolution capability
- Email: No SPF or DMARC records configured
Threat Indicators
No specific malicious indicators present. The IP is not identified as a Tor exit node, known attacker, or spam source. However, the elevated risk score and DNSBL listings warrant scrutiny. Recent observation history (14 signals) includes port scanning attempts, traceroute probes, and geolocation validation queries conducted from various transit networks.
Neighborhood Analysis
The /24 subnet (176.103.7.0/24) contains 74 neighboring IPs with mixed risk distribution:
- 60 neighbors with medium risk
- 14 neighbors with low risk
- 0 neighbors with high risk
Notable high-risk siblings include 176.103.7.9 (risk 70) and 176.103.7.18 (risk 70), suggesting potential coordinated activity or shared infrastructure within the subnet.
Recommended Actions
1. Immediate: Increase logging verbosity for traffic from this IP
2. Firewall: Block inbound traffic to critical services
3. Monitoring: Correlate with traffic from high-risk neighbors (176.103.7.9, 176.103.7.18)
Firewall Rules
```
iptables -A INPUT -s 176.103.7.139 -j DROP
nftables: nft add rule inet filter input ip saddr 176.103.7.139 drop
Cloudflare WAF: Block IP 176.103.7.139 (risk score 70)
```
Assessment
While no active exploitation observed, the combination of elevated risk score, DNSBL listings, and neighborhood risk concentration suggests this IP warrants defensive blocking and enhanced monitoring. Recommend blocking at perimeter controls and monitoring for lateral movement from associated high-risk subnet peers.
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 | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 16% | 4 | 5 |
| Data Coherence | Mostly Consistent (80%) β 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-07-28 04:02:42 UTC |
| Last Seen | 2026-07-30 15:16:59 UTC |
| Profile Built | 2026-07-30 15:28:37 UTC |
| Data Freshness | Live |
| Signal Types | 15 |
| Total Observations | 15 |
Full dossier details are available via our API.