80.174.78.134
IP Intelligence Briefing: 80.174.78.134
Date: 2026-06-10
---
**1. Risk Profile**
- Overall Risk: Moderate (Risk Score: 50)
- Ownership: Registered to netutils-mnt (RIPE) with ASN 3257.
- Geolocation: United States (Washington, Newport).
- Threat Indicators: No active threats, blacklists, or known campaigns.
---
**2. Network & Subnet Analysis**
- Subnet: 80.174.64.0/19 (parent network).
- Network Role: Firewalled / No Services (no open ports, TLS, or HTTP services detected).
- Neighbor Risk:
- 80.174.78.131 (1/24 subnet): Low risk (score: 25).
- Subnet abuse density: 0% (no malicious activity detected in neighbors).
---
**3. Historical Observations**
- Recent Activity (30-Day Window):
- DNSSEC Valid: Yes.
- Operator Score: Minimal (0.13).
- Routing Stability: Unstable (route changes detected).
- DNSBL Listings: 2 out of 8 lists.
- Threat Persistence: No persistent malicious activity.
---
**4. Relationships & Context**
- Linked Entities:
- Network: EUROPEAN-LEASE1-NET (same subnet).
- Organization: netutils-mnt (RIPE-registered).
- No Known Campaigns or Malware Signatures.
---
**5. Recommendations**
- Monitor Subnet: Track 80.174.78.131 for potential lateral movement or abuse.
- Verify DNSSEC: Ensure DNSSEC validation is active for the domain(s) associated with this IP.
- Network Segmentation: Consider isolating this subnet due to routing instability.
- Threat Intelligence Feeds: Cross-check with DNSBLs for updated listings.
Conclusion: The IP itself is low-risk, but its network and subnet history suggest cautious monitoring. Focus on subnet-level anomalies and verify DNSSEC integrity.
---
*Generated by IPDebrief. All data sourced from public registries and threat intelligence feeds.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | netutils-mnt |
| ASN | AS3257 |
| 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 | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 13% | 6 | 7 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-23 06:23:39 UTC |
| Last Seen | 2026-06-10 06:10:00 UTC |
| Profile Built | 2026-06-10 06:19:01 UTC |
| Data Freshness | Live |
| Signal Types | 15 |
| Total Observations | 15 |
Full dossier details are available via our API.