104.131.174.140
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: 104.131.174.140
Date: 2026-06-06
---
**1. Core Profile**
- Risk Score: 20 (Low Risk)
- Ownership: DigitalOcean, LLC (ASN 14061)
- Geolocation: Clifton, NJ, US (geo-plausible: false)
- Network Role: Cloud infrastructure (DigitalOcean)
- Threat Indicators: No malicious activity detected (no abuse, spam, or campaign ties).
---
**2. Observation History**
- Latest Signals (30D):
- Confirmed as a cloud server (DigitalOcean), not a CDN, Tor, or VPN.
- Geo-validation anomalies: RTT (24ms) << expected for 5,968km distance (minimum 119ms).
- No threat feed listings or malicious campaigns.
- Trend: Stable, no upward risk trajectory.
---
**3. Relationships**
- Linked Networks: Subnet `DIGITALOCEAN-104-131-0-0` (same /20 CIDR).
- Connected Entities: No hostnames, certificates, or organizations tied to this IP.
- Services: No open ports, TLS certs, or HTTP banners detected.
---
**4. Neighborhood Analysis**
- Subnet: `104.131.174.140/24`
- Neighbor Count: 0 (no sibling IPs identified).
- Abuse Density: 0% (clean subnet).
---
**5. Recommendations**
- Monitor: Track for unexpected service changes or geo-validation anomalies.
- Verify: Confirm geolocation discrepancies with DigitalOcean’s infrastructure maps.
- Firewall: No immediate action required; IP is legitimate cloud infrastructure.
Conclusion: 104.131.174.140 is a low-risk DigitalOcean cloud server with no malicious indicators. No action needed unless new threats emerge.
---
*Generated by IPDebrief intelligence tools.*
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_7.4 |
🔐 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 | 28% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 20% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 27% | 1 | 3 |
| geolocation | 37% | 2 | 3 |
| Overall | 23% | 10 | 16 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Claimed geolocation contradicts RTT physics measurement
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-10 22:16:56 UTC |
| Last Seen | 2026-06-27 18:12:53 UTC |
| Profile Built | 2026-06-28 12:18:21 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 25 |
🔍 19 signal types · 25 observations collected
This report is generated from 19+ 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.