176.103.7.52
176.103.7.52 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to Balakliya, Ukraine. As of September 2, 2026, IPDebrief rates it High Risk (70/100); no anonymizing service was detected.
# IP INTELLIGENCE BRIEFING
Target: 176.103.7.52/32
Classification: Web Server / Infrastructure Node
Date: 2026-07-27
---
## EXECUTIVE SUMMARY
IP 176.103.7.52 presents a low-risk profile with a risk score of 0. Current profile indicates a London-based web server (GB), but historical data reveals conflicting geolocation signals pointing to Ukraine. The IP operates a lighttpd web server with standard HTTP/HTTPS services and exhibits no active threat indicators. However, recent blacklist activity and routing instability warrant monitoring.
---
## INFRASTRUCTURE PROFILE
Ownership: ASN 56812 (ASZARKO - CHP Zarko Alexandr Ivanovich, UA)
BGP Prefix: 176.103.0.0/20
Location: London, GB (current consensus) / Ukraine, UA (historical)
Service: Web Server (HTTP/HTTPS)
Server Software: lighttpd/1.4.39
Ports: 80/tcp, 443/tcp
Routing Status: Unstable (route changes observed within 30-day window)
DNSSEC: Valid
PTR Record: None
Reverse DNS: Not resolved
---
## THREAT INDICATORS
Current Risk Score: 0 (Low Risk)
Blacklist Status: 4 of 8 total listings (historical observation)
Threat Severity: High (on listed feeds)
Known Campaigns: None identified
Tor/Proxy/VPN: Negative for all categories
Abuse Confidence Score: Not reported
---
## OBSERVATION HISTORY (Last 10 Signals)
Recent observations reveal concerning patterns:
- Geolocation Discrepancy: Historical signals (2026-07-27) indicate Ukraine coordinates (48.38, 31.17) with 500km accuracy
- Blacklist Activity: 4 blacklist listings identified with high severity ratings
- DNSSEC: Validated (signed zone 52.7.103.176.in-addr.arpa)
- Ownership Persistence: No ownership changes recorded
- Threat Persistence: No persistent malicious activity detected
---
## SUBNET ANALYSIS (176.103.7.0/24)
Total Neighbors: 73 IPs
Abuse Density: 0%
Risk Distribution:
- High Risk: 0
- Medium Risk: 50 (68.5%)
- Low Risk: 23 (31.5%)
Notable Neighbor IPs:
| IP Address | Risk Score | Authority Score |
|---|---|---|
| 176.103.7.9 | 70 | 50 |
| 176.103.7.17 | 55 | 50 |
| 176.103.7.6 | 40 | 50 |
| 176.103.7.13 | 15 | 50 |
| 176.103.7.18 | 0 | 50 |
*Subnet exhibits elevated medium-risk activity concentration.*
---
## RELATIONSHIP GRAPH
No direct relationships identified with other IPs, hostnames, organizations, or certificates.
---
## NETWORK BEHAVIOR
Traceroute: 21 hops (Comcast, Cogent transit networks)
RTT: 0.1ms (first hop) to 138.3ms (last hop)
Honeypot Hits: 0
Enumeration Strikes: 0
WAF Violations: Not observed
---
## SECURITY RECOMMENDATIONS
Current Action: Monitor
Justification: Low-risk profile with no active threat indicators. However, the following factors warrant continued observation:
1. Geographic inconsistency (GB vs UA)
2. Blacklist history with high-severity entries
3. Routing instability in parent prefix
4. Subnet-level medium-risk concentration (50/73 IPs)
Firewall Rules: No specific blocking rules recommended at this time. Allow traffic if required for business operations, but monitor for behavioral anomalies.
---
## CONCLUSION
IP 176.103.7.52 is classified as low-risk with no current active threats. The infrastructure appears to be a standard web server with legitimate service purposes. Historical blacklist activity and geolocation discrepancies suggest the need for continued monitoring, but no immediate blocking action is warranted. The parent subnet (176.103.7.0/24) exhibits moderate risk concentration that should be factored into broader subnet-level security policies.
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 | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Web server detected |
| 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 | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 4% | 1 | 1 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-15 10:08:42 UTC |
| Last Seen | 2026-10-06 08:56:22 UTC |
| Profile Built | 2026-09-02 19:00:59 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 26 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.7.52
Who owns the IP address 176.103.7.52?
176.103.7.52 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.7.52 located?
Geolocation data places 176.103.7.52 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.7.52 malicious or safe?
176.103.7.52 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.
What ports are open on 176.103.7.52?
Responsive ports observed on 176.103.7.52 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.