176.103.0.30
# IP Intelligence Briefing: 176.103.0.30
## Executive Summary
Risk Level: Moderate (Score: 40/100)
Classification: Network Infrastructure
Primary Concern: DNSBL listings with high severity; moderate abuse activity in /24 neighborhood
---
## Ownership & Network Context
- ASN: 56812 (DIALOGKOM-MNT)
- Organization: DIALOG-NET
- Network Block: 176.103.0.0/19 (RIPE NCC)
- Registration: Stable ownership (0 changes observed)
- Geolocation: Registered as GB; historical signals indicate Ukraine (UA) with 500km accuracy radius
---
## Threat Indicators
- DNSBL Status: Listed on 2 of 8 DNSBL feeds (max severity: HIGH)
- Threat Classifications: No Tor exit, proxy, CDN, or hosting services detected
- Service Status: Firewalled / No services exposed (no open ports)
- Campaigns: No known threat campaign matches
- Abuse Confidence: No direct confidence score; moderate risk profile
---
## Neighborhood Analysis (176.103.0.0/24)
- Abuse Density: 2.9% (0.029)
- Total Neighbors: 68
- Risk Distribution: 2 high-risk, 35 medium-risk, 27 low-risk
- Notable High-Risk Siblings:
- 176.103.0.21 (risk: 55, authority: 50)
- 176.103.0.9 (risk: 40, authority: 50)
- 176.103.0.23 (risk: 40, authority: 50)
- 176.103.0.26 (risk: 40, authority: 50)
---
## Temporal Behavior
- Observation Count: 14 signals over monitoring period
- Threat Persistence: 0 days (not persistently malicious)
- Ownership Stability: No changes detected
- Route Stability: False (routing instability observed)
---
## Recommended Actions
1. Monitor DNSBL listings for continued high-severity abuse indicators
2. Correlate with neighborhood IPs 176.103.0.21, 176.103.0.9, 176.103.0.23, 176.103.0.26 for pattern analysis
3. Investigate geolocation discrepancy between registration (GB) and signal data (UA)
4. Standard Rate-Limiting recommended given DNSBL presence and neighborhood abuse density
---
Report Generated: 2026-07-18
Data Source: IPDebrief Intelligence Platform
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 | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 25% | 1 | 1 |
| Overall | 4% | 1 | 1 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-06-08 01:59:22 UTC |
| Last Seen | 2026-08-27 07:11:47 UTC |
| Profile Built | 2026-08-29 05:22:17 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 19 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.0.30
Who owns the IP address 176.103.0.30?
176.103.0.30 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.0.30 located?
Geolocation data places 176.103.0.30 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.0.30 malicious or safe?
176.103.0.30 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.