77.83.39.235
IP Intelligence Briefing: 77.83.39.235
Date: 2026-06-06
---
**Risk Profile**
- Overall Risk Score: Low (25/100)
- Threat Indicators: No malicious activity detected (no indicators, blacklists, or campaigns).
- Network Role: Firewalled / No Services (no open ports, no TLS/HTTP services).
- Ownership: Registered to LANEDONET ABUSE DEPARTMENT (ASN 214940, Netherlands).
---
**Geolocation & Network**
- Location: Amsterdam, Netherlands (52.13°N, 5.29°E).
- Subnet: 77.83.39.0/24.
- Subnet Abuse Density: 13.3% (6 high-risk neighbors out of 45).
- Neighbor Analysis:
- High-risk neighbors: 6 IPs with risk scores ≥80.
- Mixed activity: Subnet includes both low-risk (20) and high-risk (6) IPs.
---
**Observation History**
- Recent Activity (Last 30 Days):
- 16 observations, including DNSBL listings (1), geolocation (NL/Ukraine), and network ownership.
- No persistent malicious behavior or campaign correlations.
- One entry linked to Ukraine (potential geolocation inconsistency).
---
**Network Relationships**
- Linked Entities:
- Same Network: LANEDONET ABUSE DEPARTMENT (ASN 214940).
- No external relationships (no subnets, domains, or certificates tied to this IP).
---
**Actionable Insights**
1. Monitor Subnet: The 77.83.39.0/24 subnet contains high-risk neighbors (e.g., 77.83.39.2, 77.83.39.27, 77.83.39.31). Investigate potential lateral movement or shared infrastructure.
2. Verify Ownership: Confirm LANEDONET ABUSE DEPARTMENT’s legitimacy and ensure no abuse is occurring under their ASN.
3. Check DNSBL Listings: The IP is listed in 1 DNSBL (potential spam or abuse activity). Validate the listing and block if confirmed.
4. Segment Network: Ensure the subnet is properly segmented to limit exposure from high-risk neighbors.
---
Conclusion:
The IP itself is low risk, but its subnet contains notable high-risk neighbors. SOC teams should prioritize monitoring the subnet and validating the ownership/legitimacy of LANEDONET to mitigate potential risks.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | LANEDONET ABUSE DEPARTMENT |
| ASN | AS214940 |
| Network Name | — |
| CIDR Block | — |
| RIR | RIPE |
| Country | — |
| 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 | 35% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 24% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 27% | 2 | 3 |
| Overall | 21% | 9 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-12 03:44:23 UTC |
| Last Seen | 2026-06-26 18:11:34 UTC |
| Profile Built | 2026-06-26 15:36:34 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 17 |
Full dossier details are available via our API.