146.190.157.110
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: 146.190.157.110
Date: 2026-06-11
Ownership & Network Role
- Provider: DigitalOcean, LLC (ASN 14061)
- Network Type: Cloud Compute (Virtual Machine)
- Geolocation: California, US (Santa Clara)
- Subnet: 146.190.157.110/24 (clean, zero abuse density)
Risk Assessment
- Reputation: Moderate Risk (50/100)
- Threat Indicators: No malicious activity detected (zero threat observations, no DNS/IP listings).
- Network Stability: Stable (no recent route changes).
- Cloud Environment: Firewalled, no open services or TLS certificates detected.
Behavioral & Technical Context
- Geolocation Consensus: High confidence (MaxMind geolocation data).
- DNS: No PTR records or domain associations.
- Neighbor Analysis: Subnet contains 1 sibling IP, all inactive.
Recommendations
- Monitoring: No immediate action required. The IP shows no signs of malicious activity, with no correlation to known threats.
- Firewall: No rules needed; the IP is associated with a legitimate cloud provider and exhibits no suspicious behavior.
Conclusion
This IP is part of a DigitalOcean cloud infrastructure in California, US. It shows no malicious indicators, with stable network behavior and no ties to threat feeds. No further investigation is warranted at this time.
*Generated using IPDebrief threat 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 | DO-13 |
| CIDR Block | 146.190.0.0/16 |
| 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 | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| 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 | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Issued by CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Self-signed: Yes
| SANs | ingress.local |
| Valid From | 2026-05-27T18:36:10+00:00 |
| Valid Until | 2027-05-27T18:36:10+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 365 days |
| Serial Number | 00D229DA18D43F24ED247D2AA42117FAB0 |
| Thumbprint | 45382EA59C62D1183062E3893D532AD10F4CE8F7 |
🎯 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 | 30% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 40% | 2 | 3 |
| Overall | 26% | 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 |
⚠ Claimed geolocation contradicts RTT physics measurement
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-27 01:06:49 UTC |
| Last Seen | 2026-06-29 03:38:11 UTC |
| Profile Built | 2026-06-29 09:40:40 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 25 |
🔍 23 signal types · 25 observations collected
This report is generated from 23+ 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.