64.226.88.70
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: 64.226.88.70
Date: 2026-06-11
---
**1. Core Profile**
- Risk Score: 40 (Moderate Risk)
- Provider: DigitalOcean, LLC (ASN 14061)
- Geolocation: Frankfurt am Main, Hesse, Germany (DE)
- Network Role: Cloud Compute (Virtual Machine)
- Threat Indicators: No malicious activity detected (no indicators, blacklists, or campaigns).
---
**2. Observation History**
- Temporal Trends:
- No persistent threats or ownership changes detected.
- Recent observations (2026-06-11) show stable geolocation (Frankfurt) and minimal network anomalies.
- DNSSEC validation is active, but no DNSBL listings.
---
**3. Relationships**
- Network Connections:
- Linked to DigitalOcean’s subnet `DIGITALOCEAN-64-226-64-0/18`.
- No external hostname or certificate associations.
- No known Tor, CDN, or proxy infrastructure.
---
**4. Neighborhood Analysis**
- Subnet: `64.226.88.70/24` (isolated /32 host).
- Abuse Density: 0% (clean subnet).
- Neighbors: No sibling IPs found (likely due to /32 subnet).
---
**5. Behavioral Insights**
- Traceroute: 19 hops, with transit through Comcast.
- RTT (Round-Trip Time): Average 110ms (consistent with Frankfurt location).
- Services: No open ports or TLS certificates detected.
---
**6. Recommendations**
- Monitoring: Track for unexpected service activation or geolocation drift.
- Firewall: No immediate blocking required; focus on network segmentation.
- Context: DigitalOcean IPs are generally legitimate, but ensure alignment with known cloud infrastructure.
---
Conclusion: 64.226.88.70 is a clean, cloud-hosted VM with no malicious signals. Monitor for deviations from baseline behavior.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | DIGITALOCEAN-64-226-64-0 |
| CIDR Block | 64.226.64.0/18 |
| RIR | ARIN |
| Country | United States |
| 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 | 60% (Good) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | nginx/1.24.0 (Ubuntu) |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13.16 |
🔐 TLS Certificate
An expired certificate for
CN=hesp.riyada-ventures.com was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.CN=hesp.riyada-ventures.com
Issued by CN=E7, O=Let's Encrypt, C=US
Self-signed: No
| SANs | hesp.riyada-ventures.comwww.hesp.riyada-ventures.com |
| Valid From | 2026-02-24T22:03:33+00:00 |
| Valid Until | 2026-05-25T22:03:32+00:00 (expired) |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha384ECDSA |
| Validity Period | 89 days |
| Serial Number | 0680CEC9A89EB7102063E16DC39AAA3558F5 |
| Thumbprint | FC2DF79901B923908A8FCD0C8C8CD5756D65AA2E |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 27% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 24% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 27% | 2 | 3 |
| Overall | 22% | 10 | 17 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Geo sources disagree on country: US, DE
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-26 18:58:13 UTC |
| Last Seen | 2026-06-29 03:26:36 UTC |
| Profile Built | 2026-06-29 03:33:10 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 23 |
🔍 22 signal types · 23 observations collected
This report is generated from 22+ 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.