143.198.113.241
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: 143.198.113.241
Date: June 14, 2026
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Provider: DigitalOcean (ASN 14061)
- Geolocation: North Bergen, NJ, US (plausible, but ICMP validation failed)
- Network Role: CloudCompute hosting server (no open ports/services detected)
- Threat Indicators: No malicious activity, no known attackers, spam, or Tor exit nodes.
---
**2. Observation History**
- Latest Update: June 14, 2026 (DigitalOcean cloud server, no threats).
- Historical Trends:
- Stable low-risk profile since at least June 4, 2026.
- No persistent malicious behavior or threat persistence.
- ICMP validation failed, limiting geolocation accuracy.
---
**3. Relationships & Network Context**
- Same Network: Linked to `DIGITALOCEAN-143-198-0-0` (CIDR 143.198.0.0/20).
- Subnet: 143.198.113.241/24 (no active neighbors detected).
- Control Plane:
- BGP prefix: `143.198.112.0/20` (DigitalOcean).
- DNSSEC valid, no RPKI issues.
---
**4. Neighborhood Analysis**
- Subnet Abuse Density: 0% (clean).
- Neighbors: No sibling IPs detected (likely a single-host subnet).
---
**5. Recommendations**
- Monitor: Track for unexpected service changes or network activity.
- Validate: Confirm geolocation via alternative methods due to ICMP restrictions.
- No Action Required: No signs of malicious activity or high-risk behavior.
Conclusion: This IP is a legitimate DigitalOcean cloud server with no indications of compromise. Low-risk profile persists across all data sources.
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 | 28% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 21% | 2 | 2 |
| ownership | 20% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 35% | 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-08 05:01:41 UTC |
| Last Seen | 2026-06-27 12:26:24 UTC |
| Profile Built | 2026-06-28 06:29:35 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 23 |
🔍 19 signal types · 23 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.