176.103.4.135 is an IPv4 address operated by DIALOGKOM-MNT (AS56812), geolocated to London, United Kingdom. As of August 29, 2026, IPDebrief rates it Moderate Risk (55/100); no anonymizing service was detected.
# IP INTELLIGENCE BRIEFING
Subject: 176.103.4.135
Classification: Low Risk / Defensive Monitoring
Report Date: Current
Analyst: IPDebrief Intelligence
---
## EXECUTIVE SUMMARY
IP address 176.103.4.135 presents a low-risk threat profile (risk score: 15/100). The address is assigned to DIALOGKOM-MNT within the DIALOG-NET network block (176.103.0.0/19). No active threat indicators were detected during assessment. The IP shows no evidence of malicious activity, open services, or associations with known attack infrastructure.
---
## NETWORK ATTRIBUTES
| Attribute | Value |
|---|---|
| **IP Address** | 176.103.4.135/32 |
| **ASN** | 56812 |
| **Organization** | DIALOGKOM-MNT |
| **Network** | DIALOG-NET (176.103.0.0/19) |
| **RIR** | RIPE |
| **Geolocation** | London, United Kingdom |
| **Geolocation Confidence** | Plausible (ICMP validation blocked) |
---
## THREAT ASSESSMENT
Overall Risk Score: 15/100 (Low Risk)
Threat Indicators:
- No known attacker status
- No Tor exit node activity
- No spam source classification
- Zero blacklist entries
- No associated threat campaigns
- No persistent malicious behavior observed
Network Classification:
- Firewall status: Active (no open ports)
- Service type: No active services detected
- CDN/Cloud/Proxy: Negative
- Mobile/Residential: Negative
---
## NEIGHBORHOOD ANALYSIS
Subnet: 176.103.4.0/24
- Total Siblings: 71
- Active Siblings: 29
- Threat Siblings: 1
- Abuse Density: 5.7%
- Inherited Risk Score: 0
Elevated-Risk Neighbors:
- 176.103.4.2: Risk score 70 (high)
- 176.103.4.15: Risk score 70 (high)
- 176.103.4.17: Risk score 40 (medium)
The target IP resides in a subnet with minimal threat concentration. One neighbor exhibits elevated risk characteristics.
---
## OBSERVATION HISTORY
Total Signals: 17 observations
Recent Activity: 2026-07-27
- Ownership changes: 0
- Threat persistence days: 0
- Threat observation count: 0
The IP demonstrates stable ownership with no historical threat activity. No persistent malicious signals were observed across the observation period.
---
## RELATIONSHIP GRAPH
The IP is associated with the DIALOG-NET network infrastructure. No cross-ownership or shared infrastructure relationships with known malicious entities were identified.
---
## RECOMMENDED ACTIONS
Security Actions: None required
Firewall Rules: No blocking recommended based on current risk profile
Monitoring Level: Standard
---
## ANALYST NOTES
The target IP 176.103.4.135 presents minimal threat to defensive operations. The low-risk score correlates with:
- No open ports or active services
- No threat indicator associations
- Stable ownership history
- Low neighborhood abuse density
SOC Guidance: Monitor as part of standard network traffic. No immediate blocking or investigation required. Maintain awareness of elevated-risk neighbors in the same subnet (176.103.4.2, 176.103.4.15) for context during incident analysis.
---
End of Briefing
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 | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-15 04:05:46 UTC |
| Last Seen | 2026-10-06 00:46:37 UTC |
| Profile Built | 2026-08-29 12:19:11 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 20 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.4.135
Who owns the IP address 176.103.4.135?
176.103.4.135 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.4.135 located?
Geolocation data places 176.103.4.135 in London, Kharkivs’ka Oblast’, United Kingdom. The local time zone is Europe/London. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 176.103.4.135 malicious or safe?
176.103.4.135 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.