IP Intelligence Briefing: 146.190.154.100
Date: 2026-06-16
---
**1. IP Profile**
- Risk Score: 80/100 (High Risk)
- Ownership: DigitalOcean, LLC (ASN 14061)
- Geolocation: Santa Clara, CA, US
- Network Role: CloudCompute (DigitalOcean infrastructure)
- Threat Indicators: No direct malicious activity detected (no malware, phishing, or known attacker associations).
---
**2. Observation History**
- Recent Activity:
- Observed with mixed confidence (0.21β0.60) over the past 4 days.
- No persistent malicious behavior or long-term threat signals.
- Key Metrics:
- Abuse Density: 0.5 (subnet 146.190.154.0/24 has moderate risk).
- Neighbor Risk: One sibling IP (146.190.154.85) scored 15/100 (low risk).
---
**3. Relationships**
- Network Associations:
- Linked to DigitalOceanβs network (DO-13) and subnet 146.190.154.0/24.
- DNS:
- Associated with hostname `srv.lanzatumarca.com` (forwarded via DNS).
- No Known Campaigns or Malware Signatures.
---
**4. Neighborhood Analysis**
- Subnet: 146.190.154.0/24
- Abuse Density: 0.5 (50% of IPs in subnet show abuse activity).
- Active Siblings: 1 (146.190.154.85)
- Threat Siblings: 1 (low risk, no malicious indicators).
---
**5. Recommended Actions**
- Firewall Blocking:
- iptables: `iptables -A INPUT -s 146.190.154.100 -j DROP`
- Cloudflare/WAF: Block IP with rule: `ip.src eq 146.190.154.100`
- Monitoring:
- Increase logging verbosity for this IP due to elevated risk score.
- Monitor subnet 146.190.154.0/24 for suspicious activity.
---
Conclusion:
This IP is part of DigitalOceanβs cloud infrastructure with no direct malicious activity. However, its subnet shows moderate abuse density, and the high risk score warrants proactive monitoring and blocking to mitigate potential risks.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | DO-13 |
| CIDR Block | 146.190.0.0/16 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | srv.lanzatumarca.com |
| Forward Confirmed | Yes β FCrDNS verified |
| Forward Hostnames | srv.lanzatumarca.com |
π DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | Present |
| DMARC | Not configured |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Tier 3 β Basic operator with some routing infrastructure |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | β |
| 443 | https | tcp | β |
| 22 | ssh | tcp | |
| 8443 | https-alt | tcp | β |
| Closed Ports | 25, 3389, 8080 (4 open / 7 scanned) | ||
| Server | nginx |
| HTTP Title | β |
| SSH Version | SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.13 |
π TLS Certificate
| SANs | srv.lanzatumarca.com |
| Valid From | 2026-05-16T13:28:52+00:00 |
| Valid Until | 2026-08-14T13:28:51+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 89 days |
| Serial Number | 060520893C5BF41A83150C1DCCA460EA0063 |
| Thumbprint | C6C777E169B29918CF4D5691A628E99AA8A1CF07 |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 19% | 2 | 2 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 15% | 1 | 2 |
| geolocation | 19% | 2 | 2 |
| Overall | 18% | 9 | 11 |
| Data Coherence | Mixed Signals (68%) β 2 contradiction(s) |
| Attribution | Moderate (55%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
β TLS certificate claims CH but primary geo says US
π Observation Timeline π Live
| First Seen | 2026-06-04 00:31:20 UTC |
| Last Seen | 2026-06-26 18:10:39 UTC |
| Profile Built | 2026-06-24 11:20:31 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 23 |
Full dossier details are available via our API.