176.103.1.63
# IP INTELLIGENCE BRIEFING
Target: 176.103.1.63/32
Date: 2026-07-27
Classification: Low Risk / Passive Infrastructure
---
## EXECUTIVE SUMMARY
IP 176.103.1.63 presents as low-risk passive infrastructure with no active services detected. The address belongs to DIALOG-NET (ASN 56812) and exhibits minimal threat indicators despite geographic reporting inconsistencies. No immediate defensive actions recommended.
---
## PROFILE OVERVIEW
| Attribute | Value |
|---|---|
| **Risk Score** | 25/100 |
| **Reputation** | Low Risk |
| **ASN** | 56812 |
| **Organization** | DIALOGKOM-MNT (DIALOG-NET) |
| **CIDR Block** | 176.103.0.0/19 |
| **RIR** | RIPE |
| **Control Plane** | Route Stable: No (false) |
| **DNSBL Listed** | 1 of 8 lists |
---
## GEOLOCATION & VALIDATION
- Reported Location: London, GB (Europe/London)
- Geographic Discrepancy: Multiple sources indicate Kharkivs'ka Oblast' region
- Validation Status: ICMP blocked - unable to validate
- Plausibility Score: True
- Distance Anomaly: 2,128.6 km reported
Assessment: Geographic consensus unavailable. Multiple conflicting reports suggest potential routing manipulation or data center misattribution.
---
## NETWORK SERVICES & THREATS
- Open Ports: None detected
- Service Status: Firewalled / No Services
- Tor Exit Node: No
- Known Attacker: No
- Spam Source: No
- Malware Campaigns: None correlated
- Threat Feeds: No indicators
Assessment: Passive address with no active services. Firewall configuration prevents service enumeration.
---
## NEIGHBORHOOD ANALYSIS (176.103.1.0/24)
| Metric | Value |
|---|---|
| **Subnet Classification** | Mostly Clean |
| **Abuse Density** | 6.78% |
| **Total Siblings** | 59 |
| **Active Siblings** | 27 |
| **Threat Siblings** | 4 |
| **Risk Distribution** | 1 High, 37 Medium, 19 Low |
Notable Neighbor: 176.103.1.4 (Risk Score: 55)
Assessment: Subnet exhibits minimal abuse density. One sibling IP shows elevated risk requiring monitoring.
---
## OBSERVATION HISTORY
- Total Observations: 17 signals
- Recent Activity: 2026-07-27
- Ownership Changes: 0
- Threat Persistence Days: 0
- Is Persistently Malicious: False
- Traceroute Hops: 29 (10 timed out)
- Transit Networks: Comcast, Cogent
Temporal Analysis: No ownership changes or persistent malicious behavior observed. IP remains in stable operational state.
---
## RELATIONSHIP GRAPH
- Network Associations: DIALOG-NET (multiple references)
- Organizational Links: None identified beyond network ownership
- Certificate Associations: None
---
## DEFENSIVE RECOMMENDATIONS
Current Status: No specific actions recommended
Observations:
- No active threat indicators present
- Firewall rules not automatically generated due to low-risk profile
- Geographic validation requires manual verification if traffic patterns inconsistent with London
Suggested Actions:
1. Monitor subnet 176.103.1.0/24 for emerging threats
2. Investigate neighbor 176.103.1.4 (risk score 55) if traffic observed
3. Verify geolocation claims against actual traffic routing patterns
4. Maintain baseline monitoring for subnet-level anomalies
---
## CONCLUSION
IP 176.103.1.63 operates as low-risk passive infrastructure with no active services. Geographic reporting inconsistencies warrant investigation if traffic patterns suggest non-London origin. Subnet exhibits minimal abuse density with one notable high-risk neighbor requiring awareness. No immediate blocking or mitigation actions warranted.
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 | 0% (None) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| 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 | 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-09-25 14:21:42 UTC |
| Profile Built | 2026-09-25 03:15:35 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 25 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 176.103.1.63
Who owns the IP address 176.103.1.63?
176.103.1.63 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.1.63 located?
Geolocation data places 176.103.1.63 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.1.63 malicious or safe?
176.103.1.63 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.1.63?
Responsive ports observed on 176.103.1.63 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.