176.103.3.167
IP Intelligence Briefing: 176.103.3.167
Date: 2026-06-13
---
**1. Core Profile**
- Risk Score: 55 (Moderate Risk)
- Geolocation: London, UK (GB)
- Network Role: Firewalled / No Services (no open ports, no SSL/TLS, no HTTP services)
- Ownership: Unregistered (no ASN, org, or RIR data)
- Threat Indicators: No direct malicious signals (no malware, phishing, or spam links).
---
**2. Observation History**
- DNSBL Listings:
- Listed in 8 DNSBLs (3 high-severity hits, 5 low-severity).
- Last observed in Ukraine (UA) with 0.35 confidence (potential false positive).
- BGP Data:
- Part of AS56812 (Zarko Alexandr Ivanovich, Ukraine), registered 2011-12-08.
- Route stability: Unstable (route changes in last 30 days).
---
**3. Network Relationships**
- No direct relationships (no subnets, domains, or certificates linked).
- Neighbors in 176.103.3.0/24:
- High-risk neighbors: 1 (e.g., 176.103.3.3, risk score 80).
- Medium-risk neighbors: 22 (e.g., 176.103.3.5, risk score 40).
- Low-risk neighbors: 6 (e.g., 176.103.3.19, risk score 0).
- Abuse Density: 3.3% (low, but 1 high-risk neighbor may indicate broader risk).
---
**4. Threat Analysis**
- Likely Scenario:
- The IP is firewalled and inactive (no services, no DNS resolution).
- DNSBL listings suggest potential spam or malicious activity (though no direct evidence).
- Geolocation discrepancy: London (GB) vs. BGP registration in Ukraine (UA) raises suspicion of misconfiguration or spoofing.
- Neighbor Risk: One high-risk neighbor (176.103.3.3) warrants investigation for potential lateral movement or shared infrastructure.
---
**5. Recommended Actions**
1. Monitor Traffic: Check for unexpected outbound connections or DNS queries from this IP.
2. Block DNSBL Matches: Implement firewall rules to block IPs listed in the same DNSBLs (e.g., Spamhaus, Barracuda).
3. Investigate Neighbors: Focus on 176.103.3.3 (high-risk) for shared infrastructure or compromise.
4. Verify Ownership: Confirm if the Ukrainian ASN (AS56812) is legitimate or if this IP is part of a spoofed route.
---
Conclusion: While the IP appears inactive, its DNSBL listings and geolocation mismatch warrant cautious monitoring. Prioritize high-risk neighbors and validate ownership data.
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 | |||
| 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 | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 2% | 1 | 1 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-06-05 07:04:53 UTC |
| Last Seen | 2026-06-26 18:10:47 UTC |
| Profile Built | 2026-06-13 04:38:35 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 16 |
Full dossier details are available via our API.