134.122.74.181
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 134.122.74.181
Date: 2026-06-02
---
**1. Core Profile**
- Risk Score: 40 (Moderate Risk)
- Provider: DigitalOcean (ASN 14061)
- Geolocation: Frankfurt am Main, Hesse, Germany (DE)
- Network Role: CloudCompute (Hosting, No Services)
- Threat Status: Clean (No indicators of malicious activity, no blacklists, no campaigns).
---
**2. Observation History**
- DNSSEC Validity: Confirmed (no validation errors).
- Network Behavior:
- RTT: 101ms (avg), 96ms (min), 108ms (max).
- Distance: ~296km (Frankfurt to observer).
- BGP: Stable route (no recent changes).
- Subnet: 134.122.64.0/20 (DigitalOcean-managed).
---
**3. Relationships**
- Linked Entities:
- Same network: 134.122.0.0/20 (DigitalOcean).
- No DNS, hostnames, or certificates linked.
- Ownership: DigitalOcean, LLC (ARIN-registered).
---
**4. Neighborhood Analysis**
- Subnet: 134.122.74.0/24 (no active/abused IPs detected).
- Abuse Density: 0% (clean subnet).
---
**5. Threat Indicators**
- No malicious signals: No known attackers, spam, or Tor exit nodes.
- DNSBL: 1 listing (low severity).
- Historical Trends: No persistent threats or campaigns.
---
**6. Recommendations**
- Monitoring: Track for unexpected service changes or network anomalies.
- Access Control: Ensure strict access policies for DigitalOcean resources.
- Validation: Confirm DNSSEC and BGP integrity for ongoing compliance.
Conclusion: This IP is part of a legitimate cloud provider’s infrastructure with no current malicious activity. While not a high-risk target, continuous monitoring is advised to detect any potential misuse.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | — |
| CIDR Block | — |
| RIR | ARIN |
| 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 | Infrastructure / Datacenter |
| Service Purpose | Single-Service Host |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 22 | ssh | tcp | |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.16 |
🔐 TLS Certificate
No certificate
Issued by —
N/A
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 47% | 2 | 7 |
| routing | 8% | 1 | 1 |
| services | 21% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 28% | 1 | 4 |
| geolocation | 30% | 2 | 3 |
| Overall | 26% | 10 | 20 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:39 UTC |
| Last Seen | 2026-06-26 22:16:24 UTC |
| Profile Built | 2026-06-27 18:30:21 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 29 |
🔍 20 signal types · 29 observations collected
This report is generated from 20+ independent intelligence signals including
ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds,
behavioral fingerprinting, and more.
Full dossier details are available via our API.
Full dossier details are available via our API.
ℹ️ About This Report
All data shown is publicly available network metadata — IP addresses do not reliably identify individuals.
Assessments are probabilistic and should not be used as sole basis for access control decisions.
To report an issue or request data review, contact admin@ipdebrief.com.