176.103.7.26
IP Intelligence Briefing: 176.103.7.26/32
Date: 2026-06-13
---
**1. Risk Profile**
- Risk Score: 70/100 (High Risk)
- Geolocation: London, UK (GB)
- Network Role: Firewalled / No Services
- Threat Indicators: No direct malware, scans, or spam sources detected.
- Control Plane:
- Subnet: `176.103.0.0/20`
- BGP ASN: 56812 (Route Stability: Unstable)
- DNSSEC Valid: Yes
- DNSBL Listings: 4/8 total lists (moderate risk).
---
**2. Observation History (Last 30 Days)**
- Abuse Density: 0.2553 (Moderate)
- Key Signals:
- Subnet abuse density increased slightly.
- Mixed routing and DNS signals (e.g., DNSSEC validation, BGP route changes).
- No persistent malicious activity or campaign correlations.
---
**3. Relationships**
- Linked Entities: None detected (relationships tool returned empty).
- Domain/Email: No DNS or email authentication records found.
---
**4. Neighborhood Analysis**
- Subnet: `176.103.7.0/24` (46 total IPs)
- Abuse Density: 4.3% (low overall, but 2 IPs flagged as high risk).
- Notable Neighbors:
- `176.103.7.180` (Risk: 80/100)
- `176.103.7.184` (Risk: 80/100)
- `176.103.7.126` (Risk: 0/100, likely benign).
---
**5. Security Actions**
- Recommended Mitigation:
- Block IP: Use firewall rules to deny traffic from `176.103.7.26/32`.
- Monitor Subnet: Track high-risk neighbors (`176.103.7.180`, `176.103.7.184`).
- Review Logs: Investigate potential reconnaissance or probing activity.
Firewall Rules Example:
- `iptables`: `iptables -A INPUT -s 176.103.7.26 -j DROP`
- Cloudflare/WAF: Block with rule `ip.src eq 176.103.7.26`.
---
**6. Summary**
The IP `176.103.7.26` is part of a subnet with mixed risk levels. While no direct threats were detected, its high risk score and association with high-risk neighbors warrant blocking and closer monitoring. Focus on the subnet `176.103.7.0/24` for potential lateral movement or related activity.
Next Steps:
- Confirm if the IP is part of a larger compromised network.
- Validate DNS and routing anomalies in the subnet.
- Update firewall policies to include this IP and high-risk neighbors.
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 | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 12% | 3 | 3 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-06-06 07:26:59 UTC |
| Last Seen | 2026-06-13 11:15:37 UTC |
| Profile Built | 2026-06-13 11:21:29 UTC |
| Data Freshness | Live |
| Signal Types | 15 |
| Total Observations | 15 |
Full dossier details are available via our API.